AI Agent

Zeotap Agent is a conversational interface that carries out multi-step CDP work for you — building audiences, wiring up models and relationships, configuring orchestrations, and answering questions about what is already in your workspace.

Where to Find It

The side panel is the more useful of the two while you are mid-task: on the audience builder it opens by itself when you reach the filter step, and the filters it suggests can be applied straight into the builder. See the NL Audience Builder.

What the Agent Can Do

The agent works through the same tools the MCP Server exposes, so its reach is exactly that tool set — nothing hidden, nothing extra.

It can create and change:

• Models and schema — create models from a warehouse table or SQL, adjust columns, set sensitivity and PII types, and create relationships between models
• Audiences — build filter trees, estimate sizes before saving, and create audience canvases and publish them
• Computed attributes — define them on a parent model and refresh them
• Destinations and audience syncs — create a destination, connect an audience to it with field mappings and a schedule, and trigger a run
• Orchestrations — create, validate, activate, pause, resume, and trigger them
• Identity graphs — create one, configure its identifiers and merge rules, set up golden records, and trigger a resolution run
• Stores — create a store, attach feeds, and refresh them

It can look at:

• Your models, relationships, computed attributes, audiences, destinations, and syncs
• Event volumes, contracts, contract violations, forwarding rules, and transformations
• Resolved profiles, by looking up an identifier in an identity graph
• Your warehouse directly, with a read-only SQL query

Event configuration — forwarding rules, transformations, contracts — is read-only to the agent for the same reason: it can tell you what is configured and what is failing, but the changes are yours to make.

Using It

1. Open Zeotap Agent from the sidebar, or press ⌘J to bring up the panel
2. Click New Chat and describe what you want in plain language
3. The agent works through the steps and streams what it is doing as it goes
4. Some steps come back as a card you confirm — suggested filters you Apply, canvas changes you accept
5. Keep talking to refine the result

Anything that a guardrail holds for approval pauses there until a workspace admin approves it, and the agent tells you it is waiting.

Example Requests

Building an audience:

“Create a high-value audience of customers who’ve spent over $1000 in the past year and sync it to Google Ads for retargeting”

Modelling:

“Make a model from the analytics.orders table, set order_id as its primary key, and relate it to my customers model”

Answering questions:

“Which of my audiences have no active sync, and how large are they?”

Sessions

Each conversation is a session, listed beside the chat with its most recent message. Sessions are kept, so you can go back to one and continue where you left off.

Giving the Agent Context

Under Settings → General, Workspace context is free text — up to 4,000 characters — that is included in the agent’s prompt for every session in the workspace. Use it for the things it has no way of knowing: what your business does, which markets matter, naming conventions you want followed.

We are a DTC coffee brand. Key markets are DE and FR. Prefer concise, lowercase audience names.

Turning It Off

The agent is on by default. A workspace admin can switch it off under Settings → General, which hides it from the workspace and stops new sessions from starting. Existing conversations are kept and become readable again if it is switched back on.

Next Steps

• Guardrails — what the agent may do without asking, and what it may not
• NL Audience Builder — describing an audience and applying the result
• MCP Server — the same tools, from your own AI client