Everflow

Datafly Signal records conversions in Everflow server-to-server using Everflow’s S2S conversion postback. Instead of firing a browser pixel, Signal sends an HTTP GET postback to your Everflow tracking domain when a conversion happens, matching it to the originating click via Everflow’s transaction_id. This delivery is not affected by ad blockers or browser tracking prevention.

Prerequisites

Before configuring Everflow in Signal you need an Everflow account with at least one tracking domain and offer set up, plus your Network ID.

Step 1: Find your Network ID (NID)

Log in to your Everflow Control Center.
Open your Postback URL (Control Center > Tracking Domains, or the offer’s postback settings).
Note the nid value — it is prefilled in the postback URL. This is your Customer / Network ID.

Step 2: Find your Tracking Domain

In Everflow, go to Control Center > Tracking Domains.
Copy the hostname of the tracking domain you use for this offer (for example trk.example.com).

Everflow records conversions, not page views. Signal only delivers conversion events (such as a completed order) to Everflow; page views and other non-conversion events are dropped.

Step 3: Confirm click capture

Everflow attributes a conversion to a click using a transaction_id (a 32-character click ID). When a visitor arrives via an Everflow tracking link, Everflow sets a click cookie (_ef_transaction_id) and/or a transaction_id URL parameter. Make sure your site captures this value and passes it to Signal on the conversion event (see Event Mapping below).

Configure in Signal

Configuration Fields

Field	Required	Description
`tracking_domain`	Yes	Your Everflow tracking domain hostname (e.g. `trk.example.com`). No `https://`, no trailing slash.
`network_id`	Yes	Your Everflow Network ID (`nid`), prefilled in your postback URL.
`verification_token`	No	Optional postback verification token. Only set this if the advertiser has enabled token verification.

Management UI Setup

Add the integration

Go to Integrations > Add Integration > Everflow.

Choose a preset

Select the Default preset for standard conversion tracking.

Enter your settings

Enter your tracking_domain and network_id. Leave verification_token blank unless your advertiser requires it.

Save

Select your consent category (typically advertising or marketing) and click Save.

API Endpoint

GET https://{tracking_domain}/?nid={network_id}&transaction_id={transaction_id}&amount={amount}&currency={currency}&order_id={order_id}

The conversion postback is an HTTP GET request — every field is a URL query-string parameter. There is no request body and no Authorization header; the nid parameter identifies your account.

Identity Signals

Everflow matches a conversion to its originating click using transaction_id — Everflow’s click ID. Unlike pixel-based vendors, Everflow does not use hashed PII for matching.

Signal	Parameter	Description
Click ID	`transaction_id`	Required. Everflow’s 32-character click ID, captured client-side from the `_ef_transaction_id` cookie or `transaction_id` URL parameter set when the user arrives via an Everflow tracking link.
Email	`email`	Optional. Sent as plaintext (URL-encoded) — Everflow does not hash it.
IP address	`user_ip`	Visitor IP, forwarded from the original request, used for quality and fraud signals.
User-Agent	`user_agent`	Visitor User-Agent, forwarded from the original request.

⚠️

The conversion cannot be attributed without transaction_id. Ensure your site captures Everflow’s click ID and passes it on the conversion event as shown below.

Event Mapping

Default preset

Signal event	Everflow action
`Order Completed`	`conversion` (sends `amount`, `currency`, `order_id`, `coupon_code`)
`Lead Generated`	`conversion` (sends `amount`, `currency`, `adv_event_id`)

All other events (including page) are dropped — Everflow has no pageview ingestion.

Example: Order Completed

Datafly.js call (note transaction_id captured from the Everflow click cookie):

datafly.track("Order Completed", {
  transaction_id: "3a1f9c8e2b7d4f6a0c5e8b1d2f3a4c5e",
  order_id: "ORD-001",
  revenue: 149.99,
  currency: "EUR",
  coupon: "SAVE20"
});

Postback sent by Signal:

GET https://trk.example.com/?nid=12345&transaction_id=3a1f9c8e2b7d4f6a0c5e8b1d2f3a4c5e&amount=149.99&currency=EUR&order_id=ORD-001&coupon_code=SAVE20

Testing

Visit your site through an Everflow tracking link so a transaction_id is set.
Complete a test conversion (e.g. a test order) to fire the Order Completed event.
In Everflow, open Reporting > Conversions and confirm the conversion appears with the correct amount, order_id, and currency.
You can also paste a sample postback URL into Everflow’s Postback URL Validator to confirm the format before going live.

Troubleshooting

Problem	Solution
Conversion not appearing in Everflow	Confirm `transaction_id` is present on the event. Without it Everflow cannot attribute the conversion. Check the visitor actually arrived via an Everflow tracking link.
Wrong or missing revenue	Ensure `amount` is a plain decimal (e.g. `149.99`, not `$149.99`). Map your order total to `properties.revenue`.
Currency ignored	Only send `currency` (3-letter ISO code) when it differs from the offer’s default currency.
`401` / `403` responses	Check your `network_id` (nid) is correct, and that `verification_token` matches if the advertiser requires it.
`404` responses	Verify the `tracking_domain` hostname is exactly the domain configured in Everflow.
Page views showing up as conversions	They will not — Signal only delivers conversion events to Everflow; everything else is dropped.

Refersion ShareASale