Implementation guides tied to the real signal model
Every integration page is built around the same gateway, validation, and rollout workflow, so you do not relearn the product every time you add a new platform.
- 4 live guides
- 2 ecommerce routes
- 2 destination routes
Every guide uses the same gateway model, delivery review workflow, and simulator-first validation path.
Only the storefront plumbing, credentials, and platform-specific event naming. The operational model stays the same.
Pick the storefront or destination you care about, validate one live path, then expand once dashboard truth matches the test flow.
Shopify
Connect a Shopify storefront, send first-party ecommerce events through one gateway, and route them to your ad destinations without relying on fragile browser pixels alone.
WooCommerce
Use the same gateway model for WooCommerce: one first-party event stream, one delivery control plane, and one consistent routing model across destinations.
Meta CAPI
Send first-party events to Meta through one gateway, inspect delivery health, and keep routing consistent with your other destinations.
TikTok Events API
Route first-party events to TikTok through the same gateway and proof flow you use for every other marketing destination.