Adtraction

Adtraction is a partner (affiliate) marketing network. Advertisers run programs that publishers promote; when a referred visitor converts, the advertiser reports the sale or lead back to Adtraction so the originating publisher is credited and commission is calculated.

Datafly Signal delivers those conversions server-side. Instead of relying on a browser tag that can be blocked by ad-blockers or lost to ITP cookie expiry, Signal sends the conversion directly to Adtraction’s tracking endpoint from your server, attributed to the publisher via the Adtraction click identifier that Signal captured first-party at the landing page.

Prerequisites

An Adtraction advertiser account with at least one active program.
Your Program ID (the tp value) — found in your Adtraction dashboard under your program, or in the conversion tag your account manager supplied.
The Transaction Type ID (the tt value) for the conversion you are tracking. A program can define several transaction types (for example Sale and Lead), each with its own ID.
Datafly.js deployed on your site and capturing the Adtraction click identifier on the affiliate landing page (see Identity Signals).

Configuration

Field	Required	Description
Program ID	Yes	Your Adtraction advertiser Program ID (`tp`).
Transaction Type ID	Yes	The numeric transaction-type ID (`tt`) for the conversion you are reporting.
Transaction Type Code	No	The transaction type code (`t`). Defaults to `2` (sale). Change only if your Adtraction tag uses a different code.

Configure in Signal

In the management UI, go to Integrations -> Add integration and choose Adtraction.
Enter your Program ID and Transaction Type ID. Leave Transaction Type Code at its default unless Adtraction told you otherwise.
Attach the Adtraction blueprint to your pipeline and choose the Retail preset.
Save and enable. New conversions begin delivering immediately.

API Endpoint

Signal delivers each conversion as an HTTP GET request whose parameters live entirely in the URL query string:

GET https://track.adtraction.com/t/t?tp={program_id}&tt={transaction_type_id}&t=2&ti={order_id}&am={amount}&c={currency}&epi={click_id}

There is no API token: the conversion is identified by your Program ID (tp) and Transaction Type ID (tt), and attribution is authorised by the click identifier (epi). A 200 response means the conversion was accepted.

Identity Signals

Adtraction attributes a conversion to a publisher using the click identifier set when the visitor clicked an Adtraction tracking link. For server-side delivery this value must be captured and replayed:

On the affiliate landing page, Adtraction appends a click value (the at_gd / EPI parameter) to the URL and/or sets a first-party cookie.
Datafly.js persists that value and Signal stores it as the adtraction_click_id vendor identifier.
On the conversion, Signal sends it back as the epi query parameter.

Without the click identifier, a server-side conversion cannot be attributed to a publisher. Make sure Datafly.js is loaded on your affiliate landing pages and that the click value survives to the order confirmation page.

Email matching: Adtraction’s tag supports an optional MD5-hashed email (xd) as a secondary match key. Signal does not emit it, because Signal hashes PII with SHA-256 and a mismatched hash would harm matching. Attribution relies on the click identifier.

Event Mapping

The Retail preset maps Signal events to Adtraction conversions. All other events are dropped.

Signal event	Adtraction conversion	Notes
`Order Completed`	sale	Sends order reference, amount, currency, coupon, new-customer flag.
`Lead Generated`	lead	Sends reference, optional value and currency.

Example

A purchase tracked with Datafly.js:

datafly.track("Order Completed", {
  order_id: "ORDER-10482",
  revenue: 79.90,
  currency: "SEK",
  coupon: "SPRING10",
  new_customer: true
});

Resulting request to Adtraction (the click identifier is added automatically from the captured adtraction_click_id):

GET https://track.adtraction.com/t/t?tp=1234567&tt=987654&t=2&ti=ORDER-10482&am=79.90&c=SEK&cpn=SPRING10&nc=1&epi=abc123clickid

Parameter	Source	Value
`tp`	Program ID (config)	`1234567`
`tt`	Transaction Type ID (config)	`987654`
`t`	Transaction Type Code (config)	`2`
`ti`	`properties.order_id`	`ORDER-10482`
`am`	`properties.revenue`	`79.90`
`c`	`properties.currency`	`SEK`
`cpn`	`properties.coupon`	`SPRING10`
`nc`	`properties.new_customer`	`1`
`epi`	`adtraction_click_id`	`abc123clickid`

Testing

Click one of your live Adtraction tracking links so a click is registered and the click identifier is set on your landing page.
Complete a test purchase end to end so an Order Completed event fires.
In Signal, open the Event Debugger and confirm the Adtraction request was sent with a 200 response and the expected tp, tt, ti, am, c and epi parameters.
In your Adtraction dashboard, confirm the transaction appears in the transaction report with the correct amount, currency and order reference, attributed to the expected channel.

Troubleshooting

Conversion not attributed to any publisher. The epi click identifier was missing or empty. Confirm Datafly.js is on the affiliate landing page and that adtraction_click_id is captured and still present at checkout. With no click id, Adtraction has nothing to attribute the sale to.
Conversion missing from the report. Check the Program ID (tp) and Transaction Type ID (tt) match your program exactly. A 404 from the endpoint means the program or transaction type is unknown.
Duplicate conversions. Adtraction de-duplicates on the order reference (ti). Ensure properties.order_id is unique per order and stable across retries.
Wrong amount or currency. Confirm properties.revenue is the order value as a plain decimal and properties.currency is a valid ISO 4217 code.
400 response. A parameter is malformed — most often a non-numeric amount or a missing required field. Inspect the request in the Event Debugger.

ShareASale Voluum