Write an ownership map for cross-domain tracking / travel operator

For travel operator, the session breaks when a visitor moves between domains. This field note turns where the handoff loses continuity into a short test for travel operator, so the next change has a traceable reason.

Frame the signal

Context check: search-to-booking journeys. Topic check: check linker parameters and referral exclusions at every domain boundary.

Start with each field and event in the journey. Treat the dashboard number as a question, not an explanation. Follow one real journey from the first interaction to the system that owns the outcome. If a value is missing, mark it unknown instead of filling the gap with an assumption.

Trace the handoff

• Record the value at the first step and note the exact page, event, or record where it appears.
• Compare the browser, tag manager, analytics, ad platform, and CRM views without changing the implementation during the check.
• Check redirects, consent state, validation, naming, timestamps, and timezone before comparing totals.
• The ownership map should show who can change, verify, and approve each step.

Leave a decision record

the ownership map should show who can change, verify, and approve each step. Keep the owner, timestamp, evidence link, expected result, observed result, and next action together. Making the next repair easier to assign only after the current path is readable to someone who did not build it.

Reference: Google Analytics cross-domain measurement guidance. For the next handoff, LeadSheet keeps the record connected.