Skip to content
BakingAds
Sign inBook a demo
Integrations

Site events and backend events, in the same analysis.

Every business has its own customer journey. In BakingAds you define the events that matter, collect actions on your site with the tracking script and send conversions confirmed by your systems through authenticated server-to-server API.

Let’s talk about your integration How it connects
How it connects

From the first ad contact to the value it creates.

A click identifier links every event of the journey, whether it is captured in the browser or confirmed by your backend.

Ad click

Campaign, ad and click ID arrive on the landing page.

Tracking script

Captures campaign parameters and on-site events.

Server-to-server API

Confirms leads and purchases from your backend.

BakingAds

Views, Cohort, ARPU forecast and Tell Me Why read acquisition and value together.

Events

Define the actions that count.

In the Events panel you describe your funnel: which action makes a user a valid lead, which one generates revenue, which ones must be counted only once.

  • Lead event: the action that qualifies a user, e.g. email confirmation.
  • Revenue event: the action that generates revenue, e.g. purchase or subscription.
  • Signup, first purchase, unique and any other funnel step you want to follow.
  • Event tokens route each action to the right definition.
Events / DefinitionsSAMPLE DATA
EventLeadRevenueSignupUnique
signup——●—
email_confirmed●———
purchase—●——
engaged———●
add_payment_info————

Tokens are never shown in clear in shared screens.

Browser and server

Two collection paths. One journey.

CLIENT-SIDE

Tracking script

A lightweight, asynchronous snippet on the pages of your funnel. It captures campaign parameters from the landing URL and attaches them automatically to every event you track.

  • Real-time events with automatic context.
  • Cross-subdomain support.
  • Minimal performance impact.
SERVER-TO-SERVER

S2S API

Authenticated calls from your backend for the events that matter most: lead confirmation, purchase, renewal. Unaffected by ad blockers and independent of the device.

  • Events confirmed by your internal systems.
  • Offline and delayed conversions.
  • Duplicate protection for unique and lead events.
A typical journey. A user arrives from a campaign, completes registration and buys a few days later. The site records the initial journey; the backend reports the purchase via API. The panels read acquisition and value in the same analysis.
Access and security

Keys and permissions managed per company.

Each company has its own data context. Access to panels depends on permissions and enabled features.

API keys per company

Generated and regenerated from the Events panel. Used only server-side, never exposed in the browser.

Roles and permissions

Each user sees the panels enabled for their profile and company.

Technical guide

Call examples, payloads and integration requirements are available in the Integration Guide inside the workspace.

The next decision starts here

Let’s talk about your integration.

Tell us about your funnel and your stack. We will map the events that matter and the fastest way to collect them.

Book a demo Open your workspace