Troubleshooting
Start each check with debug mode. It writes each event, its checks and the response in the browser console:
lg('debug', true);With the npm client, call lg.debug(true).
QuickPipe shows no events
- Open your page and open the browser console.
- Look for the network requests to
in.quickpipe.ai, or to your own endpoint. - If there are no requests, make sure that the script tag is on the page and that
data-keyhas your publishable key. - If the requests fail with status
401, copy the key again from QuickPipe under Settings, then Tracking.
An ad blocker stops the events
Some ad blockers stop requests to analytics domains. Send the events through an endpoint on your own domain, and set it in data-endpoint.
The events have no visitor ID
The visitor did not give consent, or your consent tool does not tell the SDK.
- Make sure that your consent tool sets Google Consent Mode v2, or uses
Cookiebot,CookieYesorOneTrust. - If you use a different tool, set
data-consent="manual"and calllg('consent', 'granted')after the visitor accepts.
Safari forgets the visitor after 7 days
Safari keeps cookies that a script sets for a maximum of 7 days. A subdomain that points to QuickPipe does not help. Send the events through a path of your website, and set it in data-endpoint. Refer to Use a first party endpoint.
The SDK drops an event
Debug mode shows the reason. Make sure that the event obeys these rules:
- The name has only
atoz,0to9and_ . : -, and a maximum of 100 characters. - The name is not
identify,linkorprofile, and it does not start withsystem.. - The properties have a maximum size of 32 KB, a maximum depth of 5 and a maximum of 200 keys.
The console shows an error about a secret key
A secret key lg-sec-live-… is on a page. The SDK refuses it. Use the publishable key lg-pub-live-… in the browser, and delete the secret key from the page. Then make a new secret key in QuickPipe, because the old key is not secret now.
The console shows a Content Security Policy error
Your policy blocks the script or the requests. Add https://cdn.jsdelivr.net to script-src and https://in.quickpipe.ai to connect-src. Refer to Privacy and security.
The console shows an integrity error
The integrity hash does not agree with the file at the URL.
- Make sure that the URL has the same version as the hash.
- Copy the complete script line again from QuickPipe.
- Do not use an
integrityhash with a URL without a fixed version.