Web Tracking Quickstart

Create a tracking source, add the generated snippet to your website, and check that Vendo receives the events.

Last reviewed September 23, 2026

This guide takes you from a new tracking source to events in Vendo. It takes about 10 minutes.

1. Create a Tracking Source

In Vendo, open Data.
In the Integrations group, click Web Tracking.
Click Add Tracking Source.
Enter a Source Name, for example the name of your website.
Select the Environment: Production, Staging or Development.
Optional: in Allowed Domains, add each domain that can send events, for example example.com.
Click Create Source.

Use one tracking source for each website and environment. Do not use your production source on a staging site.

If you add allowed domains, Vendo rejects events from all other domains. Enter the domain only, without https://. If you leave the list empty, Vendo accepts events from all domains.

2. Copy the Snippet

The Install step shows your Write Key and the installation snippet.

Click the Vendo CDN tab.
Click Copy.

You can copy the snippet again later. Open the tracking source and find Installation Snippet on the Overview tab.

The snippet contains your write key and the tracking host for your workspace. Always copy the complete snippet. Do not combine a key or a host from a different tracking source.

Note: If Vendo shows the warning Events from this snippet will not arrive above the snippet, do not install it yet. See Troubleshooting.

3. Add the Snippet to Your Website

Paste the snippet into the <head> of every page, or into the shared layout of your site.
Publish the change.

Add the snippet 1 time only. If you add it 2 times, Vendo records each page view 2 times.

Other ways to add the snippet:

Google Tag Manager
Next.js, Vue and Nuxt
An AI coding agent, for example Claude Code, Cursor or Codex

4. Send Page Views on Route Changes

The snippet ends with vendo('page'). This call sends the page view for the page that loads first. The SDK does not send page views automatically.

If your site is a single-page app (SPA), the URL can change without a new page load. Call vendo('page') after each client-side route change:


vendo('page');

The framework guides show where to add this call. If your framework component also sends the first page view, remove vendo('page') from the snippet. If you do not remove it, Vendo records the first page view 2 times.

5. Send Events and Identify Users

Send an event when a user does an important action:


vendo('track', 'Signup Completed', { plan: 'growth' });

After a user signs in, identify the user with a stable user ID from your system:


vendo('identify', 'user_123', { plan: 'growth' });

Do not use an email address as the user ID. Send the email address as a trait only if your consent rules allow it.

You can use the call form vendo('track', ...) at all times, before and after the SDK loads. The method form vendo.track(...) works only after the SDK loads.

6. Check That Vendo Receives the Events

Open your website.
Open the tracking source in Vendo.
Click the Live Events tab.
Load a page on your website.
Look for the Page Viewed event in Live Events.

You can also check the request in the browser:

Open the browser’s developer tools.
Click the Network tab.
Filter the requests by collect.
Load a page on your website.
Check that the response status is 202.

The Run test button on the Overview tab sends a test event through the Vendo pipeline. It does not write data. It does not check your website.

If you do not see events, see Troubleshooting.

Production Checklist

The snippet is on every page, 1 time only.
Each environment has its own tracking source.
Single-page apps send vendo('page') on each route change.
Consent behavior is tested before and after opt-in and opt-out. See Consent Management.
Event names and properties match your tracking plan.
User IDs come from your own system and do not change.