Configure: map canonical events to ad platforms
The Configure split separates credentials, per-platform event allowlists, and checklists from generic settings — so you ship destinations without tag manager indirection.
- Configure
- dashboard
- destinations
- event mapping
Problem: You connected Meta and Google but SignUp fires while Purchase does not. Nobody remembers which conversion action ID maps to which canonical event.
What Configure replaces
Scattered env vars and GTM lookup tables do not scale across ten ad APIs. Configure centralizes platform credentials, event routing rules, and domain allowlists in one dashboard surface.
Changes persist to edge key metadata — routing updates without redeploying customer apps.
Per-platform allowlists
Blank allowlist means all canonical events route to that destination. Uncheck events you do not want — for example, send Purchase to Google but only SignUp and StartTrial to LinkedIn for pipeline campaigns.
This prevents mid-funnel noise from reaching platforms you optimize differently.
Checklists
Configure shows missing pixel IDs, conversion action IDs, and token expiry warnings before you scale spend.
Complete the checklist, fire test events, verify in Logs.
Split from legacy settings
API keys and team auth remain under Settings. Configure is the operational home for growth engineers owning conversion delivery.
Docs cross-links
Platform-specific behavior lives in Platforms. Event names in Events. Install path in quickstart.
Sources
Official documentation and references cited in this article.
More in Product
Using PostHog and TrackStack together
PostHog answers product questions; TrackStack delivers conversions to ad platforms. Here is how to run both without duplicate scripts, conflicting proxies, or split event schemas.
Read postDomain allowlisting for public API keys
TrackStack public keys ship in client bundles. Domain allowlisting restricts which origins can send events — a basic security control every production app should configure.
Read postDelivery logs: debug CAPI like you debug API requests
Every conversion should leave an HTTP trail. Delivery logs show platform responses, payloads, and retries — so you fix match issues before wasting ad spend.
Read postReady to fix your conversion pipeline?
Install the TrackStack SDK, route events to Meta and Google, and verify delivery from one dashboard.