Tracking & Attribution

Comment composer une URL de suivi

La réponse fournit trois sources à combiner :

• Page-level trackers.impression: for example, a page impression uses type: "impression" and params including ts and iabConsentString.
• Shared trackingTemplates: one set of client(relative) and server (absolute) URL templates, already containing session and placement query parameters.
• Per-node trackers.click and/or trackers.addToCart on a module, row, or gallery item: type+ params for that specific event (for example, modId, rurl, productCode).

Quel modèle ?

Use the node’s tracking.type to look up trackingTypes.<type>. This defines the valid client.* and server.* keys for that interaction (for example, for link: client.clickRedirect, client.clickEvent, server.clickEvent).

Client/Serveur

• Client (trackingTemplates.client.*): Values are relative paths (including query strings). Prepend your reverse‑proxy base URL (BASEURL).
• Server (trackingTemplates.server.): Values are absolute URL templates on the Epsilon tracking host. Compose the final URL the same way as C2S: template + "&" + queryString(trackers.<slot>params).

Exemples pratiques (pseudocode)

C2S click for a HERO CTA

url = BASEURL + trackingTemplates.client.clickRedirect + "&" + queryString(trackers.click.params)

S2S page impression

url = trackingTemplates.server.impressionEvent + "&" + queryString(trackers.impression.params)

S2S add-to-cart for a product row

url = trackingTemplates.server.addToCartEvent + "&" + queryString(trackers.addToCart.params)

Macro substitution

• Replace {TS} with the current millisecond timestamp, {RURL} with the URL-encoded destination, and {TCF} with the current TCF v2 string from your CMP before firing.
• For add-to-cart, also substitute {QTY} with the absolute quantity of that SKU in the cart at fire time (not a delta), and {CONVERSION_VALUE} with the absolute monetary value of those items (quantity × unit price, minus any applied discounts).

Suivi – Client-serveur (C2S)

C2S tracking is implemented in the browser using composed URLs. Prepend BASEURL to the paths in trackingTemplates.client and append the appropriate trackers.<slot>params (see How to Compose a Tracking URL).

Only client.impressionPixelUrls are pixels (1×1 GIF). The other client templates are not pixels:

• client.clickRedirect: 302 redirect endpoint. Epsilon logs the click and redirects the browser to the decoded rurl. Use this as a browser navigation target.

• client.clickEvent: Event beacon returns 204 No Content). Fire using navigator.sendBeacon or fetch({ keepalive: true }). Do not render as <img>.

• client.addToCartEvent: Event beacon (returns 204). Uses the same firing pattern as clickEvent.

Étapes de mise en œuvre

1. Affichez le contenu de la page de marque renvoyé par l'API.

