Tracking & Attribution

Cómo componer una URL de seguimiento

La respuesta proporciona tres fuentes para combinar:

• 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).

¿Qué plantilla?

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).

Cliente frente a servidor

• 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).

Ejemplos resueltos (pseudocódigo)

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).

Seguimiento: cliente a servidor (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.

Pasos para la implementación

1. Renderiza el contenido de la página de marca devuelto por la API.

2. Tras la representación, active los píxeles de impresión en el navegador (todas las entradas en trackingTemplates.client.impressionPixelUrls, como imágenes de 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.

Píxel de impresión

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" />

Pasos:

1. Para cada cadena de trackingTemplates.client.impressionPixelUrls, anteponga su BASEURL (p. ej., 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. Actívelo como una < img src="..."> de 1×1 en el navegador (o equivalente).

Seguimiento de clics

Opción A: haga clic en Redirigir (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;

Opción B: haga clic en la baliza de eventos (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>.

Añadir al carrito (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.

Seguimiento: de servidor a servidor (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).

Cuándo usar el seguimiento S2S

• Su arquitectura requiere la activación de eventos por parte del servidor.
• Necesitará seguimiento en los entornos en los que no sean fiables los píxeles del lado del cliente.
• 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.

Notificación de impresiones 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).

Notificación de clic S2S

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

Notificación S2S de agregar al carrito

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

Parámetros S2S

Referencia macro

Referencia de codificación de URL

Al codificar {RURL}, utilice la codificación porcentual estándar:

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)

Guía de estilo

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.

Logotipo

Colores

Tipografía

Botones

Requisitos de contenido del módulo

Las páginas de marca se componen de módulos de contenido. Para cada tipo de módulo, indique las restricciones de contenido que exige su sitio. Nuestro equipo las utilizará para configurar las reglas de validación de plantillas.

IMAGE Modules

TEXT Modules

PRODUCT_GRID Modules

IMAGE_GALLERY Modules

El módulo de Galería de imágenes hereda las mismas propiedades de configuración que el módulo de IMAGEN. Además, también acepta las siguientes propiedades específicas de la galería:

SPLIT_LAYOUT Modules

El módulo de Diseño dividido permite mostrar dos módulos uno al lado del otro. Actualmente, solo se admiten los módulos de Texto e Imagen. Además de los ajustes individuales de configuración para los módulos de Texto e Imagen (descritos en las secciones anteriores), se requieren las siguientes propiedades adicionales:

Identidad y privacidad

Identificadores aceptables

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

Requisitos de privacidad

Los minoristas deben:

• indicar el seguimiento de las mediciones en su política de privacidad
• proporcionar enlaces de exclusión:
  • NAI: https://optout.networkadvertising.org/
  • DAA: https://optout.aboutads.info/

RGPD / Consentimiento

Pase el objeto regsa 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.