This article describes how to track conversions using a pixel (image-based integration) as a replacement for server-side postback integration.
The pixel uses the same conversion endpoint and the same parameters as a postback. The only difference is the delivery method: instead of sending the request from the server, the conversion request is triggered by loading an image on a web page.
Insert the following <img> tag on the final confirmation ("thank you") page.
Pixel structure
<img
src="POSTBACK_URL"
width="1"
height="1"
alt=""
/>
Fixed amount conversion
Use this pixel if your postback integration does not send a revenue value.
<img
src="https://YOUR_TENANT_ID.trackdesk.com/tracking/conversion/v1?conversionTypeCode=sale&cid={CLICK_ID}"
width="1"
height="1"
alt=""
/>
Make sure to replace YOUR_TENANT_ID with your actual Tenant ID. Replace CLICK_ID with your Trackdesk click ID (CID).
Revenue share (dynamic amount)
If your postback integration includes a revenue value, include the same parameter in the pixel.
<img
src="https://YOUR_TENANT_ID.trackdesk.com/tracking/conversion/v1?conversionTypeCode=sale&cid={CLICK_ID}&amount.value={AMOUNT}"
width="1"
height="1"
alt=""
/>
Make sure to replace YOUR_TENANT_ID with your actual Tenant ID. Replace CLICK_ID with your Trackdesk click ID (CID), and AMOUNT with the conversion revenue value.
Adding more parameters
The pixel accepts the same extra parameters as a standard postback. Common additions include:
AdvS1–AdvS5: custom advertiser parameters for tracking IDs or traffic source labels.
Customer ID: a customer identifier.
External ID: an order or transaction ID, used for deduplication and refund handling.
Currency: the conversion currency, for revenue-share cases.
Status: the conversion status the conversion will be created with.
For the full syntax and examples, see the Add extra parameters section of the Redirect tracking article.