Troubleshooting

Common issues and how to fix them.

"Awaiting the first event"

Your dashboard shows this when no events have been received yet. Check these things:

  1. Is the script installed? Open your site, right-click > View Source, and search forattribu. You should see the script tag.
  2. Is the website ID correct? The data-website-id must match your site's UUID in Settings > General.
  3. Is the domain correct? The data-domain must match your actual domain.
  4. Are you on localhost? Tracking is disabled on localhost by default. Add data-allow-localhost="true" to test locally.
  5. Is an ad blocker active? Some blockers block requests to attribu.tech. Try disabling it or proxy the script.
  6. Check the browser console. Open DevTools > Console and look for errors related to the script or network requests to /api/events.

Events show but no revenue

  • Is Stripe connected? Check Settings > Revenue. You should see "Connected" in green.
  • Are you passing the visitor ID? Your Stripe Checkout must includeattribu_visitor_id in the session metadata. See Stripe integration.
  • Using Payment Links? Make sure your success page URL includes?session_id={CHECKOUT_SESSION_ID} so the pixel can detect it.
  • Check the webhook. Go to Stripe Dashboard > Webhooks and verify the attribu.tech endpoint is receiving events and returning 200.

Revenue is attributed to "Direct"

This means the visitor had no UTM params or referrer on their first visit. Common causes:

  • The visitor typed your URL directly or used a bookmark
  • UTM parameters were stripped before reaching your site (some link shorteners do this)
  • The visitor first visited from a channel that doesn't set a referrer header (some email clients)
  • The pixel wasn't installed when the visitor first arrived

Visitor count seems low

  • Bot filtering: attribu.tech filters out bots, crawlers, and headless browsers automatically
  • Iframe blocking: Events from iframes are ignored
  • Opt-out: Check if localStorage.attribu_ignore is set to "true" in your browser
  • Ad blockers: Visitors with ad blockers won't be tracked unless you proxy the script

Browser shows as "unknown"

This usually happens when someone opens your link from an in-app browser (Twitter, Instagram, LinkedIn, etc.). attribu.tech now detects these and labels them accordingly (e.g. "X/Twitter App", "Instagram App"). If you still see "unknown", the user agent string is unrecognizable.

Cross-domain tracking not working

  • Make sure the pixel is installed on both domains with the same data-website-id
  • Add the second domain to data-allowed-hostnames or in Settings > General > Additional Domains
  • The visitor must click a link between domains (direct navigation won't carry the visitor ID)
  • Check that the link URL contains _att_vid parameter after clicking

Affiliate commissions not appearing

  • Is the affiliate link correct? It should be yourdomain.com?via=CODE
  • Is the affiliate active? Pending or rejected affiliates don't earn commissions
  • Is the visitor ID passing through checkout? Same as the revenue troubleshooting above
  • Is recurring enabled? If disabled, only the first purchase creates a commission

Excluding yourself from tracking

To exclude your own visits from the dashboard, open your browser console on your site and run:

localStorage.setItem("attribu_ignore", "true");

To re-enable tracking:

localStorage.removeItem("attribu_ignore");

Still stuck?

If none of the above helps, check the browser DevTools Network tab for failed requests to/api/events and inspect the response. If the issue persists, reach out with your site ID and a description of the problem.

Copied