Vendo Support Docs
Set up Vendo, connect your data, build models in Data Studio, analyze results and troubleshoot your workspace.
Last reviewed September 15, 2026
Vendo puts your data operations in one workspace. Connect source systems, model trusted data, analyze performance and send approved results to the tools that your team uses.
Start here
| Your goal | Read this first | Outcome |
|---|---|---|
| Ask a question about your data | Agent | Run a grounded query and verify the result |
| Connect a business system | Apps | Add credentials and confirm connection health |
| Import data | Sources | Configure a source, schedule, and first sync |
| Send data to another tool | Destinations | Map and verify a destination delivery |
| Understand available data | Data Model | Learn the events, users, groups and ad data in Vendo |
| Build reusable data logic | Data Studio | Create and run a model |
| See how your data flows | Orchestration | Understand what runs, when, in which order, and why |
| Diagnose stale or failed data | Troubleshooting | Find the root error and retry safely |
Workspace
- Agent (Home in the top menu) investigates data and uses permission-scoped workspace tools.
- Data holds your integrations, your data catalog and your data preferences.
- Reports presents recurring and ad-hoc analysis.
- Data Studio (Studio in the top menu) holds SQL, Python, notebooks, grouping and model outputs.
- SQL Editor gives direct read-only warehouse analysis. It is in Studio.
Data
- Apps: credentials, capabilities and connection state.
- Sources: scheduled, webhook and first-party ingestion.
- Data Uploads: reviewed file-to-table imports.
- Destinations: warehouses, analytics, messaging and advertising delivery.
- Web Tracking: first-party browser events and identity.
- Data Health: make expected data behavior explicit.
- Orchestration: how Vendo schedules, orders and runs the jobs of your sources, models and destinations.
- Data Model: events, users, groups, ad data and custom entities.
- Customer 360: unified customer profiles and calculated properties.
- Identity Merge: how Vendo links the records of one person across sources.
- Auto-Segmentation: find natural customer groups and turn them into audiences.
- Metrics: reusable business definitions.
- Audiences: reusable customer groups for activation.
- Attribution: give conversion credit to the touchpoints before a conversion.
Developers
- API: authenticated account, app, source, integration, model, job and usage resources.
- CLI: terminal workflows against the Vendo API.
- MCP Server: connect an external AI client with read-only or read-write scope.
- Web Tracking SDK: browser SDK setup and reference.
Common workflows
Connect, validate, and transform a source
- Add credentials in Data → Integrations → Apps.
- Create the source.
- Select its data types and its schedule.
- Run a small first sync.
- Inspect the sync in Data → Integrations → Logs.
- Confirm the new tables and fields in Data Catalog.
- Build and validate a model in Studio.
- Before you connect a destination, validate the output.
Troubleshoot a failed sync
- Find the resource and its latest job.
- Read the first error, not only the final retry message.
- Fix the credentials, permissions, schema or mapping.
- Retry a small range.
- Before you expand the run, compare the accepted, rejected and duplicate records.
Account and support
Last updated on