Equativ
Datafly Signal reports conversions to Equativ (formerly Smart AdServer) through the click-ID postback.
Why route Equativ 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 Equativ optimises against are not filtered by the browser.
- One consent decision governs every destination. Equativ 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
Add the click ID to your click-through URLs
Append &transactionid=[sas_transactionid] (or your own parameter name) to the click-through URL of your Equativ campaigns.
Capture it
Collect the value in Signal with an ID provider named equativ_transaction_id, or send it on the event as equativ_transaction_id. A conversion without it did not come from an Equativ click and is not sent.
Configure in Signal
Configuration fields
| Field | Required | Description |
|---|---|---|
network_id | Yes | Your Equativ [Smart AdServer] network ID, used by the tracking endpoint mappings. |
site_id | No | Optional site ID when conversions are tracked per site. |
Management UI setup
- Go to Integrations > Add Integration > Equativ.
- Choose a preset: Default (
default), Lead generation (lead_gen). - Fill in the fields above and click Save.
Request format
GET https://www.smartadserver.com/track/download?transactionid=<Equativ transaction ID>The visitor’s user agent and IP are sent as the User-Agent and X-Forwarded-For headers, as Equativ asks for server-side calls. Equativ answers 200 with a 1x1 pixel.
Event mapping
| Signal event | Vendor event | Presets |
|---|---|---|
purchase | download | Default |
generate_lead | download | Lead generation |
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
Attribution is by the Equativ transaction ID only. No personal data is sent.
Limitations
- Deduplicate before sending: each Equativ click should be reported once.
Vendor documentation
Equativ (read 2026-09-22).