StayStrategy

Consent Mode for Independent Hotels: Three Setup Jobs to Get Right

Google Consent Mode v2 lets your Google tags adjust their behavior based on each guest’s consent choice. When cookies are unavailable, Google may use modeling, but it does not recover specific bookings you would otherwise lose. If your hotel uses GA4 or Google Ads, turn it on now. Hand your developer three jobs: the consent banner (CMP), the Google tag or Google Tag Manager setup, and coordination with your booking engine vendor.

TL;DR:

  • Advanced mode sends cookieless pings before a choice, supporting modeling; basic mode blocks tags until consent, leaving no signals for declined guests.
  • Ask booking engine and widget vendors whether scripts wait for consent and pass campaign data across domains, since premature tracking can undermine the setup.
  • Test booking flows after accepting and declining, inspect Google Ads and Tag Manager diagnostics, and repeat checks after website, banner, or booking engine updates.
  • Treat modeled conversions as estimates, compare analytics with reservation reports and server logs, and do not base budgets on one modeled booking cost.
  • Consent Mode does not ensure legal compliance; check regional requirements with a privacy professional, and keep cookie consent separate from email marketing consent.
StayStrategy
Build Your Hotel’s AI Visibility
Explore StayStrategy’s guides and tools for helping hospitality businesses get named when travelers ask AI where to stay.
Explore StayStrategy

Table of Contents

Consent Mode is Google’s way of letting your website tell its tags what a guest agreed to. Tags adjust their behavior based on those choices instead of firing the same way for everyone. Think of it as a switchboard between your banner and your analytics and ad tags.

You need to know four consent types:

  • ad_storage: whether advertising cookies can be written or read.
  • analytics_storage: whether analytics cookies can be used.
  • ad_user_data: whether user data can be sent to Google for advertising.
  • ad_personalization: whether data can be used for personalized ads and remarketing.

The last two arrived with v2, when Google made the API more granular for European traffic. When cookies are unavailable, tags may still send signals that Google can use for modeling. The details depend on the consent settings and implementation.

For a hotel, the payoff is measurement you can still trust. A guest who accepts cookies behaves as before: your remarketing audiences and conversion tracking keep working. When cookies are unavailable, Google may use modeling, so reports can include estimates rather than showing only directly observed conversions. Without Consent Mode, every declined banner is a hole in your data.

That matters most if you pay for traffic. A hotel running paid campaigns to drive direct bookings may want to understand how its advertising relates to reservations. Booking engine tracking is where this often breaks, since the guest leaves your site to complete the stay on a vendor’s domain.

There is also a trust angle. When a banner choice is actually honored by your tags, you are doing what the banner promised. Honoring banner choices helps keep your implementation consistent with what guests were told. Google also expects it: for advertisers targeting the European Economic Area, Google’s user consent policy calls for consent signals to be sent back to Google, and non-compliance can mean losing personalization and measurement features.

A guest opens your site, and your banner (the CMP) sets default consent states. Configure those states to fit the choices you offer and the rules that apply to your visitors. The guest clicks accept or reject. The CMP then updates the consent state, and the Google tag reads it and decides what to do: write cookies, send only a ping, or hold back.

There are two ways to set this up:

  • Basic: Google tags are blocked until the guest interacts with the banner. Nothing is sent before a choice, so there is nothing to model from for guests who decline.
  • Advanced: tags load right away with the default states and send cookieless pings, then upgrade their behavior if the guest accepts. Google describes this version as the one that supports advertiser-specific modeling, which is why it recovers more data.

Google also warns that blocking tags until interaction can stop it from verifying consent choices and lead to data loss. An advanced implementation may provide modeling, but choose an approach only after checking that it fits your consent setup and applicable requirements.

Know the limits. Modeling can provide estimates when cookies are unavailable, but it does not restore unavailable cookie-based information. Check Google’s documentation for the details of what your implementation reports. When ad_storage is denied, personalization is limited, so remarketing lists for that guest will not grow. Modeled numbers are estimates, and you should read them that way.

Implementation checklist for hotel websites

