Can the assistant publish without me?

No. Publishing, rollbacks, credential rotation and destination activation always require your click on an approval card that is bound to the exact change.

OpenAI Responses API with structured outputs and strict function calling. Model names are configured server-side and verified at start; the UI never hard-codes them.

Features

AI-guided setup

Your first destination goes live in one guided session — without writing a tag, and without giving up control over what gets published.

Start free See pricing

Guided setup

Example data

Track AI
example-shop.test runs on Shopify with Cookiebot as consent tool (high confidence). For a shop I suggest view_item, add_to_cart, begin_checkout and purchase. Shall I draft the plan for Meta and Google Ads?
You
Yes, Meta first.
Track AI
Pixel id validated. The Conversions API needs an access token — please enter it in the vault card below; it never appears in this chat.

Vault card · Meta access token

Stored encrypted; visible to no one, including the model.

stored

Test event · purchase

Sent through the real pipeline with the vendor's test event code.

accepted by Meta

Publish version 13

Bound to exactly this diff and to you as the approver.

waiting for your approval

+ destination meta: browser + server
+ mapping purchase → Purchase (event id, order id)
~ consent: marketing required for meta

Approve and publish

The assistant proposes, tools validate, you approve.

Example session: platform detected, event plan proposed, token stored in the vault, a real test event accepted, publish waiting for your approval.

Every action is a typed tool call you can see

The assistant turns a domain into a working measurement setup: it detects the platform and consent tool, proposes an event plan for your business type, collects public identifiers in chat and secrets in a vault card, sends a real test event and prepares a publish diff you approve.

The assistant never runs free-form code. It calls server-validated tools: detect the platform, draft the event plan, validate a pixel id, send a test event, prepare a diff. Anything irreversible — publishing, rollback, credential rotation — stops at an approval card bound to the exact change you are looking at.

Assistant → typed tools → approval card → signed configuration. Secrets go straight into the vault and never pass through the chat.

How it is built

The technical decisions behind the capability — the proof after the benefit.

01
Typed tools instead of free-form actions
Every action the assistant takes is a server-validated tool call with role checks, an audit entry and, for anything irreversible, an approval token bound to the exact diff you saw.
02
Secrets never reach the model
Access tokens go straight into the encrypted vault through a dedicated card or OAuth. The transcript, the model and the browser never see them; a DLP layer redacts pasted secrets and PII.
03
Deterministic state machine
Setup follows an explicit state machine with requirements and evidence for each state. The same states are available as a rule-based wizard when the AI provider is unavailable — nothing depends on a model being online.

Setup by hand versus the guided session

What changes when the assistant drives the setup and you keep the approvals.

Setup by hand versus the guided session
Setup by hand versus the guided session	Manual container setup	Guided setup with Track
Event plan	Written from memory, one tag at a time	Proposed for your business type, edited in chat, validated before publishing
Credentials	Pasted into tag fields and visible to everyone with container access	Entered in a vault card or via OAuth; never shown in the transcript
Verification	Hope the vendor received something	A real test event through the real pipeline with the vendor's verdict
Publishing	Publish, then discover what changed	Diff, recipients and approval first; a signed, versioned bundle after

What you can verify

Product facts you will find in the dashboard, the docs and the audit log.

Business type and platform detection with a confidence level
Event plan templates for shops, lead generation, SaaS and publishers
Public IDs validated against vendor formats
Publish only after a diff, recipient list and explicit confirmation

Questions

Can the assistant publish without me?: No. Publishing, rollbacks, credential rotation and destination activation always require your click on an approval card that is bound to the exact change.
Which model is used?: OpenAI Responses API with structured outputs and strict function calling. Model names are configured server-side and verified at start; the UI never hard-codes them.

More capabilities

Built on the same signed configuration and event schema.

Server-side event router
One event, every platform: browser and server delivery with shared deduplication.
Event debugger and lineage
See every event with its consent snapshot, routing decision and vendor response.
Data quality and health score
A single score with explainable components and issues that link to their fix.
Consent-aware by construction
Strict opt-in defaults, Consent Mode v2, purpose-based destinations, no replay after consent.
Click ids and attribution done right
Capture only the ids the destination needs, only with consent, only for the documented window.

Try it on your domain

Create a site, install one snippet and let the assistant configure the first destination in minutes.