Impression Tracking (loaded and viewed impressions)

Track when an ad is shown to the user using a tracking pixel (1x1 image) or by calling the tracking URL. Load impressions should be triggered on pageload, while viewed impressions should be triggered when the asset is in the viewport in accordance with IAB Standards

Click Tracking

Track when a sponsored product is clicked by the user by sending a GET request to the Click URL. The click URL should be triggered for both click and add to basket actions.

For Sponsored Brand ads, the Click URL should be triggered on any click action on the asset or associated products. Pentaleap handles de-duplication of click and impression events automatically.

Conversion Tracking

Track conversions (e.g., purchases) by calling an endpoint on the conversion page with transaction details. Ensure the user_id in the AdRequest matches the user_id in the conversion events.

Refer to our Tracking API Documentation for detailed information.

Trigger Load Impression links on pageload: Load Impression links signified by loadUrls should be triggered on pageload.

Trigger Impression (Beacon) links on view: Impression links signified by beaconUrls should be triggered only when the ad is visible in the viewport to the user. For example, a carousel could contain 10 ads but only display 4, so BeaconUrls should only be triggered for the first 4 until the user scrolls to further ads.

Trigger Click links on click and add-to-cart: The same click link can be associated to multiple actions. For example, if you have an add-to-cart button ans well as a product image and text, the click link should be triggered when the user does any of:

Pentaleap attribution has a de-duplication function to only count clicks once.

Which conversion events to send?

Batch Processing for Conversions: When possible, use batch processing for conversion tracking to reduce the number of POST requests. This can help in managing load and ensuring efficient data transfer.

Consistent User IDs: Ensure that the user_id sent in the AdRequest is the same as the one used in conversion events. This consistency is vital for accurate tracking and attribution.