Web Tracking Quickstart
Install Vendo's generated snippet, send a test event, and verify the complete delivery path.
Last reviewed July 25, 2026
1. Copy the Generated Snippet
- Open Data → Integrations → Web Tracking.
- Create or select the write key for the site and environment.
- Copy the complete generated snippet, including its tracking host.
- Add it once in the site’s
<head>or shared application layout.
Use the generated snippet as a single contract. Do not combine a key, host, or SDK URL from different workspaces or environments.
The generated snippet ends with an explicit vendo('page'); call. Since SDK 0.2.0, init does not send a page view automatically — keep that call in place, and call vendo('page') again on every client-side route change in single-page apps.
2. Send a Test Event
After the snippet loads, send a distinctive event from a test page:
vendo('track', 'Documentation Test', {
implementation: 'web',
test_id: 'replace-with-a-unique-value',
});After a user has authenticated and consent permits identification:
vendo('identify', 'your-stable-user-id', {
plan: 'example',
});Do not use a real email address or other personal data for an implementation test unless the test is approved for that data.
3. Verify the Path
- Open the browser’s Network panel.
- Find the request to the configured tracking host’s
/collectendpoint. - Confirm the response is successful and reports the event as received.
- Use the Web Tracking diagnostics or live-event view if enabled.
- Find the unique
test_idin the final destination. - Check that the timestamp, anonymous ID, user ID, consent state, and properties are correct.
If the browser request succeeds but the event is missing downstream, investigate ingestion routing and destination delivery separately.
Debug Temporarily
The SDK supports diagnostics such as debug: true and debugState() when included by the generated configuration. Enable browser logging only during implementation, avoid logging personal data, and turn it off before production unless it is deliberately required.
Production Checklist
- the snippet appears once on every intended page;
- development and production use different approved keys where required;
- consent behavior is tested before and after opt-in or opt-out;
- event and property names match the tracking plan;
- retries do not create unintended duplicates;
- known-user identification uses a stable source-of-truth ID;
- monitoring has an owner.