Web Tracking Troubleshooting

Use this page when your website does not send events to Vendo. Start with the browser check. It tells you which section applies.

Check the Browser First

1. Open your website.
2. Open the browser’s developer tools.
3. Click the Network tab.
4. Filter the requests by collect.
5. Load a page on your website.

Compare the result with this table:

No Request Is Sent

Check these causes in this order:

1. Make sure that the snippet is on the page. View the page source and search for vendo('init'.
2. Make sure that the browser loads https://cdn.vendodata.com/sdk/v1/vendo.js. An ad blocker or a content security policy can stop the file.
3. If your site uses a consent tool, accept analytics cookies. With waitForConsent, the SDK holds events until the visitor gives consent. See Consent Management.
4. Wait 5 seconds, or leave the page. The SDK sends events in batches.

If your content security policy blocks the files, allow these hosts:

• script-src: https://cdn.vendodata.com
• connect-src: the tracking host in your snippet

The Key Is Not Recognized

The response 401 with invalid_write_key means that the tracking host does not know the write key in the snippet.

1. Open the tracking source in Vendo.
2. On the Overview tab, find Installation Snippet.
3. Click Copy.
4. Replace the complete snippet on your website with the new copy.

Do not edit the key or the host in the snippet by hand. Each workspace has its own tracking host. A key works only with the host in its own snippet.

If the tracking source is not Active, Vendo rejects its events. Open the Settings tab and turn on Active.

The Domain Is Not Allowed

The response 403 with origin_not_allowed means that your tracking source accepts events only from its allowed domains.

1. Open the tracking source in Vendo.
2. Click the Settings tab.
3. In Allowed Domains, add the domain of your website, for example example.com.
4. Save the settings.

Enter the domain only, without https://. Add each domain and subdomain that sends events, for example www.example.com and shop.example.com.

Too Many Events

The response 429 means that the site sends more events than the rate limit of the tracking source. You can see the limits in Source Details on the Overview tab. If your site needs a higher limit, contact Vendo support.

Events Do Not Show in Vendo

The response 202 means that Vendo accepted the events.

1. Open the tracking source in Vendo.
2. Click the Live Events tab.
3. Load a page on your website.

If the event shows in Live Events but not in a destination, check Tracker Health on the Overview tab. Then check the destination under Destinations on the same tab. If the problem continues, contact Vendo support with the time of the test and the tracking source name.

The App Shows a Warning Above the Snippet

Vendo checks the snippet before you install it. It sends a test request to the tracking host with your write key. The request does not write data.

If the check fails, the app shows Events from this snippet will not arrive above the snippet. Vendo alerts its team automatically. Contact Vendo support if the warning does not go away after 1 hour.

You can install the snippet while the warning shows. Events start to arrive when the tracking host accepts the key.

Page Views Are Missing or Duplicated

The SDK does not send page views automatically. Each call to vendo('page') sends 1 page view.

• Page views are missing after the first page. Your site is a single-page app. Call vendo('page') after each client-side route change. See the Quickstart.
• The first page view shows 2 times. The snippet sends the first page view, and a framework component sends it again. Remove vendo('page') from the snippet, or stop the component from sending the first page view.
• Every page view shows 2 times. The snippet is on the page 2 times, for example in the layout and in Google Tag Manager. Remove 1 copy.

Related

• Web Tracking Quickstart
• JavaScript SDK reference
• Ingestion API reference