Vendo Support Docs

Vendo brings data operations into one workspace: connect source systems, model trusted data, analyze performance, and send approved results to the tools where your team acts.

Start here

Workspace

The primary Vendo navigation follows the way work moves from question to action.

• Agent investigates data and uses permission-scoped workspace tools.
• Automations holds trackable work and attached workflows.
• Approvals is the human-review queue for generated recommendations.
• Insights presents recurring and ad-hoc analysis.
• Documents stores durable written context for people and the Agent.
• Memory holds durable context the Agent can use across conversations.
• Timeline records dated decisions, experiments, and annotations.

Data

Open Data in Vendo to work with integrations, definitions, transformations, and data preferences.

Connect and move data

• Apps — credentials, capabilities, and connection state.
• Sources — scheduled, webhook, and first-party ingestion.
• Destinations — warehouses, analytics, messaging, and advertising delivery.
• Web Tracking — first-party browser events and identity.
• Data Uploads — reviewed file-to-table imports.
• Pipelines — operational flow and run state.

Define and transform data

• Data Model — events, users, groups, ad data, and custom entities.
• Data Catalog — discover and understand data assets.
• Metrics Library — reusable business definitions.
• Transformations — SQL, Python, notebooks, grouping, and model outputs.
• SQL Editor — direct read-only warehouse analysis.

Resolve and activate customer data

• Customer 360 — unified customer profiles and calculated properties.
• Identity Resolution — configure identifiers and merge rules.
• Audiences — reusable customer groups for activation.
• Data Quality & Contracts — make expected data behavior explicit.

Planning and activation

• Strategy Builder — capture business context and priorities.
• Measurement and Budget — cross-channel analysis and budget planning.
• Budget Change Requests — review and audit proposed budget changes.
• Signal Recovery — restore server-side conversion signals.

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

1. Add credentials under Data → Integrations → Apps.
2. Create the source and select its data types and schedule.
3. Run a small first sync and inspect Activity Logs.
4. Confirm the new tables and fields in Data Catalog.
5. Build and validate a transformation under Data → Integrations → Transformations.
6. Validate the output before connecting a destination.

Review and execute a recommendation

1. Open Approvals and read the evidence and proposed action.
2. Confirm the account, resource, time range, and expected impact.
3. Approve or dismiss the recommendation.
4. Follow any resulting work in Automations and Activity Logs.
5. Record the outcome in Timeline or preserve the analysis in Documents.

Troubleshoot a failed sync

1. Find the resource and latest job.
2. Read the first error, not only the final retry message.
3. Fix credentials, permissions, schema, or mapping.
4. Retry a small range.
5. Compare accepted, rejected, and duplicate records before expanding the run.

Account and support

• Credits and Billing
• Notifications
• Roles and Permissions
• Troubleshooting
• Labs — experimental features; do not treat Labs behavior as a general-availability contract.