The rising cost of OTA dependency<\/strong>. Leading independent hotels now achieve between 40% and 55% of their volume through their own channel, compared with an industry average of 25% to 30%. The gap between the two rarely comes down to traffic volume \u2014 it comes down to the ability to turn that traffic into a relationship, rather than a one-off booking.<\/p>\n Privacy is no longer an obstacle \u2014 it’s a design condition<\/strong>. The good news is that identifying behaviour at an aggregate, anonymous level doesn’t require the same legal treatment as identifying an individual. In Spain, the data protection authority (AEPD), in line with the EU’s GDPR, exempts aggregate and anonymous audience-measurement tools from prior consent requirements, provided they don’t cross-reference data between sites or identify the specific visitor \u2014 a position consistent with data protection guidance across the EU and UK (SecurePrivacy<\/a>). The legal tipping point isn’t “observing behaviour”, it’s “linking that behaviour to an identity” without a lawful basis for doing so.<\/p>\n Systems that work with anonymous traffic typically combine several techniques: first-party domain cookies, behavioural session clustering, and AI models that score purchase intent based on pages viewed, visit frequency and content consumed. Realistic match rates for linking a session to a specific identity sit between 30% and 75%, depending on the sector and the data available \u2014 far from the 90%+ that some vendors occasionally claim (Factors.ai<\/a>).<\/p>\n In hospitality, the most sensible approach \u2014 and the one that avoids any legal friction \u2014 isn’t to forcibly “de-anonymise” visitors, but to categorise behaviour in aggregate (what type of interest that visitor is showing: family, weddings, weekend getaways, business) and wait for the moment the visitor identifies themselves voluntarily: by filling in a form, connecting to the hotel’s WiFi, or completing a booking. At that point, the entire anonymous behavioural history can be linked to their profile, without it ever having been treated as personal data beforehand.<\/p>\n The real value isn’t in knowing that “an anonymous visitor looked at double rooms three times this week” \u2014 it’s in what can be done once that person identifies themselves: at that point the hotel already knows they’re interested in a specific room type, that they’ve compared prices for particular dates, or that they’ve shown interest in a specific service. That information makes it possible to send a relevant message instead of a generic campaign, and to decide, with real evidence, who is worth targeting with media spend (Google, Meta), because they’ve already shown genuine intent, rather than starting from scratch with cold audiences.<\/p>\n![\"Three](\"https:\/\/www.hotelinking.com\/en\/wp-content\/uploads\/sites\/2\/2026\/08\/Visit_anonimos_WebHotel-inf01-hotelinking-EN.webp\")
<\/p>\nHow this traffic is identified, without compromising visitor privacy<\/h2>\n
From anonymous visitor to named guest: the opportunity<\/h2>\n
How GuestMaker addresses this<\/h2>\n