Events Not Showing Up

If your PixelsCleared dashboard shows zero events, work through these checks in order.

1. Verify the Script Is Loaded

Open your website in a browser and check the Network tab in developer tools:

1. Press F12 to open developer tools.
2. Switch to the Network tab.
3. Reload the page.
4. Filter for pixelscleared in the network search box.

You should see a request to https://track.yourdomain.com/pixelscleared.js with a 200 status. If you see a 404 or Failed status, the script URL does not match your gateway configuration.

Common causes:

• The subdomain in the script tag does not match the subdomain you set up. Check Gateway > Settings for the correct domain.
• The DNS CNAME has not propagated yet. DNS changes can take up to an hour.
• The script tag is missing from the page. Verify it is present in the HTML source.

2. Confirm DNS CNAME Is Resolving

Open a terminal and run:

dig track.yourdomain.com

The answer section should show a CNAME pointing to gateway.pixelscleared.com. If it shows an A record, the wrong record type was created. See DNS CNAME Not Verifying for detailed steps.

3. Check That Consent Is Being Detected

The PixelsCleared widget stays dormant until consent is granted. Open your website and:

1. Accept your consent banner.
2. Open the browser console (F12 > Console tab).
3. Look for any messages from the PixelsCleared widget.
4. Check if a consent cookie is being set by your CMP (Cookiebot, OneTrust, CookieYes, or Complianz).

If no consent cookie is being set, the widget will not send events. Verify that your consent management platform is installed and configured correctly.

You can also grant consent manually for testing by running this in the browser console:

window.PixelsCleared('consent', true);

If events start flowing after manual consent, the issue is with your CMP integration, not with PixelsCleared.

4. Check for JavaScript Errors

Open the browser console (F12 > Console tab) and look for any red error messages. Common issues:

• CORS errors -- The script tag URL uses a different domain than what is configured in your gateway. Make sure the subdomain matches exactly.
• Mixed content -- Your site uses HTTPS but the script tag uses HTTP. The script URL must always use HTTPS.
• Syntax errors -- The script tag was modified or corrupted during copy-paste. Remove and re-add the script tag from Gateway > Settings.

5. Disable Ad Blockers

Ad blockers and privacy-focused browser extensions can block the PixelsCleared script or the outbound event requests, even though they are sent to your own domain.

To test:

1. Disable all browser extensions, especially ad blockers (uBlock Origin, AdBlock Plus, Brave Shields).
2. Reload the page.
3. Accept consent and trigger an event.

If events appear after disabling extensions, your visitors using ad blockers may not send events either. This is expected behavior and not something PixelsCleared can override.

6. Verify Events Are Triggering

The widget automatically captures page views. For custom events (form submissions, button clicks), make sure the tracked actions are actually firing on your page. Check your browser console for any errors related to event listeners or form handlers.

Still Not Working

If none of these steps resolve the issue:

1. Go to Gateway > Settings and verify your API key matches the one shown in the dashboard.
2. Check that your tenant status is Active (not Inactive).
3. Contact support at pixelscleared.com/contact with your tenant subdomain and a description of what you have checked.