Analytics, tracking, and consent dependencies

Documentation / Media, forms, and integrations

Beeboo provides built-in connection settings for Google Analytics 4, Google Tag Manager, and Meta Pixel. Each requires an enabled connection and a valid identifier. Adding an identifier without enabling the connection does not activate it.

Configure the integration

Open the integrations settings for the intended website. Enter the Google Analytics measurement ID, Google Tag Manager container ID, or Meta Pixel ID in its matching field, enable the connection, and save.

The form checks the expected identifier shapes: G- for Analytics, GTM- for Tag Manager, and digits for Meta Pixel. A matching shape does not prove that the identifier belongs to the correct account, so verify ownership and destination in the provider's tools.

Understand loading behavior

The engine registers Analytics and Tag Manager loading through the analytics consent category. Meta Pixel uses the marketing category. When Tag Manager is enabled, the standalone Analytics loader is not also loaded, so configure the container deliberately if it is responsible for Analytics.

A Tag Manager container can load additional tags. Audit those tags and their consent rules; enabling the container is not a guarantee that every tag inside it respects the site's intended categories.

Arbitrary pasted scripts and provider embeds are separate. Do not assume the built-in connection gates automatically manage them. A native form consent question also does not grant analytics or marketing cookie consent.

Validate with fresh preferences

Test before choosing consent, after rejecting optional categories, and after granting the relevant category. Inspect network requests and the provider's diagnostic tools. Saved browser preferences can hide first-visit behavior, so include a clean-session test.

See Legal and privacy with LEX8 before enabling tracking.