Integrations / Analytics
econda
Server-side web analytics delivery to econda (DYMATRIX) via the emos3 logging service (els). Maps Signal events to the econda emos data schema — content/page views, ec_Event product interactions (view/c_add/c_rem/buy), and the billing order array — with visitor/session identity and SHA-256 hashed email.
Datafly Signal delivers first-party events to econda server-to-server from infrastructure you control, using a pre-built blueprint that maps your event schema to the payload econda expects.
Why route econda 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 econda receives the complete event stream.
Email hashed before it leaves your infrastructure
Signal normalises (trim and lowercase) and applies SHA-256 inside your own deployment, so econda receives match keys rather than raw personal data.
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 econda attributes the event to the right session.
One consent decision governs every destination
econda 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
add_to_cartbegin_checkoutpagepurchaseremove_from_cartview_itemVertical presets
Retail. 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 econda documentation.
Frequently asked questions
Does Datafly Signal integrate with econda?
Yes. Datafly Signal delivers first-party events to econda server-to-server from infrastructure you control, using a pre-built blueprint that maps your event schema to the payload econda expects. The integration is included in every deployment at no additional cost.
How is server-side econda tracking different from the econda tag?
The econda 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 econda from your server, so delivery does not depend on browser conditions.
What personal data is sent to econda?
Email are normalised and SHA-256 hashed inside your own deployment before delivery, so econda receives match keys rather than raw personal data. Which fields are sent is configured per pipeline.
Which events can Signal send to econda?
The blueprint ships with mappings for add_to_cart, begin_checkout, page, purchase, remove_from_cart, view_item. Any event in your schema can be mapped to econda through pipeline configuration without a code change.
Do I need to keep the econda tag on my site?
No. Signal delivers to econda from the server, so no client-side econda script is required on your site.
Other analytics integrations
Ready to move econda server-side?
See how Datafly Signal delivers first-party events to econda from infrastructure you control, with hashed identity and consent enforcement built in.