Tracking & Attribution

추적 URL 구성 방법

응답에서 제공하는 조합 가능한 세 가지 소스입니다:

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

어떤 템플릿이 사용되나요?

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

작업 예시(의사코드)

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

추적 – 클라이언트-서버(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.

구현 단계

1. API가 반환한 브랜드 페이지 콘텐츠를 렌더링합니다.

2. 렌더링 후, 브라우저에서 노출 픽셀을 실행합니다(trackingTemplates.client.impressionPixelUrls의 모든 항목을 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.

임프레션 픽셀

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

단계:

1. trackingTemplates.client.impressionPixelUrls의 각 문자열에 BASEURL 을 추가하십시오(예: 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. 브라우저(또는 동등한 환경)에서 1×1 < img src="..."> 으로 실행하십시오.

클릭 추적

옵션 A: 리디렉션 클릭 (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;

옵션 B: 클릭 이벤트 비콘(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>.

장바구니에 추가(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.

추적–서버 간(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).

S2S 추적 사용 시기

• 이 아키텍처는 서버 측 이벤트 발생이 필요합니다.
• 클라이언트 측 픽셀이 신뢰할 수 없는 환경에서는 추적이 필요합니다.
• 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.

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

S2S 클릭 알림

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

S2S 장바구니 추가 알림

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

S2S 매개변수

매크로 참조 안내

URL 인코딩 참조

{RURL}을 인코딩할 때 표준 백분율 인코딩을 사용하십시오:

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)

스타일 안내서

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.

로고

색상

타이포그래피

버튼

모듈 콘텐츠 요구사항

브랜드 페이지는 콘텐츠 모듈로 구성되어 있습니다. 각 모듈 유형에 대해 사이트에 필요한 콘텐츠 제약 조건을 제공해 주십시오. 팀에서 이를 사용하여 템플릿 검증 규칙을 구성할 것입니다.

IMAGE Modules

TEXT Modules

PRODUCT_GRID Modules

IMAGE_GALLERY Modules

이미지 갤러리 모듈은 이미지 모듈과 동일한 구성 속성을 상속합니다. 또한 다음과 같은 갤러리별 속성도 허용:

SPLIT_LAYOUT Modules

분할 레이아웃 모듈을 사용하면 두 모듈을 나란히 표시할 수 있습니다. 현재는 텍스트 및 이미지 모듈만 지원됩니다. 텍스트 및 이미지 모듈에 대한 개별 구성 설정(위의 섹션에 설명됨) 외에도 다음과 같은 추가 속성이 필요합니다:

신원 및 개인정보 보호

허용 가능한 식별자

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

개인 정보 보호 요건

소매업체는 다음을 수행해야 합니다:

• 측정 추적을 개인 정보 보호 정책에 공개
• 광고 수신 거부 링크 제공:
  • NAI: https://optout.networkadvertising.org/
  • DAA: https://optout.aboutads.info/

개인 정보 보호법(GDPR) / 동의

POST /ads/v3/brand-pages에 regs 객체를 전달합니다:

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