> 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/integrations/destinations/demand-side-platforms-dsps/simpli.fi-conversions-api-early-access/simpli.fi-reference.md).

# Simpli.fi Reference

This is a reference document for the Simpli.fi destination. For information on how to set up this integration, see the [Simpli.fi Quick Start Guide](/integrations/destinations/demand-side-platforms-dsps/simpli.fi-conversions-api-early-access/simpli.fi-quick-start-guide.md).

{% hint style="warning" %}
The Simpli.fi Conversions API destination is currently in Early Access. Please contact <support@freshpaint.io> for more information about this integration.
{% endhint %}

## Destination Info

* Supports [Track](/reference/developer/freshpaint-sdk-reference.md#track) calls
* Supports [HIPAA mode](/readme/hipaa-mode.md)
* Supports forwarding from the [Google Tag Manager Integration](/integrations/google-tag-manager-integration.md)
* Refer to this destination as **Simpli.fi** in the [Integrations object](/reference/developer/freshpaint-sdk-reference.md#using-the-integrations-object)
  * If you've configured multiple Pixel IDs, you can choose a specific one by suffixing the Pixel ID, such as: **Simpli.fi::123456.** You can retrieve this value from the Simpli.fi configuration page for the Pixel ID of interest.

{% hint style="info" %}
When no suffix is specified, all configured Pixel IDs are selected for inclusion / exclusion.
{% endhint %}

* Connection Modes:

<table><thead><tr><th width="200.33333333333331" align="right"></th><th data-type="checkbox">Client-side</th><th data-type="checkbox">Server-side</th></tr></thead><tbody><tr><td align="right">Web</td><td>false</td><td>true</td></tr><tr><td align="right">Mobile</td><td>false</td><td>true</td></tr><tr><td align="right">Server</td><td>false</td><td>true</td></tr></tbody></table>

## View-Through Tracking

Freshpaint supports view-through tracking by capturing the `$sifi_transaction_id` and `$sifi_day` parameters passed in by Simpli.fi using the Freshpaint Impression Pixel. Assuming you have followed the [Simpli.fi Quick Start Guide](/integrations/destinations/demand-side-platforms-dsps/simpli.fi-conversions-api-early-access/simpli.fi-quick-start-guide.md) to set up your destination, you can verify that view-through tracking is working by looking for an event in Event Verification that contains the `$sifi_transaction_id` and `$sifi_day` fields.

You can also look for a transformation that shows the event data was enriched by the Freshpaint Impression Pixel.

<figure><img src="/files/OkbJ0wOJwxCK27h72BvV" alt="Freshpaint transformation showing impression pixel match"><figcaption></figcaption></figure>

For unattributed conversions (where no impression pixel match is found), if `$ip` is allowlisted, Freshpaint will send the user's IP address as a device identifier so Simpli.fi can still\
record the conversion.

## Relevant Properties

| Freshpaint Property    | Simpli.fi Parameter  | Type    | Required?   | Description                                                                                                                                                                                                         |
| ---------------------- | -------------------- | ------- | ----------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| `audience_key`         | `audience_key`       | string  | Required    | The Simpli.fi conversion audience key. Set via a Send Constant Property transformation. Identifies the Simpli.fi conversion audience to attribute the conversion to.                                                |
| `$sifi_transaction_id` | `transaction_id`     | string  | Recommended | The Simpli.fi unique identifier for impressions. Captured automatically by the Freshpaint Impression Pixel from the `{{transactionID}}` macro on your Simpli.fi creatives. Required for view-through attribution.   |
| `$sifi_day`            | `sifi_day`           | integer | Recommended | The internal Simpli.fi day identifier of the impression. Captured automatically by the Freshpaint Impression Pixel from the `{{sifiDay}}` macro on your Simpli.fi creatives. Required for view-through attribution. |
| `$ip`                  | `device_id`          | string  | Recommended | The IP address of the user. Used as the device identifier for unattributed conversions when no impression pixel match is found.                                                                                     |
| `purchase_value_usd`   | `purchase_value_usd` | number  | Recommended | The monetary value of the conversion event in US dollars.                                                                                                                                                           |
| `purchase_order_id`    | `purchase_order_id`  | string  | Recommended | A unique identifier for the purchase associated with the conversion.                                                                                                                                                |


---

# 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:

```
GET https://documentation.freshpaint.io/integrations/destinations/demand-side-platforms-dsps/simpli.fi-conversions-api-early-access/simpli.fi-reference.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.
