econda

Datafly Signal delivers events to econda Analytics (part of the DYMATRIX group) server-to-server. Signal replays econda’s emos3 “emos data” beacon to the econda logging service (els), so page views, product interactions and orders are collected reliably even when the browser blocks the client-side emos3.js tag.

Prerequisites

Before configuring econda in Signal you need:

An active econda Analytics account (DYMATRIX Cockpit).
Your econda client key, shown in the econda interface under Configuration → Analytics JS Library (the same value the browser loader script passes as client-key="…").

econda identifies your account by the public client key — there is no separate secret API token on the logging endpoint. Signal sends the client key as the emc parameter on every event.

Configuration

Field	Required	Description
`client_key`	Yes	Your econda client key from Configuration → Analytics JS Library. Sent as the `emc` parameter.
`siteid`	No	Name of the site being measured (the emos `siteid` field). Use when one account collects from several sites.

Configure in Signal

Add the integration

Go to Integrations → Add Integration → econda.
Choose the Retail preset (page views, product views, cart events and orders).

Enter your credentials

Paste your client_key.
Optionally set siteid.
Select the consent category that should gate analytics collection (typically analytics).
Click Save.

API Endpoint

POST https://www.econda-monitor.de/els/logging?emc={client_key}

The request body is the econda emos data object as JSON. Signal forwards the visitor’s IP (X-Forwarded-For) and User-Agent as request headers so econda attributes geo and device to the real visitor rather than the Signal server.

Identity Signals

econda matches visitors and sessions from the emos data object:

Signal	emos field	Description
Visitor ID	`vid`	Stable visitor identifier. Signal sends its first-party `anonymous_id`.
Session ID	`sid`	econda session identifier (default 30-minute timeout).
Customer ID	`emuid`	Logged-in customer / user id, from `datafly.identify()`.
Hashed email	`ememailhash`	SHA-256 of the visitor’s email.

When a user is identified via datafly.identify(), their email is normalised (trimmed, lower-cased) and SHA-256 hashed by Signal before delivery. Raw email never leaves your infrastructure.

datafly.identify("customer-123", {
  email: "jane.doe@example.com"
});

Event Mapping

Signal event	econda emos	Notes
`page`	`content` page view	Page path, title and category.
`Product Viewed`	`ec_Event` type `view`	Product detail view.
`Product Added`	`ec_Event` type `c_add`	Add to cart.
`Product Removed`	`ec_Event` type `c_rem`	Remove from cart.
`Checkout Started`	`orderProcess`	Checkout step marker.
`Order Completed`	`ec_Event` type `buy` + `billing`	Order with line items and totals.

Product events populate the ec_Event array (pid, sku, name, price, count, group). Orders also populate the billing array: [orderId, customerId, location, total, currency, delivery, deliveryCost, payment, paymentCost].

Example: Order Completed

Datafly.js call:

datafly.track("Order Completed", {
  order_id: "ORD-001",
  revenue: 129.99,
  currency: "EUR",
  product_id: "SKU-A",
  product_name: "Widget",
  price: 49.99,
  quantity: 2
});

emos payload sent by Signal:

{
  "content": "/checkout/confirmation",
  "siteid": "myshop.com",
  "vid": "a1b2c3d4e5f6",
  "sid": "s-789",
  "ememailhash": "5e884898da...",
  "billing": ["ORD-001", "customer-123", "", 129.99, "EUR"],
  "ec_Event": [
    { "type": "buy", "pid": "SKU-A", "name": "Widget", "price": 49.99, "count": 2 }
  ]
}

Signal maps your canonical marketing-consent state to econda’s privacy flag (emos_privacy): 3 for full tracking when consent is granted, 1 (suppressed) otherwise. Classify your CMP categories in Settings so the flag follows every event.

Testing

Trigger events on your site (or use Signal’s event debugger to replay one).
Open the real-time monitor in your econda Cockpit.
Confirm page views and product/order events arrive with the correct content, ec_Event type and billing values.

Troubleshooting

Problem	Solution
No events in econda	Check the `client_key` is correct (Configuration → Analytics JS Library) and that the account is active.
Orders missing line items	Ensure `Order Completed` carries `product_id`, `price` and `quantity`; econda needs at least one `ec_Event` of type `buy`.
Wrong geo / device	Confirm Signal is forwarding the visitor IP and User-Agent (default for this integration).
Visitors not de-duplicated	Make sure `anonymous_id` (→ `vid`) is stable across sessions.

etracker Adjust