Your ad and analytics tags, managed from the console.
Fourteen analytics and advertising providers configured once and installed per app - no tracking code in your codebase. Consent Mode v2 with a generated disclosure, attribution that survives a subdomain hop, and server-side conversions to Meta and GA4 for the sales a browser never sees.
Your app is an organization in BuildBase. Your users sign in and work inside workspaces - one per team or customer.
You set up
In the console and the SDK
- Your ad and analytics tags (GA4, Google Ads, Meta, X and more), in the console
- Which of your sites and apps each tag loads on
- One line in your app to turn tracking on
You get
For you and your team
- Sign-ups and purchases reported to your ad platforms, with no event code
- Conversions credited to the ad your user actually clicked
- Tags that wait for your cookie banner before they load
Conversions your ad platforms can actually count
BuildBase already sees the sign-up and the payment, so it reports them. You add the tags and pass consent.
Tags Without Code
Add GA4, Google Tag Manager, Google Ads, Meta, X, TikTok, LinkedIn and more in the console. No tracking id lives in your code.
Sign-ups and Sales Reported
When your users sign up, sign in, start checkout or pay, every tag hears about it in its own terms: an event name for GA4 and Meta, the conversion you created for Google Ads, X and LinkedIn.
The Steps Before Paying
See who opened your pricing, picked a plan or hit a limit. These go to your analytics tools, not to ad networks.
Consent First
Only consent-aware Google tags load until your cookie banner is answered. The console writes your privacy-policy paragraph for you.
Credit the Right Ad
The ad a visitor clicked is remembered for 90 days, across your site and your app, and through Stripe checkout.
Sales the Browser Missed
A buyer who closes the tab before the thank-you page still reaches Meta and GA4, sent from our servers.
One prop to turn it on
tracking={{}} loads the tags attached to your app and reports sign-ups, logins, checkouts and purchases. track() sends anything else.
import { ApiVersion } from '@buildbase/sdk';
import { SaaSOSProvider } from '@buildbase/sdk/react';
<SaaSOSProvider
serverUrl={serverUrl}
version={ApiVersion.V1}
orgId={orgId}
auth={{ clientId, redirectUrl }}
tracking={{}}
>
{children}
</SaaSOSProvider>;import { useTracking } from '@buildbase/sdk/tracking';
function InviteButton() {
const { track } = useTracking();
return (
<button onClick={() => track('teammate_invited', { seats: 3 })}>
Invite
</button>
);
}Know which ad brought each customer
The ad click a visitor arrived with follows them from your marketing site to sign-up and payment, and respects their answer to your cookie banner.
Remembered across your subdomains
A visitor's ad click id and UTM tags (the campaign labels in a link) are kept for 90 days in one cookie on your own domain. So a sale on app.yoursite.com is credited to the ad that brought them to www.yoursite.com.
The ad keeps the credit
A new ad click replaces what's stored. A later visit with only campaign labels never overwrites a click, so someone who clicks an ad and comes back through your newsletter still counts for the ad.
Carried into sign-up
When the visitor signs in or creates a workspace, the stored click goes with them to the server. It stays on the user and the workspace for every sign-up or sale that follows.
Waits for marketing consent
From @buildbase/sdk 1.0.0, the cookie is saved only after a visitor says yes to marketing cookies. Until they answer, the click is kept for that page only, and a no deletes it. On older versions, the cookie is saved as soon as they land.
Proof of consent
Every answer to your cookie banner is saved with the choices made, the version of the wording they saw and their country, never their IP address. When someone asks for their data, look them up by email, user id or browser id.
Or ask at sign-up
Turn on one consent checkbox on the hosted sign-up page instead of a banner. It's never ticked in advance, never required and never bundled with the terms.
Measure what a paying customer costs you
If the only result an ad platform sees is a sign-up, it learns to buy sign-ups. BuildBase reports the moment someone pays, which happens on your server through Stripe, often days later.
Count paying customers, not sign-ups
BuildBase builds a file of the subscriptions that actually paid, from Stripe updates no browser ever sees. Point Google Ads at it once as a scheduled upload (Google calls it a click import).
Refunds taken back out
A refund goes into a second file, of adjustments, against the same click, so a campaign never gets credit for money you gave back.
Your own team left out
List your team's email domains, addresses and workspaces once. Their sign-ups stay on record, marked internal, and never reach an ad platform.
Enhanced conversions
Turn it on per app and each conversion carries a scrambled copy (a hash) of the signed-in user's email to Google Ads and Meta. That lets them match more sales to ads. The email is scrambled in the browser and sent only with marketing consent.
Every sale, with a reason
Every sale your server weighed up is one row in the console, saying whether it was sent to the ad platform and, if not, why. A missing conversion always has an answer.
Bid on what pays
Make Paid subscription your main conversion and Google Ads aims for customers, not trials. What each customer costs you (your CAC) is then the campaign's spend divided by that count.
Works well with
Other modules for growth & insight.
Read more in the docs
Setup guides and reference for Tracking & Tags.
Overview
Analytics and ad tags configured in the console, installed by the SDK.
Run ads with conversions
The checklist for Google Ads and Meta to count your sign-ups and sales.
Measure real CAC
Find what a paying customer really costs you (your CAC) by reporting payments, not sign-ups, so Google Ads spends on the clicks that pay.
Conversions without a browser
Send Google Ads a file of the subscriptions that actually paid, with refunds taken back out.
Providers
The fourteen tags you can configure, the ID each takes, and the Content-Security-Policy you need.
Events
The events BuildBase fires for you, and how to send your own.
Consent
Consent Mode v2 defaults, your banner, and the parameters kept for attribution.
Server-side conversions
Report the sales a browser never saw, under the same event id.
Verify and troubleshoot
Prove your tags load and your conversions arrive.
Frequently Asked Questions
What people ask about Tracking & Tags.
Do my users see this?
Only your cookie banner. The tags load in the background and report to your analytics and ad tools.
Where is it set up?
Add tags in the console under Settings › Tracking & tags, and attach them to an app in that app’s authentication settings. In your code, pass tracking={{}} to the provider, or wrap a marketing site in BuildBaseTracking from @buildbase/sdk/tracking.
Which tools are supported?
14: Google Tag Manager, Google Analytics 4, Google Ads, Meta Pixel, X (Twitter) Pixel, LinkedIn Insight Tag, TikTok Pixel, Reddit Pixel, Microsoft Advertising (UET), Microsoft Clarity, Hotjar, PostHog, Plausible Analytics, Ahrefs Analytics. You can also add a script of your own by URL.
Does anything load before my cookie banner is answered?
Only Google Tag Manager, Google Analytics 4 and Google Ads, which honour Google Consent Mode and load in denied mode. Everything else waits for consent.
How does X (Twitter) conversion tracking work?
Add your X Pixel ID, then paste the event ID of each conversion you created in X Events Manager, or the whole tw- code from its snippet. From SDK 1.0.0 the SDK fires each one under the code X counts, with the value, currency and items of a purchase, and records a page visit on every in-app navigation. By default X waits for a visitor to accept marketing cookies before it loads. Conversions reach X from the browser; there is no server-side send to X.
Can I point PostHog at my own server?
No. PostHog is supported on its US and EU clouds only.
Does the attribution cookie wait for consent?
From @buildbase/sdk 1.0.0, yes. When a visitor arrives from an ad, the click they came from is kept in memory on that page. Only once they agree to marketing cookies is it saved in the cookie, for 90 days. If they refuse, it is deleted. On older versions, the cookie is written as soon as they land.
Get your conversions counted
Add your tags in the console, attach them to your app, and pass tracking={{}}. Sign-ups and sales reach your ad platforms from the first visit.