Skip to main content

Hi everyone

We’re running into a tracking and consent issue that I imagine others might have faced too — and I’d love to hear how you’ve solved it.

First I’d like to add that the MEWS Booking Engine have been configured with the GTM-ID, and the GTM has been configured based on the documentation from MEWS. No issue here - everything works and it’s all good.

 

The situation:
Our main websites (www.steelhousecopenhagen.com and www.nexthousecopenhagen.com) uses Cookie Information as our CMP, and many visitors accept cookies there.

However, when users move to the end of the MEWS Booking Engine flow, they are forwarded to the domain app.mews.com for payment and confirmation. Here they are prompted to accept cookies again, witch is very easy to over look and not do!

Our guess is, that most visitors don’t accept cookies on app.mews.com, which means our purchase event for Google Analytics, Google Ads and Meta never fires — since consent isn’t granted on the MEWS domain.

 

What we’ve found so far:

  • Consent on our main site doesn’t carry over to app.mews.com, because it’s a different top-level domain.

  • We have our GTM container added in MEWS Booking Engine, but Consent Mode v2 still defaults to “denied” there - as best practice.

  • We’re considering a workaround where we pass the consent state in the booking URL (e.g. ?cm_analytics=granted&cm_ads=denied) and then read it via a GTM script on the MEWS domain to update gtag('consent', 'update', {...}).
    This would allow the same consent to apply without showing a second cookie banner.

Questions for the community:

  1. Has anyone successfully implemented a cross-domain consent bridge between their main site and MEWS Booking Engine?

  2. If so, how did you handle it — through GTM, server-side tagging, or another method?

  3. Are there any privacy or technical pitfalls we should be aware of when carrying the consent state this way?

Ultimately, we’d like the user’s original consent (granted on our domain) to persist so that our purchase events fire reliably in GA4, Gads and Meta, while still staying compliant with GDPR and Google Consent Mode v2.

Any insights, examples, or best practices would be super appreciated! 🙏

Thanks in advance for sharing your experiences.

 

Best regards,
Jacob Hartvig Nielsen
Arp-Hansen Hotel Group

Hi ​@JacobNielsen 

It seems you are using the Standalone Version of the Mews Booking Engine, which to my knowledge does not support what you are looking for.

 

There is also the Widget version, which you initiate on your own website with a script. See here:
https://mews-systems.gitbook.io/booking-engine-guide/booking-engine-widget/getting-started

When calling the widget, you have the option to pass the already given consent on your website to the IBE. See here: https://mews-systems.gitbook.io/booking-engine-guide/booking-engine-widget/reference
 

Option: enableTracking()

Please note that tracking is done by your Google Analytics, but as well the Mews Google Analytics! So you want to make sure that in the consent given, the visitor agrees to share its data also with Mews.


From your great description, I assume you are quite familiar with web technologies, otherwise a web developer can for sure assist with above.

Let me know if questions - best, Marc

Hi Marc

Thank you for the input! I’ll take a closer look at it with our developers! 😊

Terms and ConditionsCookie settingsAccessibility statement