Ads binding
Link ad-platform accounts to a funnel for offline conversion postback when orders are paid.
Ads binding connects one or more ad platform accounts to a funnel so that when an order placed through that funnel is paid, autonnel sends an offline conversion event to the matched platform automatically.
Ads binding is only required if you want offline conversion postback — autonnel calling the ad platform’s server-side conversion API when an order is paid. If you only need online (client-side) tracking via the platform’s JS pixel, you don’t need to bind ad accounts here — install the pixel script via Settings → Scripts (site-wide) or the funnel’s Scripts tab (per-funnel).
Offline postback is more reliable than client-side pixels (ad blockers, iOS Safari ITP, etc.) but requires server-side API tokens. Online pixels are simpler to set up but lose attribution to blocking software. Most stores run both.
One account per platform per funnel
Each funnel can be bound to at most one account per ad platform. For example, a funnel can have one Facebook account and one TikTok account bound simultaneously, but not two Facebook accounts. A single ad account can be bound to multiple funnels.
Token mode vs. OAuth mode
Token mode (available in core)
Facebook, TikTok, and Bing Ads support token mode. You paste the platform’s access token and pixel or UET tag ID directly into the ad account settings. No OAuth flow is required. Server-side postbacks use these credentials when sending conversion events.
To set up an ad account in token mode:
- Go to Ads in the sidebar and create an account for the platform.
- Enter your access token and pixel / UET tag ID.
- Open the funnel detail, go to the Ads tab, and bind the account.
OAuth mode (requires plugin)
Google Ads does not support token mode due to API restrictions. To use Google Ads postbacks, install and configure the @autonnel/plugin-ads plugin. Once the plugin is active, an Connect with OAuth button appears in the Ads UI for supported platforms, and the Google Ads platform becomes available for binding.
Postback timing and retry
Postbacks fire when an order is marked paid. The postback runs server-side (offline) — no client-side pixel is involved.
If a postback fails, autonnel records the failure and a cron job retries it periodically until it succeeds. You can see postback status on the order detail page.
Click ID routing
Autonnel attributes conversion events to the correct platform by inspecting the click ID stored with the order’s first page visit. The routing rules are:
| Click ID parameter | Platform |
|---|---|
fbclid | |
ttclid | TikTok |
gclid, wbraid, gbraid | Google Ads |
msclkid | Bing Ads |
Only events where the order’s click ID matches the bound platform are sent. If an order arrived without a matching click ID for a given platform, that platform receives no postback for the order.
Event mapping
Each ad platform account has an event mappings configuration that translates Autonnel’s events to platform event names:
| Autonnel event | Example platform mapping |
|---|---|
| PageView | ViewContent |
| CheckoutView | InitiateCheckout |
| InitiatePayment | AddPaymentInfo |
| Purchase | Purchase |
The Purchase mapping is required and not editable — it is always sent when an order is paid. Other event mappings can be configured or omitted per platform.
Caveats
- Client-side pixels are your responsibility. Autonnel’s ads binding handles server-side order conversion postbacks only. In-page tracking pixels (for page views, add to cart, etc.) are not injected automatically. Set those up via Settings → Scripts or per-funnel scripts (see Funnel scripts).
- No postback for orders without a click ID. If the order has no matching click ID for the bound platform, no event is sent to that platform.
- Token credentials are sensitive. Treat access tokens like passwords. Rotate them if you suspect exposure.