Integrations / Analytics
etracker
Server-side delivery to etracker analytics. Reproduces etracker's tracking hit (GET to the v6 tracking endpoint with URL-encoded parameters) from the customer's own first-party server, so page views, on-site search, e-commerce orders and lead conversions are recorded in etracker analytics even when ad blockers or tracking-prevention block the browser pixel. The etracker account is identified by its public secure code (the `et` parameter); no secret token is sent. Consent is honoured by setting et_cblk=1 (cookie-less / no-consent mode) when marketing consent is absent.
Datafly Signal delivers first-party events to etracker server-to-server from infrastructure you control, using a pre-built blueprint that maps your event schema to the payload etracker expects.
Why route etracker through Datafly Signal
Your numbers stop depending on what the browser allows
Client-side analytics loses every visit where the tag is blocked or the page unloads early. Signal delivers from the server, so etracker receives the complete event stream.
Client IP and user agent are preserved
Server-to-server delivery normally loses both, which weakens matching. Signal forwards the genuine visitor values as request headers so etracker attributes the event to the right session.
One consent decision governs every destination
etracker is gated by the same consent state as the rest of your stack, so a withdrawal applies everywhere at once.
What ships in the blueprint
Mapped events
generate_leadpagepurchaserefundsearchVertical presets
Default. Each preset starts from a working configuration for that vertical rather than a blank field map.
Full field mappings, configuration fields, and troubleshooting are in the etracker documentation.
Frequently asked questions
Does Datafly Signal integrate with etracker?
Yes. Datafly Signal delivers first-party events to etracker server-to-server from infrastructure you control, using a pre-built blueprint that maps your event schema to the payload etracker expects. The integration is included in every deployment at no additional cost.
How is server-side etracker tracking different from the etracker tag?
The etracker tag runs in the visitor's browser, so it is subject to ad blockers, tracking prevention, and page-unload races. Signal collects the event through a first-party endpoint on your own domain and delivers it to etracker from your server, so delivery does not depend on browser conditions.
Which events can Signal send to etracker?
The blueprint ships with mappings for generate_lead, page, purchase, refund, search. Any event in your schema can be mapped to etracker through pipeline configuration without a code change.
Do I need to keep the etracker tag on my site?
No. Signal delivers to etracker from the server, so no client-side etracker script is required on your site.
Other analytics integrations
Ready to move etracker server-side?
See how Datafly Signal delivers first-party events to etracker from infrastructure you control, with hashed identity and consent enforcement built in.