Skip to main content
Attribution needs three things: a captured campaign touchpoint, a preserved visitor journey, and a conversion that can be matched back to that journey.

​
1. Check the landing event

Open the visitor’s first relevant pageview. Confirm the landing URL captured the expected UTM parameters or platform click ID. If the parameter is absent from the actual landing URL, Datalyr cannot recover it later. If every paid visit is missing campaign data, review ad destination URLs, redirects, consent behavior, and tracking installation. Redirects must preserve query parameters.

​
2. Follow the identity

Check whether the anonymous visitor ID remains stable through the journey and whether the user is identified when known.
  • A new ID after every page suggests storage or initialization problems.
  • A domain change can break the journey without cross-domain tracking.
  • A web-to-app handoff needs an explicit identity or campaign bridge.
  • A hosted checkout needs supported metadata or customer matching.

​
3. Inspect the conversion

Confirm the revenue or conversion event contains a compatible visitor, user, customer, or transaction identity. An event can be collected correctly but remain unattributed when it cannot be joined to the earlier visitor.

​
4. Run a clean test

  1. Open a private session with a unique UTM campaign.
  2. Land on the final destination URL.
  3. Complete the same cross-domain, checkout, or app path as a customer.
  4. Trigger a test conversion.
  5. Inspect the full journey in order.
Use a unique campaign value so the test is easy to find.
Successful delivery to an ad platform does not prove Datalyr has a complete journey. Delivery and attribution are separate stages.