Skip to main content
Run five checks against the published site. The setup is complete when one test person carries a campaign from the landing visit to a delivered conversion.

​
Before you start

You need the published site, a private browser window, and a revenue source already connected. Turn off every ad blocker in the test window.

​
1. Check the visit

Open this URL in a private window. Replace the host with your own.
Open Events and select the newest pageview. Open a second page in the same window. Confirm the new pageview carries the same distinct id.

​
2. Check identity

Pass your database user ID to identify(), not an email address. An email changes, and a changed email creates a second user with a split journey.
Sign in inside the same private window.
Confirm $identify arrives in Events. Open Users and find user_123. Confirm the pageview from step 1 is on that person’s journey.

​
3. Check a product event

Trigger one funnel action.
Open the event in Events. Confirm the properties you sent are present. Use a fixed lowercase name. A name built from button text creates a new event name per button.

​
4. Check revenue

Create one test transaction in the revenue source you connected. A transaction that arrives with no campaign means the payment reached Datalyr but the visitor_id did not. See Missing attribution.

​
5. Check delivery

Don’t stop before this check. Revenue in Datalyr reaches no ad platform until a rule forwards it.
  1. Open Conversions and select manage rules.
  2. Confirm one enabled rule matches your revenue event name and source.
  3. Return to Conversions and find your test transaction.
  4. Open the row and confirm it records a delivery to the ad platform.
Do not enable two rules for one event. Each rule delivers on its own, and the ad platform counts the conversion twice.

​
When a check fails

To read the SDK’s own log, add data-debug="true" to the script tag. Remove it after the test.

​
Next