Skip to main content
Test one visitor journey through the campaign. Keep the campaign, test time, and final page URL. An ad click does not always produce a tracked visit or offer click.

​
Decide which event should exist

For an offers-only redirect, Visits = 1 and Clicks = 0 can be the correct result.

​
First rule out the report scope

  1. Open Live Visits for the campaign and a date range that includes the test time.
  2. Check the reporting timezone and remove optional filters.
  3. Refresh the report.
  4. Compare the visit with the campaign report for its original visit date. Include archived entities in that report when checking an archived campaign.
If the visit appears in Live Visits, check the campaign report’s dates and filters. If it is missing, follow the test for your tracking mode below.

​
Test arrival in redirect mode

Copy Tracking link from the saved campaign and open it. Check that it uses your tracking domain and reaches the intended destination. Check that the traffic source uses this link. If the tracking domain does not open or HTTPS fails, check the domain configuration. If the tracker returns an error, save its HTTP status and response. Check the campaign ID, saved destination, and active paths. Your test visit may match a different rotator rule than expected. Check Errors around the same time and keep the browser’s request details if the issue persists.

​
Test arrival with a tracking script

Check that the page is in the campaign and has the complete Include in <head> snippet from 4. Finish. Open Traffic URL and check Live Visits.
If the visit is still missing, open the landing or offer page with browser developer tools. Use the Network panel:
  1. Check that the script loads from the intended tracking domain. Inspect blocked requests and console errors.
  2. For a journey with several pages, install the same script on the first page and every page with offer buttons. Those pages must share the same scheme, hostname, and port.
  3. Retest through Traffic URL and check Live Visits. For a custom integration, add an error handler.
Open Traffic URL to start a new visit. Use ordinary site links when continuing the same journey across pages.If page code changes the address or removes tracking parameters, place the tracking snippet before that code. Test the page, not the script URL alone.

​
If visits exist but the landing CTA produces no click

Check the button’s HTML against the campaign’s generated setup. With Direct script, it should use the tracking domain’s /click URL or data-dtp-link. If the button still contains the original tracker URL or # after the page loads, check that the script loaded successfully. Buttons added or changed by a popup or page builder need an explicit generateLinks() call after the update. Follow Connect buttons added later. If one button action records several clicks, check for an extra registerClick() call in custom page code. Call it once per action. Retest from the campaign’s current Traffic URL or Tracking link. Click the CTA and check Live Clicks.

​
What a successful retest establishes

For a landing flow, find the visit in Live Visits and the CTA click in Live Clicks for the same campaign. Check the campaign report for the visit date. If the next stage is missing, continue with Missing conversions. For smaller differences between systems rather than a completely missing step, use Numbers do not match.