Session Enrichment
Automatically enrich events with session context — UTM parameters, landing page, referrer, and device data.
Overview
MRKT Mesh's data layer captures session-level context on every event. This data travels with the event through server-side delivery, so your destinations receive rich attribution data even for webhook-based events like purchases and refunds.
Data Captured
| Field | Description | Example |
|---|---|---|
| utm_source | Traffic source | facebook, google |
| utm_medium | Marketing medium | cpc, email, social |
| utm_campaign | Campaign name | spring_sale_2026 |
| landing_page | First page visited | /collections/new |
| referrer | Referring URL | google.com |
| fbp / fbc | Meta click/browser IDs | fb.1.1234... |
How It Works
The tracking script reads UTM parameters from the URL and stores them in a first-party cookie. When a purchase webhook arrives, MRKT Mesh matches the order to the stored session using the customer identifier, then enriches the server-side event with the original session context.
Using Session Data in Destinations
Session fields are passed through to each destination in their native format. For example, Meta receives fbc and fbp values, GA4 receives UTM parameters as event params, and Klaviyo receives them as event properties.