Connect, preview, activate

Destinations

Open only the platform you need. Each card explains when it fires and what it requires; use Destination firing to apply presets or test an event.

Advanced: AI classifier and connector development
Core transformation

AI classifier

Checking the AII configuration…

Open connector API v1

Community connectors

Checking contributed adapters…

Contributors add a reviewed *_connector.py adapter implementing status, preview and delivery. It receives canonical privacy-filtered events only and cannot change capture or consent.

No credentials included

Configuration portability

Export firing rules, conversion mappings, event routes and the tag registry for review or reuse in another environment. API keys and live-delivery switches are always excluded.

Destinations

Every destination is built from the same privacy-safe event — add details for as many as you use.

Matomo
The base address of your Matomo instance, without /matomo.php.
Only turn this on once you've checked the previews in the explorer look correct. Until then, events are prepared but never sent.
GA4
Your GA4 property measurement ID.
Only turn this on once you've checked the previews in the explorer look correct. Events are sent to Google's Measurement Protocol v2 endpoint when enabled.
Optimizely
Found in Optimizely under Settings → Account. Required for live delivery.
Used to build Optimizely event payloads.
Sends to Optimizely's real-time event API (logx.optimizely.com). Only turn this on once previews in the explorer look correct.
Webhook
Every ready event is POSTed here as JSON, one event per request.
Only turn this on once you've checked the previews in the explorer look correct. Each request is signed with X-Signature-SHA256 (HMAC-SHA256 of the raw body) when a secret is set, so your endpoint can verify it came from here.
Warehouse
Ready events are appended here as JSON Lines, standing in for a real warehouse load (e.g. Snowflake) until a connector is built.
Google Ads
10-digit Google Ads account ID, no dashes.
Uploads offline click conversions via the Google Ads API. Only events carrying a gclid (captured automatically from the landing URL) can be attributed; others are skipped.
LinkedIn Ads
Posts to the LinkedIn Conversions API. Only events carrying a li_fat_id click id (captured automatically when present on the landing URL) can be matched; others are skipped.
AI insights (optional destination)
This is an optional downstream insight destination, not the AII classifier that creates canonical events. It receives only a privacy-filtered summary after classification.
Classification
Events scored below this are held for review instead of being sent automatically. 0.90 is a sensible starting point.
Web source
Used to build safe page URLs for every destination. Source configuration is independent of any connector.
Provider-specific transformation

Event mapping models

The canonical event remains destination-neutral. Configure the fields each provider actually needs on the Events screen before publishing.

Privacy & identity

What is actually enforced on every event before it reaches a destination — not a configurable policy yet, just the current rule.


      

      
Consent (local simulation)

No real consent management platform is connected. These switches simulate granted consent categories so delivery gating can be tested locally.