> For the complete documentation index, see [llms.txt](https://track360.gitbook.io/track360/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://track360.gitbook.io/track360/section-10-integrations/editor/10.1-postbacks-pixels-integration.md).

# 10.1 Postbacks/Pixels Integration

* These pixels act as automated notifications sent from the platform to a specified URL when a particular event occurs.

{% hint style="warning" %}
For tracking the affiliate's postbacks fired go into section [4.3 Postbacks Report](/track360/section-4-reports-and-analytics/editor/4.3-reports.md#postbacks-report)
{% endhint %}

<figure><img src="https://track360.gitbook.io/track360/~gitbook/image?url=https%3A%2F%2F4110691288-files.gitbook.io%2F%7E%2Ffiles%2Fv0%2Fb%2Fgitbook-x-prod.appspot.com%2Fo%2Fspaces%252F1iHXZgeTSXZwHDnWa5S8%252Fuploads%252Fe4wod8eB9iBFPs9IV39y%252FPostback_T360.jpg%3Falt%3Dmedia%26token%3D5193de7c-be25-4cdd-b290-6817c5612fa9&#x26;width=768&#x26;dpr=4&#x26;quality=100&#x26;sign=f3b55b8f&#x26;sv=2" alt=""><figcaption></figcaption></figure>

* Before configuring postbacks, the affiliate must configure the **entry URL.**
  * Add parameters to links generated on Track360.
  * The Entry URL is the **tracking link** that an affiliate uses to send traffic to the advertiser.
  * Contains the parameters sent from the affiliate that want to track and receive as postback information.
  * Parameters that are not added in the original tracking links can not be send in the postbacks.

{% hint style="success" %}
Where the **entry URL** should point the affiliate's platform domain. For example: <https://tracking.brandname.com/click?affid=101&campaign=2001&affclickid=1122223444455565666>

Please **do not** **clickid** to name a parameter. Instead, you can use alternatives as trackid, affclickid, or similar.
{% endhint %}

* After configuring postbacks on Track360, the affiliate will receive the **Final URL.**
  * The Final URL is the **postback URL** used on the platform with the conversion data back to the affiliate’s system.
  * Contains the parameters that will be dynamically replaced when the postback fires.
  * Postbacks are fired once Track360 receives the event (event trigger may be delayed by 5 secs - 5 mins delayed depending on integration)

{% hint style="success" %}
Where the **final URL** should point the affiliate's crm domain, will be the same domain as Postback URL with the parameters converted. For example: <https://affiliatedomain.com/postback?click_id={affclickid}&payout_sum={amount}&currency={currency}>
{% endhint %}

* The **Postback URL** should point to the domain where the affiliate will receive the conversion data.
* The **URL Postbacks parameters** needed include specific parameters that allow proper attribution of the activity.
* The parameters included in the postback URL must be configured in advance by the affiliate/IB in the input URL.

{% hint style="warning" %}
Values inside braces **{}** define the parameters using Track360's naming convention. These placeholders will be dynamically replaced with actual data during postback generation. The value before the equal **=** is customizable to define how do you want to name the parameter.
{% endhint %}

* The **dynamic parameters** are variables wrapped in **{}** that are automatically replaced by real data when the postback fires. At least one of these parameter type must be configured:
  * This parameters will give you values provided from the affiliate platform
  * Needs to be named as the affiliate platform named
  * Used to pass changing values such as {affclickid}, {campaign}, {amount}, {currency}
  * These ensure tracking systems can attribute each conversion to the correct value.

{% hint style="success" %}
An example for dynamic parameters: \
URL postback: \&click\_id={affclickid}\&payout\_sum={amount} \
Final URL (output when fired): \&click\_id=1122223444455565666\&payout\_sum=50
{% endhint %}

* The **static parameters** are values manually set in the postback URL by the affiliate/IB. It could be present as no
  * This parameters will give you fixed values
  * Remain the same for every postback fired.
  * Used for constants such as source, type, partner\_id.

{% hint style="success" %}
An example for statics parameters: \
URL postback: \&source=track360\&type=signup \
Final URL (output when fired): \&source=track360\&type=signup
{% endhint %}

{% hint style="success" %}
Example of a **URL postback** with combined parameters (dynamic + static) **URL postback:** <https://affiliatedomain.com/postback?click_id={affclickid}&payout_sum={amount}&currency={currency}&source=track360&type=signup>

**Final URL** (output when fired): [https://affiliatedomain.com/postback?](https://affiliatedomain.com/postback?affclickid=1122223444455565666\&payout_sum=50\&currency=USD\&source=track360\&type=sign)[affclickid=1122223444455565666](https://tracking.affiliatesystem.com/click?affid=101\&campaign=2001\&clickid=abc123)[\&payout\_sum=50\&currency=USD\&source=track360\&type=signup](https://affiliatedomain.com/postback?affclickid=1122223444455565666\&payout_sum=50\&currency=USD\&source=track360\&type=signup)
{% endhint %}

### Set Postback for an Affiliabe/IB

* Navigate into **Affiliate/IB Management**&#x20;
* Select the affiliate or click to the arrow icon on the rightmost of the row. Click on the desired affiliate/IB to see details&#x20;

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

* Navigate into **Pixels tab** set Postbacks to the designated affiliate/IB.

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

* Click the **Add Postback Pixel** button to open the setup window, then complete:
  * **Postback URL** is the tracking endpoint.
  * **Trigger Event** to select the event (e.g., Singups, FirstDeposits) that activates the pixel.
  * **Traffic Scope** to define whether the pixel applies to all campaigns or specific ones.
  * **Example of URL** will display a sample URL with placeholders for customization.
  * **System Parameters** incorporate parameters like {affid}, {affclickid}, {campaign}, and {offer\_id} into the URL for detailed tracking.
  * In addition, you can add as many parameters as you want with the structure as **“\&name={parameter}”**

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

* Once the postback setup is saved, it will appear as a row in the list of postbacks for the selected affiliate/IB. For a more detailed explanation, refer to [section 2.6 Open Affiliate Page - Pixels/Postbacks](/track360/section-2-partner-management/editor/2.6-affiliate-details-page.md#pixels-postbacks-tab).

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

{% hint style="info" %}
For tracking the affiliate's postbacks fired go into section[ 6.3 Postbacks Report](https://track360.gitbook.io/track360/section-4-reports-and-analytics/editor/4.3-reports#postbacks-report). Where is necessary to have the following columns checked on the report:

* Clickid to check the entry URL (by clicking on the desired clickid value)
* URL to check the postback URL
* Final URL to check the postback URL replaced with the values on the parameters.
  {% 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:

```
GET https://track360.gitbook.io/track360/section-10-integrations/editor/10.1-postbacks-pixels-integration.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.