IntegrationsAnalyticsetracker

etracker

Datafly Signal delivers analytics events to etracker server-to-server. Instead of loading etracker’s browser tracking pixel, Signal reproduces etracker’s tracking hit from your own first-party server, so page views, on-site search, orders and lead conversions are recorded in etracker analytics even when ad blockers or browser tracking-prevention block client-side scripts.

etracker is a German web analytics platform with a strong GDPR and consent posture. Signal honours marketing consent by switching etracker into its cookie-less measurement mode (et_cblk=1) whenever consent is absent, so you collect privacy-compliant analytics without setting cookies.

Prerequisites

Before configuring etracker in Signal you need:

  1. An active etracker analytics account.
  2. Your account secure code (also called the account key, the et value). This is a short alphanumeric string such as M632hA.

Find your secure code

  1. Look at your existing etracker tracking snippet — the secure code is the value of the data-secure-code attribute:

    <script id="_etLoader" data-secure-code="M632hA"
  src="//code.etracker.com/code/e.js" async></script>

  2. Alternatively, sign in to your etracker account and open Account Settings — the secure code is listed there.

Configure in Signal

Configuration fields

FieldRequiredDescription
account_keyYesYour etracker account secure code (the et value, e.g. M632hA).

Management UI setup

Add the integration

Go to Integrations → Add Integration → etracker.

Enter your secure code

Paste your account secure code into the Secure Code (Account Key) field.

Select consent categories

Select the consent category that governs analytics for your deployment (typically analytics or marketing). When consent in that category is absent, Signal sends et_cblk=1 so etracker measures in cookie-less mode.

Save

Click Save. Page and conversion events begin flowing to etracker on the next matching event.

API Endpoint

Signal delivers to etracker’s tracking-hit endpoint as a GET request with URL-encoded query parameters:

GET https://www.etracker.de/api/v6/tracking/ampHitCount?et={account_key}&pagename=...&et_url=...

There is no secret token. The account is identified by the public secure code carried in the et query parameter. The visitor’s IP address and User-Agent are forwarded as request headers (X-Forwarded-For, User-Agent) so etracker attributes geo and device to the real visitor rather than to the Signal server.

Identity Signals

etracker is a first-party analytics platform and does not require hashed PII match keys. Signal forwards:

SignalParameterDescription
Visitor IPX-Forwarded-For headerReal visitor IP, for geo attribution.
User-AgentUser-Agent headerReal visitor device/browser.
Customer IDet_custYour logged-in user identifier (from datafly.identify()), if available.
Consentet_cblkSet to 1 (cookie-less mode) when marketing consent is absent.

No email or phone hashing is performed — etracker measurement is based on the page hit, IP, User-Agent and (optionally) your own customer ID, not on shared identity graphs.

Event Mapping

Default preset

Signal eventetracker hitKey parameters
pagepage viewpagename, et_url, et_ref, areas
Products Searchedon-site searchet_se (search term)
Order Completedorder (sale)et_tonr, et_tval, et_tsale=1
Order Refundedorder (cancellation)et_tonr, et_tval, et_tsale=2
Lead Generatedgoal (lead)et_tonr, et_tval, et_tsale=0

etracker’s et_tsale parameter distinguishes the conversion type: 0 = lead, 1 = sale, 2 = cancellation. Signal sets it automatically per event.

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

Example: page view

Datafly.js call:

datafly.page();

etracker hit sent by Signal:

GET https://www.etracker.de/api/v6/tracking/ampHitCount
  ?et=M632hA
  &v=5.0
  &pagename=Product%20Catalogue
  &et_url=https%3A%2F%2Fexample.com%2Fcatalogue
  &et_ref=https%3A%2F%2Fwww.google.com%2F
  &areas=%2Fcatalogue
  &tc=1717660800000

(plus X-Forwarded-For and User-Agent request headers carrying the real visitor IP and device.)

Example: order

Datafly.js call:

datafly.track("Order Completed", {
  order_id: "ORD-001",
  revenue: 129.99,
  currency: "EUR"
});

etracker hit sent by Signal:

GET https://www.etracker.de/api/v6/tracking/ampHitCount
  ?et=M632hA
  &v=5.0
  &et_tonr=ORD-001
  &et_tval=129.99
  &et_tsale=1
  &pagename=Order%20Confirmation
  &tc=1717660800000
⚠️

etracker expects et_tval (net turnover) as a decimal with a period separator and at most two decimal places. Make sure your revenue property is the net order value, not the gross or formatted string.

Testing

  1. In your etracker account, open Real-time (live) reporting.
  2. Trigger a page view and an order on a page where Signal is active.
  3. Within a few seconds you should see the page name appear in real-time visitors, and the order value appear under e-commerce / goals.
  4. Confirm orders show the correct et_tonr (order number) and et_tval (value).

Because Signal delivers from your server, etracker shows these hits as ordinary first-party traffic. Use a unique order number per test so you can find each one in reporting.

Troubleshooting

ProblemSolution
No hits appear in etrackerCheck the Secure Code (Account Key) is correct (matches data-secure-code in your old snippet). The wrong et value silently sends data to a non-existent account.
Page views appear but orders don’tEnsure your Order Completed event sends order_id and revenue. etracker requires a unique et_tonr to record an order.
Wrong geo / all traffic from one locationConfirm the visitor IP is being forwarded. Signal sends it as X-Forwarded-For; check no upstream proxy is stripping it.
Cookies set despite no consentConfirm the consent category is mapped in Signal so et_cblk=1 is sent when marketing consent is absent.
Revenue looks wronget_tval must be net turnover with a period decimal separator and two decimals; check the revenue property format.
Webtrendseconda