Tracking and consent
This page explains the cookie banner on BoostUp's own website and what it allows us to measure. It is for visitors who want to know what we track, and for operators who run a BoostUp instance.
The cookie banner
On your first visit a banner asks what you allow:
- Accept all: analytics and marketing cookies.
- Only necessary: only the cookies needed to sign in, keep you secure and remember this choice.
- Settings: two switches, Analytics (Google Analytics 4 and PostHog) and Marketing (Meta Pixel), then Save settings. Both switches start off.
Until you choose, nothing loads from Google, Meta or PostHog.
Changing your choice
Click Cookie settings in the footer of any public page. The banner opens with the settings panel and your current choice. Turning a switch off stops the matching tool from sending anything more (a script that already loaded stays in the page until you reload, but it no longer sends data).
The bu_consent cookie
Your choice is stored in a first-party cookie named bu_consent. It holds URL-encoded JSON like this:
{"v":1,"analytics":true,"marketing":false,"ts":1762905600000}
| Field | Meaning |
|---|---|
v | Version of the consent record |
analytics | Whether you allowed analytics |
marketing | Whether you allowed marketing |
ts | When you made the choice (milliseconds since 1970) |
The cookie lasts 180 days, is sent only to BoostUp (SameSite=Lax, path /, Secure over HTTPS) and is
readable by the page's own scripts, because the page needs it to decide what to load. After 180 days, or if the
cookie is deleted, the banner asks again.
Google consent mode v2
Before any tag could run, the page sets Google consent mode v2 defaults with every signal denied:
ad_storage, analytics_storage, ad_user_data and ad_personalization. This step makes no network request.
When you choose, the signals are updated: analytics_storage follows your Analytics choice, and the three ad_
signals follow your Marketing choice.
What loads after consent
| Your choice | What loads |
|---|---|
| Analytics | Google Analytics 4. PostHog too, but only when the operator configured a PostHog key |
| Marketing | Meta Pixel |
| Only necessary | Nothing from Google, Meta or PostHog |
Each tool loads only when its ID is configured. Page views are sent once per page to each tool you allowed, including when you move between pages without a full reload.
Events
Besides page views, the site sends four events, only to the tools you allowed:
| Event | When | Name in Meta |
|---|---|---|
start_analysis | You start a free website analysis on the homepage | StartAnalysis (custom event) |
sign_up | You create an account | CompleteRegistration |
report_viewed | You open a website report | ViewContent |
talk_to_sales | You click a link to email our sales team | Contact |
GA4 and PostHog receive the event names as they are in the first column.
Server-side Conversions API
For sign_up and report_viewed, BoostUp's server also sends the event to the Meta Conversions API, but only when
you allowed marketing. The browser event and the server event carry the same event ID, so Meta counts them once.
The server event includes your IP address, your browser's user agent, the page address and the Meta browser cookies
(_fbp, _fbc) when they exist. For sign_up it also includes your email address, hashed with SHA-256.
For operators
All IDs come from environment variables. Leave one empty to turn that tool off.
| Variable | Where | What |
|---|---|---|
NEXT_PUBLIC_GA4_ID | web, build time | GA4 measurement ID. Empty: GA4 off |
NEXT_PUBLIC_META_PIXEL_ID | web, build time | Meta Pixel ID. Empty: Meta Pixel off |
NEXT_PUBLIC_POSTHOG_KEY | web, build time | PostHog project key. Empty: PostHog entirely off |
NEXT_PUBLIC_POSTHOG_HOST | web, build time | PostHog host, default https://eu.i.posthog.com |
META_PIXEL_ID | API | Pixel the Conversions API sends to |
META_CAPI_TOKEN | API | Conversions API token. The server sends nothing unless both Meta API values are set |
The NEXT_PUBLIC_ values are read when the web image is built, so changing them needs a rebuild.
GA4 setting. In the GA4 web stream, under enhanced measurement, turn off page changes based on browser history events. BoostUp sends its own page view on every page change, so leaving it on counts page views twice. See GA4 setup.