Epsilon

Datafly Signal delivers events to Epsilon (formerly Conversant / Dotomi) server-to-server using the Epsilon Event API — the server-side surface of Epsilon’s DTM (Data & Tag Management) tag. This sends your browsing and conversion data to Epsilon for first-party audience building and conversion attribution without a client-side pixel, so delivery is not affected by ad blockers or browser tracking prevention.

Prerequisites

Before configuring Epsilon in Signal you need an active Epsilon (Conversant) advertiser account and the tagging document Epsilon issues for it. That document contains the values you will enter in Signal.

Configure in Signal

Configuration Fields

The browsing and conversion Form IDs are set on the integration’s field mappings (dtm_fid) per event, so a single integration can route page views and purchases to different Epsilon forms.

Management UI Setup

1. Go to Integrations → Add Integration → Epsilon.
2. Choose the Default preset (page browsing + purchase conversion).
3. Enter your company_id and company_magic.
4. Set the browsing and conversion Form IDs in the event field mappings.
5. Select consent categories (typically advertising or marketing).
6. Click Save.

API Endpoint

GET https://fp.dotomi.com/dtm/track?dtm_cid={company_id}&dtm_cmagic={company_magic}&dtm_fid=...

The Epsilon Event API is a GET “fire pixel”: every field is carried on the URL query string and the response is a 1×1 image. There is no JSON body and no API key — the account is authenticated by dtm_cid plus dtm_cmagic, which Signal appends to every request.

Identity Signals

Epsilon matches server events to user profiles using several signals. The more you provide, the higher your match rate.

Automatic Signals

Sent automatically by Signal — no configuration needed:

User-Provided Signals (Hashed)

When a user is identified via datafly.identify(), the email is normalised (trim + lowercase) and SHA-256 hashed before delivery:

How to Send User Data

datafly.identify("user-123", {
  email: "jane.doe@example.com"
});

Signal normalises and hashes the email automatically before sending to Epsilon.

Consent

Epsilon honours IAB consent strings. Signal forwards whichever your CMP produced:

Events only deliver when the visitor’s canonical marketing consent is granted, per the integration’s selected consent categories.

Event Mapping

Default preset

To customise, edit the integration’s Field Mappings in the Management UI.

Example: Purchase Event

Datafly.js call:

datafly.track("Order Completed", {
  order_id: "ORD-001",
  revenue: 129.99,
  currency: "USD",
  products: [
    { product_id: "SKU-A", price: 49.99, quantity: 2 },
    { product_id: "SKU-B", price: 30.01, quantity: 1 }
  ]
});

Epsilon Event API request sent by Signal:

GET https://fp.dotomi.com/dtm/track
  ?dtm_cid=1234567
  &dtm_cmagic=abc123def
  &dtm_fid=conversion-form
  &dtmc_conv_type=purchase
  &dtmc_transaction_id=ORD-001
  &dtm_conv_val=129.99
  &dtm_conv_curr=USD
  &dtm_user_ip=203.0.113.50
  &dtm_email_hash=5e88489...
  &dtmc_loc=https%3A%2F%2Fexample.com%2Fcheckout%2Fconfirmation
  &dtmc_tcf_string=CPxxxx...

The visitor User-Agent is sent as the request’s User-Agent header.

Testing Your Integration

1. Trigger a page and an Order Completed event on your site.
2. In Signal’s Event Debugger, confirm the outbound request to fp.dotomi.com shows your dtm_cid, the correct dtm_fid, and the conversion parameters.
3. Confirm a 200 OK (or image) response.
4. Ask your Epsilon account team to confirm the events are landing against the expected Company ID and Form IDs — Epsilon does not provide a self-serve real-time event inspector.

Troubleshooting