Intro
S2S (Server-to-Server) Tracking Pixel integration allows you to track ad impressions, clicks, and conversion events (e.g., signups, deposits) from Cointraffic. This data helps measure campaign performance, optimize and improve marketing effectiveness.
How S2S Tracking Work
When a visitor clicks on your ad, Cointraffic appends tracking query parameters to your landing page URL.
We provide several UTM tags to help you track conversion statistics, such as {CAMPAIGN_ID}, {GEO}, and {WEBSITE_DOMAIN}.
The most important parameter for S2S tracking is the {CLICK_ID} UTM tag. This tag assigns a unique identifier to each click and allows us to track the visitor's journey within our system, helping to optimize your campaigns.
If you need a custom analytics setup, you can define a specific query parameter in the creative URL (e.g., example.com?custom_click_param={CLICK_ID}). If {CLICK_ID} is missing in the creative URL, we will automatically pass it as ct_click_id (e.g., example.com?ct_click_id={CLICK_ID}).
Once the visitor lands on your page, you must store this query parameter and send it back to us when the visitor takes an action (e.g., registration or deposit). Typically, the Click ID parameter is stored in localStorage, cookies, or an analytics system.
You can trigger multiple actions and pass the necessary data to track conversions, including any additional data required.
How to Integrate the Tracking Pixel
Your server must send a GET request to our S2S endpoint with the values of the initially set variables as follows:
https://apps-pxl.ctengine.io/e?k=UNIQUE_PIXEL_ID&ev=EVENT_NAME&click_id=CLICK_ID
UNIQUE_PIXEL_ID– A unique key provided by our managers, linked to your Cointraffic account (required).CLICK_ID– A unique identifier generated each time a visitor clicks on the banner. This value must be stored on your end and sent back to us when the event is triggered (required).EVENT_NAME– The name of the event (maximum 20 characters, no spaces or special characters) (required).
Parameter Description
Below is a detailed list of all available query parameters and their descriptions.
REQUIRED Parameters
Parameter | Description | Example | Type |
k | Your unique tracking pixel key, which you will receive from our manager. | ABcdEFgH | static |
click_id | A unique Click ID generated each time a visitor clicks on your banner. It can be stored in a cookie or local storage and retrieved from the URL parameter when a visitor reaches your landing page. | 00000000-0000-0000-0000-000000000000 | dynamic |
ev | The name of the event being triggered on your end. | signup | static |
OPTIONAL Parameters
Parameter | Description | Example |
Any custom tag name (e.g., | Any event data passed along. It can contain letters and numbers. Used to send additional event details, such as deposit amount, anonymous client ID, etc. | 50.00 |
Examples
Basic Signup Request Example
Basic Signup Request Example
https://apps-pxl.ctengine.io/e?k=ABcdEFgH&ev=signup&click_id=3647587a-4c6f-4452-496b -547462b755d2
Signup Request Example with Custom User ID Tag
Signup Request Example with Custom User ID Tag
https://apps-pxl.ctengine.io/e?k=ABcdEFgH&ev=signup&click_id=3647587a-4c6f-4452-496b -547462b755d2&user_id=12345
The user_id parameter is a custom tag in this example and is not required.
Deposit Request Example with Custom User ID and Deposit Amount Tag
Deposit Request Example with Custom User ID and Deposit Amount Tag
https://apps-pxl.ctengine.io/e?k=ABcdEFgH&ev=deposit&click_id=3647587a-4c6f-4452-496b-547462b755d2&user_id=12345&deposit_amount=1
The deposit_amount parameter is a custom tag in this example and is not required.