Pixel tracking - also called cookie-based or client-side tracking - attributes conversions using the user's browser rather than a server-to-server postback from the advertiser. A small tracking pixel on the advertiser's conversion page fires back to Swaarm when the user converts.
When to use pixel tracking
Pixel tracking is an alternative to S2S postback tracking. Use it when:
The advertiser cannot send server-side postbacks
The offer does not involve mobile app installs
The end-users are on browsers that support cookies
The advertiser's website uses SSL (HTTPS)
⚠️ If a user does not accept cookies in their browser, they cannot be tracked with pixel tracking.
How to configure pixel tracking
Go to Offer → Edit → General tab
Set Attribution Type to Image Pixel
Add the pixel URL to the advertiser's conversion page
Pixel types supported:
Type | How to use |
Image Pixel | Standard |
iFrame Pixel | Replace |
Tracking events via pixel:
To track specific conversion events (not just the default install), add our_event_type_id= or event_id= to the pixel tracking URL.
How pixel tracking works
On click
User clicks the publisher's ad
Swaarm records the click and generates a unique click ID
Swaarm stores the click ID in a cookie in the user's browser
Swaarm redirects the user to the advertiser's landing page
On conversion
The user completes the desired action on the advertiser's page (purchase, registration, etc.)
The advertiser's conversion page loads a 1×1 pixel containing the Swaarm conversion URL
The pixel fires - the user's browser sends the session cookie (containing the click ID) to Swaarm
Swaarm matches the click ID from the cookie to the original click and records the conversion