Give this sequence to your developer or web vendor. It fits a small independent hotel with one website, one booking engine and a Google Tag Manager container.

  1. Pick a CMP that supports Consent Mode v2. Google recommends a Google-certified CMP for most advertisers. Switch on its Google Consent Mode option in the settings.
  2. Connect the CMP to your Google tag. Use gtag.js or Google Tag Manager so the consent state reaches every Google tag. If you run your own custom banner, you must implement v2 manually and verify it afterward.
  3. Set default consent states. Decide what applies before a guest chooses, by region if needed, and confirm the appropriate settings for your circumstances.
  4. Configure ad_user_data and ad_personalization to reflect the guest’s choice. Check the requirements that apply to your implementation.
  5. Decide on server-side tagging. It requires a web container to collect consent and a server container to process data, along with components such as a GA4 client and configured Conversion Linker tags. Assess whether this setup suits your needs.
  6. Coordinate with your booking engine, CRS and widget vendors. Ask each one whether its scripts wait for consent and whether it can pass consent or campaign data across domains. Anything that fires tracking before consent is recorded undoes your setup.
  7. Test Ads Data Redaction and URL passthrough only if they fit. Both are optional settings. Turn them on deliberately, with a reason, and check the result.

Pro Tip: Ask your booking engine vendor for its consent documentation before launch. Reviewing the integration early can help you identify issues before they affect your reporting.

Once Consent Mode is live, its behavior depends on your implementation and consent settings. Google may use modeling when cookies are unavailable; check its documentation for how estimates are reported. Check Google’s reporting and diagnostics to understand how modeled estimates appear in your account.

Check conversion diagnostics in Google Ads and Tag Manager. They can help you check whether consent signals are arriving and whether tags report consent status. If signals are missing, investigate your setup.

Then protect your attribution from the outside:

  • Be strict about UTM tags on every campaign link, email and partner placement. This short guide on UTM steps for hospitality covers the habits that stop bookings from landing in “direct” by mistake.
  • Compare your analytics totals against server logs and your booking engine’s own reservation reports. Aggregated counts from your own systems do not depend on cookies.
  • Treat modeled figures as directional. A week-over-week trend is useful. A single exact cost per booking from modeled data is not something to bet a budget on.

If you also run vacation rental ads, our Google Ads guide for direct bookings walks through campaign structure that pairs well with this setup.

Validation, testing and ongoing maintenance

Treat Consent Mode like any tracking setup: test it at launch and again after changes.

  • Run Tag Manager preview and debug mode, and look for the consent log lines showing default and update states.
  • Open Google’s conversion diagnostics to confirm pings and consent status are being received.
  • Walk the full booking flow yourself, once accepting cookies and once declining, including the booking widget and any third-party chat or review plugins.
  • Recheck after every website, banner, plugin or booking engine update, and test the server container after any change if you use one.
  • Name one internal owner for consent issues, and keep a vendor contact for your CMP, your web developer and your booking engine in one place.

Consent Mode is a technical tool. It does not make a hotel compliant by itself, and it is not legal advice. What it does is make your tags follow the choice a guest made in your banner, which is the behavior privacy rules expect from you.

Privacy requirements depend on the jurisdictions and circumstances involved. Check the rules that apply to your hotel with a qualified privacy professional. That is the case Google built v2 around: advertisers targeting EEA traffic are expected to send consent signals to keep ad personalization and measurement features. Privacy requirements vary by jurisdiction. For a California-facing hotel, check the applicable rules with a qualified privacy professional and ensure your tag behavior reflects the choices you offer.

Hospitality adds its own wrinkles. You collect reservation data, guest profiles, loyalty details and sometimes ID information, often through several vendors. Your cookie banner covers website tracking, but your privacy policy and data processing agreements need to cover everything else. The FTC has long pointed out that effective privacy notices should state what data is collected, whether providing it is voluntary, and how people can exercise their rights, and opt-in and opt-out regimes should both be built for clarity.

Practical steps: keep your privacy policy current, record consent choices through your CMP, and have a privacy professional review your setup for the regions you target.

A cookie banner is often the only privacy message a guest sees on your site, so it deserves the same care as your booking button.

  • Use plain words. “We use cookies to measure which pages help guests book and to show relevant ads” beats legal phrasing.
  • Make the choice fair. Accept and decline buttons should look equally easy to click. Make the available choices clear and easy for guests to understand.
  • Explain the purpose clearly. Describe what data you collect and how you use it, and provide details where guests can find them.
  • Link to a short privacy page written for guests, not lawyers, covering website tracking, reservation data and how to ask for deletion.
  • Keep the promise. Test that declining actually changes what your tags do, since a banner that says one thing while scripts do another is the worst outcome.
  • Repeat it at check-in points. Your pre-arrival email and booking confirmation can carry a one-line note about how guest data is used and where to change preferences.

