Web Tracking SDK

SDK and ingestion API: The browser SDK sends events to the tracking host configured for your workspace. Vendo validates, normalizes, and routes accepted events into the configured data path.

Event Types

The SDK can also capture session context, campaign parameters, click identifiers, referrer, locale, and device context. The exact payload depends on initialization options, browser availability, and consent.

Automatic vs Explicit Tracking

Vendo does not globally record every click, scroll, or form field. Tracking is explicit and predictable:

• page is never sent automatically. Since SDK 0.2.0, init does not fire a page view. Call vendo('page') after init on the initial page, and again on every client-side route change. The trackPageViews / pageView options are deprecated no-ops.
• Clicks, form submissions, and visibility impressions are opt-in through data-vendo-* attributes.
• Business events, user identity, groups, and aliases require explicit SDK calls.

Every accepted event includes a message ID, timestamp, anonymous ID, optional user ID, and session ID. It also includes page metadata, browser/device metadata, attribution data, and a structured context envelope. See the JavaScript SDK reference for the complete payload shape.

Data Flow

1. The generated SDK snippet loads on your site.
2. Calls made before the full library loads are queued.
3. The SDK batches eligible events and sends them to the configured tracking host.
4. The ingestion API authenticates the write key and validates each payload.
5. Accepted events are normalized and routed to the workspace’s configured destinations.

A first-party endpoint can improve control and resilience, but it does not override browser settings, content blockers, consent choices, or privacy obligations.

Implementation Rules

• Copy the snippet and host from Data → Integrations → Web Tracking. Do not assemble production credentials from examples.
• Define event names and properties in a tracking plan before broad deployment.
• Call identify only when the application has a stable, permitted user identifier.
• Keep write keys out of server logs and public documentation, even though browser keys are not equivalent to administrative API keys.
• Test consent denied, anonymous, identified, duplicate, and retry scenarios.

Verify

Use browser network tools to inspect /collect, Vendo’s live-event or diagnostic views where enabled, and the final destination. Verify event count, name, timestamp, identity, consent, and important properties at every step.

Related

• Quickstart
• JavaScript SDK reference
• Declarative tracking
• Ingestion API reference
• Self-hosting