Skip to main content
If a report looks incorrect, check these items in order:
  1. Confirm that you are in the correct workspace and viewing the intended resource.
  2. Check the selected date range and comparison period.
  3. Visit the short URL rather than its destination directly when testing clicks.
  4. For leads and sales, confirm conversion tracking is enabled and the event uses the correct workspace publishable key or integration.
  5. Allow for browser privacy controls, referrer removal, duplicate protection, and processing time.
Folder totals depend on link membership, and static QR codes do not produce scan analytics. If the difference remains, send support the resource ID, time range, and an example timestamp. Do not send API keys or customer secrets.

​
Click totals differ from another service

Other systems can count page loads, ad clicks, bot traffic, previews, or refreshes differently. Compare the same time zone and period, then account for duplicate filtering, privacy tools, and the destination’s own redirect chain.

​
A conversion is missing

Verify that conversion tracking was enabled on the original link, the visitor used that link before converting, the publishable key was valid, and the event came from an allowed origin. Check the event’s external identifier, currency, and timestamp in the sending integration.

​
Audience data is unknown

Country, city, browser, device, platform, and referrer depend on request data. An unknown value is expected when that data is unavailable and cannot always be recovered later. When contacting support, include the stable resource ID, event type, exact time with timezone, and expected result. A screenshot of the filter and date range is more useful than a cropped total alone.