Help Center

Find answers fast. Browse categories or search our guides and troubleshooting.

Help/Integrations & tracking/Debug tracking with DevTools
Debug tracking with DevTools
Updated 2026-04-11

Open DevTools

Use the Network tab and filter by your tracking endpoint or “track”. You should see requests returning HTTP 200.

What to inspect

  • Request payload includes expected properties (domain, campaign_id).
  • Response is 200 (or a known success response).
  • No CSP or CORS errors in Console.

Common blockers

  • Ad blockers
  • Strict content security policy
  • Browser privacy settings

Tip

Always test in an incognito window without extensions to isolate the issue.

Was this helpful?
Views 22 Helpful 0 Not helpful 0
Back to Integrations & tracking All categories