IntegrationsAdvertisingEpsilon

Epsilon

Datafly Signal sends browsing and transaction events to the Epsilon Event API (the server-side surface of Epsilon’s DTM tag).

Why route Epsilon through Datafly Signal

  • Conversions survive ad blockers and tracking prevention. A browser tag served from an advertising domain is blocked outright for part of your traffic. Signal sends the event from your own server, so the conversions Epsilon optimises against are not filtered by the browser.
  • One consent decision governs every destination. Epsilon is gated by the same consent state as the rest of your stack, so a withdrawal applies everywhere at once.
  • No vendor tag on the page. Removing it removes its page weight and its independent access to your visitors.

Prerequisites

Get your tagging document

Your Epsilon account team provides a tagging document with the Event API URL (domain and tag path), Company ID (dtm_cid), Secondary Company ID (dtm_cmagic) and the Form IDs (dtm_fid) for browsing and for transactions.

Configure in Signal

Configuration fields

FieldRequiredDescription
endpoint_urlYesThe Epsilon Event API URL (domain and tag path) from the tagging document your Epsilon account team provides.
company_idYesYour Epsilon Company ID (dtm_cid), issued by Epsilon. Found in the tagging document provided by your Epsilon account team.
company_magicYesYour Epsilon Secondary Company ID / Company Magic (dtm_cmagic) that confirms the Company ID. Provided alongside dtm_cid in the Epsilon tagging document.
browse_form_idYesThe Epsilon form ID (dtm_fid) for browsing activity, sent on page and product events. Provided in the Epsilon tagging document alongside dtm_cid.
conversion_form_idYesThe Epsilon form ID (dtm_fid) for transactions, sent on purchase events. Provided in the Epsilon tagging document alongside dtm_cid.

Management UI setup

  1. Go to Integrations > Add Integration > Epsilon.
  2. Choose a preset: Default (default), E-commerce (ecommerce).
  3. Fill in the fields above and click Save.

Request format

GET <Event API URL>?dtm_cid=2474&dtm_cmagic=0bf727&dtm_fid=102&dtmc_loc=https%3A%2F%2F...
    &dtm_user_ip=203.0.113.9&dtm_cookie_id=df_anon&dtm_email_hash=86e0b9e5...
    &dtmc_transaction_id=ORD-1001&dtm_conv_val=259.99&dtm_conv_curr=GBP
    &dtm_items=%5B%7B%22product_id%22%3A%22SKU_1%22%2C%22item_amount%22%3A120%2C%22item_quantity%22%3A2%7D%5D

Signal’s first-party ID is the cookie ID (dtm_cookie_id), which Epsilon requires.

Event mapping

Signal eventVendor eventPresets
pagepageDefault, E-commerce
view_itemview_itemDefault, E-commerce
purchasepurchaseDefault, E-commerce
view_item_listview_item_listE-commerce
add_to_cartadd_to_cartE-commerce
view_cartview_cartE-commerce
begin_checkoutbegin_checkoutE-commerce

Events not listed are not sent (the presets drop unmapped events). Each preset turns on the strict output contract, so only the mapped fields are sent.

Identity

Identifiers: Signal’s first-party cookie ID, your customer ID, a SHA-256 of the normalised email, and the visitor IP and user agent. The TCF string is forwarded when present.

Limitations

  • Epsilon publishes no API reference; parameters follow Tealium’s Epsilon Event API connector guide (updated 2026-03-17). Confirm the request with your Epsilon account team.
  • Epsilon lists a GPP string as required; Signal does not collect GPP yet, so it is not sent.
  • dtm_conv_val is the order value from the event, which in the Datafly spec includes tax and shipping; Epsilon asks for the subtotal.

Vendor documentation

Epsilon (read 2026-09-22).

KoddiLiveIntent