Review the wording periodically, and whenever you add a new marketing tool or booking vendor.

Some personalization will shrink, and that is the honest tradeoff. When a guest denies ad_storage or ad_personalization, the related tag behavior changes according to your consent settings. Check your implementation and applicable requirements before using data for remarketing or tailored ads. Audiences built on consenting guests will be smaller than your total traffic.

What you keep is still useful. Guests who accept remain fully measurable and targetable. When cookies are unavailable, Google may use modeling. Do not assume that modeled signals guarantee better bidding decisions. Your campaigns work on a thinner, cleaner base of data, not a broken one.

To balance the two:

  • Lean on first-party relationships. Email lists, past-guest offers and a booking-confirmation opt-in rely on consent given directly to you, not on cookies.
  • Strengthen contextual targeting: search ads matched to what a person is looking for right now do not need a history of that person.
  • Improve the site itself. Clear rooms, rates, photos and policies convert guests regardless of what you can track.
  • Judge campaigns on trends and total bookings, not on perfectly attributed individual journeys.

Respecting guest choices can mean relying on a smaller audience of people who have opted in.

Consent Mode itself only governs Google tags. It does not write anything into your CRM. But the consent choice behind it is a piece of data worth keeping, and a good integration treats it that way.

Start with what your CMP records: each guest’s choice, a timestamp and the policy version shown. Check whether your CMP can export or send this information to a database or tag manager. If you can attach it to a guest record, with a lawful basis for doing so, your marketing team can see who agreed to what.

Use it to avoid mistakes:

  • Before syncing guest information to advertising audiences, check the applicable consent requirements and the choices recorded by your CMP.
  • Keep email marketing consent separate from cookie consent. Accepting cookies does not mean agreeing to newsletters.
  • Pass campaign source data (UTMs) from the booking engine into the CRM so you can tie reservations back to channels without relying on cookies.
  • Honor deletions and opt-outs across every system, not only the banner.

Ask your CRM, booking engine and email vendors what consent fields they hold and how they update. Small hotels do not need a customer data platform for this. A spreadsheet of fields, owners and vendors can help you document the setup.

Consent Mode does not make ChatGPT, Gemini or Google’s AI features recommend your hotel. Those tools pull from your site content, reviews, listings and mentions across the web, not from your consent settings. What Consent Mode does is protect your ability to measure the traffic that results.

That distinction matters as guests start asking AI tools where to stay. Some visitors may arrive from an AI answer and book after declining cookies. How those visits appear in reporting depends on your Consent Mode setup and Google’s modeling. Without it, you may wrongly conclude that AI discovery sends you nothing.

Where your analytics setup and consent choices allow it, first-party data can help you understand how visitors use your site. You can use those patterns to improve the content AI systems read about you, always within the choices guests gave.

To go deeper on the visibility side, read our guides on Google AI Overview visibility for hotels and tips for boutique owners, or take the free AI visibility course.

FAQ

Consent Mode v2 supports the ad_user_data and ad_personalization parameters alongside ad_storage and analytics_storage. Google introduced it for advertisers with European Economic Area traffic.

Remove or disable the Consent Mode settings in your CMP and Google Tag Manager, so your tags stop reading consent states. Think carefully before doing it. Without consent signals, Google may limit personalization and measurement for EEA traffic, and your reporting gaps will grow.

Can a hotel see my browsing history?

A hotel can only see activity that happens on its own website, and only what its analytics and ad tags record. Consent Mode helps make sure those tags follow your banner choice. It does not give a hotel access to your history on other sites.

If you use GA4 or Google Ads, yes. Without it, every guest who declines cookies leaves a gap in your reports. With it, Google can model conversions while your tags still respect each guest’s choice.

Sources

StayStrategy Editorial articles are general information for hospitality operators and are produced with the help of AI. Platform policies, prices and local rules change, so confirm the details before you act on them.

Get your property ready to be named by AI

The AI Visibility Workbook is eleven printable sheets. When every box is full you have written what a machine needs to be able to name you.

Or check your visibility first. Seven questions, about two minutes.

How to get recommended by AI, the course