If bookings drop off when visitors leave your website, or if your tracking numbers do not line up with consent rules, it is hard to trust what is working. Operators often end up double-checking campaigns, guessing which traffic converts, or worrying that tracking will break compliance.
Embedding Growth Hub directly into your website keeps visitors in the same experience from first click to checkout. At the same time, consent-aware tracking follows the cookie choices visitors already made on your site. You still see bookings and revenue, while the attribution details follow consent.
In this article:
Understand why embedding Growth Hub changes the booking journey
Learn how deep links work across the booking flow
See how consent-aware tracking affects data and reporting
Know what to expect when visitors do not consent to tracking
Why embedding Growth Hub matters
When Growth Hub runs inside your website, visitors do not feel pushed to another system. This removes friction during browsing and checkout, which is where many bookings are usually lost.
What you get:
A website-native booking journey: Visitors stay on your site while browsing spaces, choosing dates, and paying. This reduces hesitation and builds trust.
Direct links into the booking flow: You can send traffic straight to a specific space, product, date, or step. This helps with targeted campaigns and reduces customer clicks.
What is consent-aware tracking?
Growth Hub follows the cookie consent your website already captures. Tracking events fire only when the visitor has agreed to them.
What this means for you:
Measurement that follows consent rules: You can review performance without second-guessing compliance or privacy expectations.
Cleaner data: Events are recorded only when consent is present, reducing noise and making reports easier to trust.
A predictable visitor experience: Visitors see tracking and personalization only when they agree to it. There are no surprises that damage credibility.
If a visitor does not consent, some marketing and analytics data are limited by design. Growth Hub still records the business outcome, such as bookings and revenue. Attribution detail follows the visitor's consent choice.
Common use cases
Embedding Growth Hub into your website allows you to:
Link a campaign directly to a specific meeting room on a specific date.
Keep the full purchase flow consistent with their website look and feel.
Align Growth Hub tracking with website consent banners and connected analytics tools.
What to check if numbers look different
If reports show fewer tracked events than expected:
Confirm which cookie categories the visitor accepted on your website.
Check which events require marketing or analytics consent.
Compare total bookings and revenue; these are always recorded, with attribution data, which follows consent.
This difference is expected behavior and usually explains why totals look right while attribution looks lighter.
Best practices
Follow these best practices to achieve better and more consistent results:
Test deep links before launching campaigns: Open links in an incognito window to confirm they land on the right space and date.
Review consent settings with marketing teams: Make sure everyone understands which metrics depend on consent and which do not.
Use bookings and revenue as the source of truth: When attribution varies, rely on confirmed outcomes first, then review tracking detail second.
If something still does not line up, capture the page URL, date, and consent state before reaching out to support. This speeds up troubleshooting and reduces back-and-forth.