Tracking pixel

✅ The first-party chain is live. A visitor id and a session id are set on first touch, carried through Stripe Checkout and a Shopify install link, and matched to the payment. Listing analytics still reads a linked GA4 property for the older storefront report.

What works today

First-party visitors. Web analytics records visitors on your own site from the same /sdk.js snippet that sends usage events. The visitor id (cx_vid) and the session id (cx_sid) are set on first touch. Put them on Stripe Checkout metadata, or call the checkout helper before redirecting, and add ?payment_id= on the success URL. A Shopify install link gets the same cx_vid, cx_sid, and ref. A payment that comes back through that handoff, the payments API, or a payment event is matched to the visit. Refunds are subtracted.

Behaviour, from the CoreX SDK. The snippet autotracks page views, route changes, engaged time, and outbound clicks, and flushes on unload. Those events also power the Usage overview, Session Replay and Web Vitals.

Source attribution, from GA4. Link a GA4 property to an app and Listing Analytics reports sessions and conversion by traffic source, plus a pageview → install funnel. With BigQuery also connected, the nightly keyword rollup attributes App Store search terms through to installs. That report is the storefront view. It is not the first-party visitor chain above.

Referral attribution, from Affiliates. A referral link is attributed to the install it produced, and from there to the revenue that install generated.

Why it matters

Channel performance measured only in installs hides the channel that produces customers who pay. The first-party ids are what join the visit to the payment without a second analytics product in the middle.