Cross-domain consent issue between main site and MEWS Booking Engine — how do you handle this? Hi everyoneWe’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: Consen