econda

Signal sends web analytics events to econda (DYMATRIX Web Analytics) from the server, in econda’s emos data fields.

⚠️

econda documents server-side tracking only on a page behind its customer login; its public tooling is the browser emos3 library. The collection URL below follows a request the analytics agency IT-WINGS published from econda’s server-side tracking page, and the fields follow Commanders Act’s econda destination. Neither is econda’s own publication: confirm the endpoint with DYMATRIX support and test live before relying on it.

Prerequisites

Your econda client key (econda interface: Configuration > Analytics JS Library) and, if one account measures several sites, the site ID DYMATRIX configured for this site.

Configuration fields

Field	Required	Description
`client_key`	Yes	econda client key, the last segment of the collection URL.
`siteid`	No	Measured site name as configured by DYMATRIX support, sent as `siteid`.

API endpoint

POST https://www.econda-monitor.de/json/{client_key}
Content-Type: application/json

{"emosV": "json1.0", "rid": "{event ID}", "vid": "{anonymous ID}", "sid": "{session ID}", "host": "www.example.de",
 "siteid": "example.de", "content": "/shop/shoes", "langid": "de-DE", "camp": "autumn", "source": "google",
 "ip": "203.0.113.7", "ua": "Mozilla/5.0 ...", "hashedvalue": "{sha256 of the e-mail}",
 "ec_Event": [{"type": "buy", "pid": "SKU-1", "name": "Trail shoe", "price": 80, "group": "Shoes", "count": 1}],
 "billing": ["T-1001", "crm-user-7", "", 104.5], "orderProcess": "4_order_confirmation"}

rid, vid and sid are mandatory; an event without a session ID is not sent. hashedvalue is the normalised SHA-256 of the identified visitor’s e-mail address; the raw address never leaves your deployment.

Event mapping (Retail preset)

Datafly event	econda
`page`	page view (`content`)
`view_item`, `add_to_cart`, `remove_from_cart`, `add_to_wishlist`	`ec_Event` per item, type `view`, `c_add`, `c_rem`, `wlist_add`
`begin_checkout`, `add_shipping_info`, `add_payment_info`	`orderProcess` steps 1 to 3
`purchase`	`ec_Event` type `buy` per item and `billing` [order ID, customer ID, location, value]
`search`, `view_search_results`	`search` [[term, result count]]
`login`	`login` [[user ID, 0]]

Only emos fields are sent: event properties the preset does not map are not forwarded.

Default consent category: analytics. Consent is enforced before delivery.

Blueprint

Blueprint version 0.5.0 (not yet tested against a live econda account). One Retail preset.

etracker Index