I turned off my ads because I couldn't tell if they worked

You put $1,500 a month into Google Ads. Maybe a bit into Meta. The dashboard reports "conversions," but you can't square those numbers with what landed in your booking engine. Your bank account doesn't show a clear lift either. After ninety days of staring at a graph you don't trust, you do the rational thing and pause everything.

It feels like discipline. Stop spending on something you can't measure. But here's the catch: you didn't have a spending problem, you had a seeing problem. And the decision to switch off was made on broken data. Since Apple capped tracking cookies at roughly 7 days in 2021, browser pixels stopped reliably tying a booking back to the ad that earned it, so campaigns that were working looked dead on the dashboard.

This is the most common story we hear from independent operators. You ran ads for a few months, couldn't connect the spend to real bookings, so you turned them off. The trouble is, you may have killed campaigns that were quietly filling rooms. You just couldn't see it.

The budget you can't account for either way

When a 30-room property running ads can't trace bookings to spend, the unmeasurable budget at stake sits at a conservative $200–$2,000 a month. That's not the ad budget. That's the slice of it you can't account for either way: ads that may be paying for themselves three times over, or ads that are pure waste. Flying blind, you can't tell the two apart.

Why the booking can't find its way back to the ad

Three things break attribution for accommodation specifically, and they stack on top of each other.

The cookie cap. Apple's Intelligent Tracking Prevention caps most browser-side tracking cookies at about 7 days. Safari does it by default, and the pressure has pushed the whole industry the same way. When a pixel can't read a cookie older than a week, it can't connect a booking to a click that happened earlier.

The long booking window. Accommodation has one of the longest consideration cycles in retail. A guest sees your ad in March, daydreams about the Margaret River long weekend, comes back in April, and books in May. By the time they pay, the click that started it all is eight weeks old, long past the 7-day cookie window. The booking lands as "direct" or "organic," and the ad that earned it gets zero credit.

The multi-device journey. They tap your Meta ad on the train on their phone. They book three weeks later on a laptop at home. Two devices, no shared cookie, no connection. The pixel sees two unrelated strangers, not one guest on a journey.

Put those three together and your dashboard systematically under-counts the bookings your ads produce. The ads look worse than they are. So you cut them. So your direct bookings quietly fall and the OTAs pick up the slack, at 15–18% commission.

The real cost of flying blind

The damage isn't only the wasted spend. It's the bad decisions you make on top of it.

You kill winners. A campaign that returns $4 for every $1 looks like it returns $0, because the bookings arrive outside the tracking window. You switch it off and lose the rooms it was filling.

You feed losers. The opposite happens too. A campaign that looks fine on last-click but actually converts nothing keeps your budget, because you've no reliable signal to move it.

You can't optimise. Bid strategy, audiences, creative — every lever you'd pull needs a feedback loop. Without trustworthy conversion data, you're guessing. The platforms are guessing too, because their automated bidding learns from the same broken signal.

That's how a property ends up spending $1,500 a month and feeling like the money disappears. It doesn't disappear. It just stops reporting back.

The fix: tie the booking to the ad, server-side

The answer isn't a cleverer pixel. Browser-side tracking is the thing that broke. The fix is to move the measurement off the browser and onto the server. Your booking system reports the confirmed booking back to Google and Meta directly, with the value attached, from a source the cookie cap can't touch.

That's what server-side conversion tracking does, and it's built into Accommador as standard. When a guest completes a booking in your branded engine, the platform sends a server-side signal back to the ad networks tying that confirmed, paid booking to the campaign that started it, even when the click was eight weeks and two devices ago.

The practical effect: your Google and Meta reports start showing the bookings they actually drove, at real dollar values. The campaign that looked dead reveals a 4:1 return. The one you were proud of turns out to convert nothing. Now you can scale the first and kill the second, on data instead of a hunch.

This is the softer, plain-English half of the story. The hard part is the decision, not the plumbing: don't switch off ads you can't measure, fix the measurement first.

Where this sits in the bigger picture

Server-side attribution is one piece of a direct-booking engine, not the whole thing. It only pays off if the ads are sending traffic to a booking experience that actually converts — a branded engine that doesn't bounce guests to an OTA the moment their dates miss your min-stay rule. The minimum-stay and nearest-bookable-dates engine that keeps those guests on your own site is part of the same platform.

The order matters. Plug the leaks in the booking engine first, then measure the ads driving traffic to it, then scale what works. Switching ads off because you can't measure them is the one move that guarantees you'll never find out which ones were worth keeping.

The reason server-side attribution is built into Accommador is simple: you can't make good ad decisions on data that systematically under-counts your bookings. The closed-loop direct-sales engine — marketing, booking engine, OTA distribution, payments and Xero reconciliation in one place — starts at $500 AUD/mo per location, everything included. Monthly billing, cancel anytime. Start free.