Install the tag
Place one snippet in the shared site template or tag manager. GitHub access is optional.
X-Ray for SaaS
Build a measurement foundation you can verify.
The tag observes how someone reached and used the site. X-Ray preserves that evidence, keeps consent explicit, and lets you compare attribution models without pretending browser activity proves paid revenue.
The six measurement stages
Stages complete from persisted evidence, not from a checkbox in the browser. Each stage describes measurement X-Ray can verify today.
Preserve acquisition context
Retain UTMs and eligible click IDs and validate landing-page activity.
Define lifecycle events
Name the product actions and milestones that the browser can actually observe.
Set currency and timezone
Keep reporting groups explicit; X-Ray never adds unlike currencies into a fabricated total.
Publish consent
Choose purposes, disclosure, retention, and GPC behavior before collecting eligible identity or surveys.
Verify observed events
Generate a real eligible event and confirm its persisted receipt before trusting the measurement foundation.
Browser evidence stops at the browser.
A page view, checkout click, form submission, or return visit can describe intent and behavior. It cannot prove that an invoice was paid, renewed, refunded, or corrected, so the measurement foundation does not label those browser events as verified revenue.
Observed journey
Eligible pages, sessions, campaign parameters, and governed interaction events form the observed ledger.
Currency boundaries
Minor-unit values remain grouped by currency. Reporting never invents a cross-currency total.
Truthful limits
Missing evidence stays missing. A model can redistribute eligible credit, but it cannot create a paid outcome or a person-level ad view.
Add reported influence without rewriting the journey.
An optional structured survey records what customers say influenced them. Its aggregate results stay separate from observed touches and are combined only with explicit weights.
Structured answers
Bounded options make aggregate reporting inspectable while avoiding free-form identity or contact collection.
Isolated survey
The hosted survey uses short-lived secure cookies, CSRF protection, no-store responses, restrictive security headers, and no Pixel, third-party assets, external links, customer identifiers, or durable bearer token.
Publication requires approval
A production survey remains draft until the disclosure, purpose, retention, and customer-visible wording are approved. Answers are optional customer-reported influence, not deterministic identity or an observed touch.
Inspect attribution and surveys with governed tools.
An agent can read methodology, create and govern a structured survey, read its aggregate report, inspect view-evidence availability, and request observed-plus-reported impact with explicit weights. Site setup remains revisioned and evidence-backed.