> For the complete documentation index, see [llms.txt](https://documentation.freshpaint.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://documentation.freshpaint.io/readme/guides/ios-quickstart-guide/instrumenting-your-app.md).

# Instrumenting Your App

To instrument an event for Freshpaint, add the following bit of code whenever there's an event you want to track:

{% tabs %}
{% tab title="Swift" %}

```swift
Freshpaint.shared().track(
    "Example Event", 
    properties: ["Example Property": "Example Value"]
)
```

{% endtab %}

{% tab title="Objective-C" %}

```objectivec
[[FPAnalytics sharedAnalytics]
              track:@"Example Event" 
              properties:@{ @"Example Property": @"Example Value" }];
```

{% endtab %}
{% endtabs %}

## Verifying the Instrumentation

To verify the instrumentation you can use the Freshpaint Live View. After firing an event, you should see it show up in Freshpaint after a minute:

![](/files/-MQTIzSXRLwhtztWidp1)

You can then click the event to look at the properties of the event and confirm they are correct:

![](/files/-MQTJJsTg4UvoN04X04e)

By default, Freshpaint automatically forwards any event instrumented with the iOS SDK to any enabled destinations. If you now take a look in Amplitude, you will see the events you created being sent:

![](/files/-MQTL6JYeYlTkGen3pbR)

If you'd like to disable this behavior, you can do so by clicking into the event definition, clicking "Settings" and then enabling the "Override hardcoded destinations" toggle. This will disable all active destinations for this event.

<figure><img src="/files/ifCris8ZtdGj5wFThjcu" alt=""><figcaption></figcaption></figure>

{% hint style="info" %}
You'll need to go back into the event definition and re enable any destinations as they will now all be disabled.
{% endhint %}


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://documentation.freshpaint.io/readme/guides/ios-quickstart-guide/instrumenting-your-app.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
