Skip to main content

Sessions and the touch

The anonymous id​

A first-party cookie evx_id on the site's own domain, 13 months, with a value like evx_web_8f21c0. It is set only with analytics consent and travels as anonymousId on every call, becoming the device identifier on the activities. Devices are never joined across organisers.

Sessions​

Every call carries context.sessionId. The first call of a session is flagged context.sessionStart and carries the touch; the server derives started_session from it. A session ends after 30 idle minutes, or at once when the visitor arrives with new campaign parameters, so a second campaign on the same day gets its own session.

The touch​

On the first call of a session the SDK captures how the visitor arrived:

  • the UTM parameters as typed, in context.campaign (source, medium, name, term, content);
  • the ad click ids the server's configuration lists (gclid, fbclid, …), read from the address or a cookie, only with ads consent;
  • the landing page, query included, and the referrer;
  • the consent snapshot.

The server stores this on started_session and, through the shop, it ends up as the touch block on the order and its tickets, so revenue per campaign needs no join. Nothing is normalised on the way: "paid social" is a read-time view in the CRM.