Customer journeys
Follow the permitted touchpoints around a purchase.
On this page
Open a journey
Use the revenue or customer journey report to inspect an authorized customer's recorded marketing and visit history. The API query_customer_journey schema identifies its accepted lookup arguments. Use the supported identifier rather than guessing a visitor-to-customer mapping.
Read it in context
Check source, page and payment timestamps with the site's date scope. A customer can have a verified transaction without a complete visit history. Consent and persistent identification settings determine what can be linked.
Protect personal data
Customer and visitor records can include personal analytics data. Share aggregate reports rather than customer timelines publicly. Only connect agents that should be able to read the selected sites' records.
Troubleshoot missing history
Confirm the payment provider is connected, webhook delivery succeeded, tracking was installed before the visit, identity consent was valid and supported checkout context was passed. Cross-device and refused-consent gaps are expected limits, not grounds to bypass privacy controls.
Related guides
Read visitor identification, revenue attribution and visitor privacy requests.
Still looking for an answer? Try troubleshooting or get in touch.