2. Après la diffusion, déclenchez des pixels d’impression dans le navigateur (toutes les entrées dans trackingTemplates.client.impressionPixelUrls, sous forme d'images 1×1).

3. When a user clicks a trackable node, either:
   (a) redirect through the composed client.clickRedirect URL, or
   (b) fire the composed client.clickEvent URL as an event beacon and navigate to the destination yourself.
   Use one or the other per click, not both.

Pixel d’impression

After the brand page renders, fire each path in trackingTemplates.client.impressionPixelUrls as a 1×1 image, (see How to Compose a Tracking URL).

<img src="https://www.retailer.com/epsilon/tracking/v3/impression/pixel/brandpage_djog...?...&ts=1737485823910"
     width="1" height="1" style="display:none" />

Étapes :

1. Pour chaque chaîne dans trackingTemplates.client.impressionPixelUrls, ajoutez votre BASEURL au début (par exemple, https://www.retailer.com/epsilon).
2. Append & + queryString(trackers.impression.params), substituting {TS} with the current millisecond timestamp and {TCF} with the current consent string from your CMP.
3. Déclenchez en tant que < img src="..."> 1×1 dans le navigateur (ou équivalent).

Suivi des clics

Option A : cliquer sur Rediriger (client.clickRedirect)

Navigate the user through the composed URL. Epsilon logs the click and responds with HTTP 302 to the decoded rurl. This endpoint is GET only, and rurl is required;

Option B : cliquer sur balise d’événement (client.clickEvent)

Fire as a beacon and navigate yourself. Accepts GET or POST, returns 204 No Content. Not an image; do not render as<img>.

Ajouter au panier (C2S)

Fire trackingTemplates.client.addToCartEvent as an event beacon (not a pixel) when the user adds a product to cart. Accepts GET or POST, returns 204 No Content.

Suivi – Serveur-serveur (S2S)

S2S tracking is implemented on your backend. Compose URLs the same way as C2S: start from the appropriate trackingTemplates.server string, then append trackers.<slot>params. Server templates are already absolute — there is no BASEURLto prepend. (see How to Compose a Tracking URL).

Quand utiliser le suivi S2S

• Votre architecture nécessite un déclenchement d’événements côté serveur.
• Vous avez besoin d'un suivi dans des environnements où les pixels côté client ne sont pas fiables.
• You want to mix strategies - e.g. C2S impressions + S2S add-to-cart. This is supported but never fire both C2S and S2S for the same event.

Notification d'impression S2S

After the brand page is rendered, your server issues a GET or POST to the composed impression URL: trackingTemplates.server.impressionEvent + trackers.impression.params (substitute {TS} and {TCF} before sending).

Notification de clic S2S

Compose: trackingTemplates.server.clickEvent + trackers.click.params (substitute {TS}, {RURL}, and {TCF}), then issue GET or POST.

Notification d'ajout au panier S2S

Compose: trackingTemplates.server.addToCartEvent + trackers.addToCart.params (substitute {TS}, {QTY}, {CONVERSION_VALUE}, and {TCF}), then issue GET or POST.

Paramètres S2S

Référence de la macro

Référence d'encodage d'URL

Lorsque vous encodez {RURL}, utilisez l'encodage en pourcentage standard :

redirectParams and Redirect Signing

When platform redirect signing is enabled, trackers.click may include a redirectParamsobject alongside params. The keys in 7are merged only into client.clickRedirect URLs — not into clickEventor any server URL.

Two cases:

Embedded link destinations (URL baked into params.rurl): the platform signs the redirect at serve time and emits literal rurlKidand rurlSigvalues in redirectParams. Append these as-is to the clickRedirect URL.

Retailer-controlled redirects (params.rurl is {RURL}): redirectParams contains the macros {RURL_KID} and {RURL_SIG}. Call the batch sign endpoint (redirectSigning.url from the response) to obtain the key id and signature for your destination URL, then substitute before appending.

The top-level redirectSigningobject, when present, provides the batch POST /ads/v3/redirect/sign endpoint URL and the maxUrlsbatch limit. Contact Epsilon to confirm whether redirect signing is enabled for your integration.

clickRedirect composition with redirectParams:

BASEURL + trackingTemplates.client.clickRedirect + "&" + queryString(trackers.click.params) + "&" + queryString(trackers.click.redirectParams)

Guide de style

Before enabling Brand Pages on your site, we need to capture your site's visual identity. Fill in the table below with your design values. Our team will use this to configure the brand page preview experience.

Logo

Couleurs

Typographie

Boutons

Exigences relatives au contenu du module

Les pages de marque sont composées de modules de contenu. Pour chaque type de module, indiquez les contraintes de contenu requises par votre site. Notre équipe les utilisera pour configurer les règles de validation des modèles.

IMAGE Modules

TEXT Modules

PRODUCT_GRID Modules

IMAGE_GALLERY Modules

Le module Galerie d’images hérite des mêmes propriétés de configuration que le module IMAGE. En outre, il accepte également les propriétés spécifiques à la galerie suivante :

SPLIT_LAYOUT Modules

Le module Split Layout permet d'afficher deux modules côte à côte. Actuellement, seuls les modules Texte et Image sont pris en charge. En plus des paramètres de configuration individuels pour les modules Texte et Image (décrits dans les sections ci-dessus), les propriétés supplémentaires suivantes sont requises :

Identité et confidentialité

Identifiants acceptables

• Session ID - anonymous session identifier (non-PII)
• Customer ID - retailer customer identifier (non-PII, e.g. loyalty ID hash)

Exigences en matière de confidentialité

Les détaillants doivent :

• Divulguer le suivi des mesures dans leur politique de confidentialité
• Fournir des liens de désabonnement :
  • NAI: https://optout.networkadvertising.org/
  • DAA: https://optout.aboutads.info/

RGPD / Consentement

Passez l'objet regs sur POST /ads/v3/brand-pages :

• regs.gdpr: 1 when the request is subject to GDPR (EU/EEA/UK treatment per your policy); 0otherwise.
• regs.consent: When gdpr is 1, pass the current TCF v2 consent string from your CMP (the same value you would surface to other ad partners). Do not invent or hardcode a string—use what the user’s browser / app has consented to.
• iabConsentString: This appears in every tracker slot's params, not in trackingTemplates. When regs.consent was provided, the value is the literal TC string and no further action is needed.
• When regs.consent was omitted, the value is the {TCF}macro — substitute the current TCF v2 string from your CMP at fire time before sending any tracking request.