Web Tracking

Collect page views, events and user identities from your website with first-party Web Tracking.

Last reviewed September 23, 2026

Web Tracking is the layer that collects browser events for Vendo. It receives eligible page views, custom events and identity calls from your website. It routes accepted payloads through the tracking configuration of the workspace.

In the app, open Data. Then click Web Tracking in the Integrations group.

Setup

Create a tracking source for each website and environment.
Copy the installation snippet of the tracking source.
Add the snippet to the <head> of your website.
Send page views on client-side route changes, events and identify calls.
Check the events on the Live Events tab of the tracking source.

The Quickstart gives the full steps. Other ways to install:

Google Tag Manager
AI coding agent: a prompt for Claude Code, Cursor or Codex
Next.js, Vue and Nuxt
Declarative tracking: track clicks without JavaScript
JavaScript SDK reference

If events do not arrive, see Troubleshooting.

What gets tracked

Event type	Purpose
`page`	Page views with URL, title, and referrer
`track`	Custom events with properties
`identify`	Associate anonymous IDs with known user traits
`group`	Account- or organization-level properties
`alias`	Link two user IDs together
`rule`	Rule events that Vendo adds (see below)

Tracked identities can contribute to Customer 360 and downstream transformations. This occurs after you configure the necessary identity mappings and processing paths.

Rule Events

Vendo examines each visit (session) of a visitor. When a rule matches for the first time in a session, Vendo adds one event to your data. You do not add code for these events.

Event	Vendo adds it when
`Session Engaged`	The visitor views 3 or more pages in the session.
`High Intent Page Viewed`	The visitor views a page that starts with `/pricing`, `/demo`, `/contact`, `/signup`, `/register`, `/book`, `/schedule`, `/trial` or `/get-started`.
`Sales Ready`	The visitor views a high-intent page and 5 or more pages in the session.
`Returning Visitor`	The visitor had a different session before, on the same browser, in the last 400 days.

Each rule event:

Occurs 1 time for each rule in a session.
Has the same visitor, user, session, page and campaign data as the event that caused it.
Has the event type rule and the properties rule, page_count, session_count and trigger_event_id.
Goes to the same destinations as your other events.

Sessions and attribution touchpoints do not include rule events. You can use a rule event as a conversion in an attribution model. Ad platform conversion uploads do not include rule events.

The Rules tab of the tracking source shows the rules. You cannot change the rules.

Check One Visit

To see all the events of one session:

Open the tracking source and click the Live Events tab.
Click an event, then click Show this session. Or type the session ID in Filter by session ID and click Show session.

Vendo shows the events of the session from the last 7 days. For 30 minutes after the last event of the session, Vendo also shows a summary: the pages, the duration and the rule events. Click Back to live to show all events again.

Destinations

Depending on the workspace configuration, Vendo can route accepted events to:

Vendo managed warehouse (default)
External destinations configured in your workspace

Verify the routing in the Web Tracking configuration and in the destination. When the ingestion API receives an event, this does not prove that the destination received it.

Where Vendo Stores Tracking Data

When storage is on in the Settings tab of a tracking source (Store data in Vendo, or Store data in and the name of your warehouse), Vendo writes its events to BigQuery:

Your workspace uses	Location of the tables
The Vendo warehouse (default)	A dataset for each tracking source, named `wt_` followed by the tracking source ID
Your own BigQuery warehouse	Your Vendo dataset, in tables that start with `wt_`, the tracking source ID and `_`, for example `wt_1a2b..._events`

Vendo creates each dataset in the data location of your workspace.

If your workspace changes to your own warehouse, Vendo writes new events to your warehouse. Events from before the change stay in the Vendo warehouse.

The Tables tab of the tracking source shows the tables in their current location. The Destinations list shows the name of the warehouse.

Self-hosting

If your team needs to run the ingest API on its own infrastructure, see Self-hosting.

Tracking SDK quickstart
Web Tracking troubleshooting
Customer 360: identity resolution for tracked users