Google Things to Do Ads: The Operator Setup Guide

Most operators open Google Ads expecting a familiar search campaign. Then the booking feed doesn't sync, the landing page doesn't match, and the account sits there with almost no room for manual tinkering. Google Things To Do ads only work when the inventory, page, and conversion path are already wired together, which is why the channel behaves more like a retail feed than a keyword build.

That difference is the whole job for a tour and activity business. Google runs Things To Do as a defined Google Ads format for tours, activities, and attractions, with its own API for campaign and inventory management (Google's Things To Do ads overview). It is a productized channel, not a test feature. The operator who treats it as a feed-driven placement gets further, faster, because the campaign is only a thin layer on top of the booking system.

What Google Things To Do Ads Are

Treat Google Things To Do ads as a placement that connects a traveler's intent to structured inventory. Someone looks for an experience, Google matches that intent against your product data, and the ad is built from the feed, not from a hand-picked keyword list. The channel behaves closer to a booking inventory system than to a standard search campaign.

Google is direct about the category: it is a Google Ads format for tours, activities, and attractions, backed by a Things To Do ads API for campaign and inventory management (Google Things To Do ads overview). For operators, that confirms defined rules and an official product, not a workaround.

Practical rule: if the feed is wrong, the ad is wrong. Campaign settings cannot fix stale titles, mismatched prices, or missing inventory.

What operators can actually control

The control surface is narrower than most search advertisers expect. The feed generates the creative, so the levers are geo-targeting, budget, and bidding — not keywords or ad copy. That feels limiting, but it strips out the low-value testing that standard search accounts drift into.

For teams used to managing campaigns by hand, that is the shift to absorb. There is no search term to shape with copy tests and match types. The account works like a commerce layer, where product quality, eligibility, and destination intent decide whether the inventory shows at all.

Feed first, campaign second. The feed is what Google reads; the campaign is what Google spends against. Get that order wrong and the setup turns into guesswork.

Building the Campaign in Google Ads

A Things To Do build starts with the feed and the account link already in place. Once those are wired, the Google Ads side is narrow: the campaign uses advertising_channel_type=TRAVEL, advertising_channel_sub_type=TRAVEL_ACTIVITIES, a TravelCampaignSettings object carrying the travel_account_id, and MaximizeConversionValue as the bidding strategy (Google campaign creation guide). That gives Google the campaign shell. The inventory and pricing still come from the travel system behind it.

The setup logic that matters

MaximizeConversionValue only does its job when the conversion value reflects real booking revenue. If the booking platform sends back a placeholder, the strategy optimizes toward a number that has nothing to do with what you collected. The campaign then chases traffic that looks efficient on paper while missing the bookings that pay the bills.

The feed and pricing live in Things To Do Center, not in the Google Ads API. That split stalls a lot of first builds. Operators hunt for a field in the ad account, then wonder why the inventory won't change — but the campaign is only the delivery layer, and the feed is the source of truth.

Keep campaign ownership close to the commercial side and feed ownership close to operations, because the decisions are different. The campaign needs budget discipline and booking economics; the feed needs accurate product data, live availability, and clean mapping from the booking system. A team can run both in-house, or lean on paid search management when the account needs one person keeping both sides aligned.

The campaign should be the last thing built, not the first thing discussed.

Why the account structure is unforgiving

There isn't much room for improvisation here. If the travel account link is wrong, the feed is stale, or the booking inventory no longer matches what the campaign expects, delivery gets erratic fast. The setup is compact, and every field carries weight.

That is why a clean release process beats a loose marketing test. Confirm the feed, confirm the account link, confirm the bidding strategy, then launch. A careful build is easier to scale than a clever one.

Writing a Feed That Google Will Approve

A feed passes review when the inventory row matches the booking flow end to end. Google expects partner-provided data to match the landing page, allows only one listing per product, and rejects near-duplicate products that blur the catalog or distort ranking. Titles cannot carry promotional wording, including discount or flash-sale language (Google Things To Do policies).

What compliant naming looks like

A title should identify the experience, not pitch it. For a multi-day hike, “Multi-Day Alpine Trek with Guide and Camping” reads like inventory. “Best Epic Adventure Deal” reads like a rejected feed row. The first describes the product; the second advertises inside the title, which Google does not want.

For a half-day city tour, “Half-Day Old Town Walking Tour” works. Format details the traveler actually gets — private, small-group, sunset — can help, as long as they reflect what is on sale. The test is simple: would a traveler recognize the product on the landing page and get exactly what the feed promised?

Imagery follows the same rule. Google wants title and photos to match the experience, so stock images and generic destination shots become a problem when they don't reflect what's sold. Operators who run tight product catalogs tend to have fewer issues, because each row is easier to keep current (Google Things To Do policies).

Why small feed errors suppress delivery

One stale row can suppress a product without making a visible mess in the account. Duplicates add ranking noise, and near-duplicates make the product set harder for Google to read. Feed cleanup is eligibility work, not cosmetics.

Review each listing like a manifest line before departure: if the title, photos, and real product don't match, fix the row before launch. For connecting the feed to an actual booking stack, Samba's guide to Google Things To Do for tour operators walks through where feed data has to line up with live availability.

Designing Landing Pages That Pass Review

A Things To Do landing page is a checkout page first and a marketing page second. Google expects the deeplink to surface the exact product the traveler clicked, with the title, attributes, description, price, currency, and a button to start checkout visible on the page. The price has to be easy to see and has to match the inventory feed, which is why the Google landing page guidelines matter during review.

What “most prominent” means in practice

A page that opens with a generic homepage hero, a full navigation menu, and the tour tucked halfway down is already in trouble. The linked product needs to sit at the center of the page — not inside a tab, a modal, or a hidden accordion. If the page shows more than one price, the advertised product's price has to be the most prominent one there.

That is why direct-response booking pages fit this channel better than broad brand pages. A structured trip page already has the right shape when it leads with the itinerary, inclusions, price, currency, and a clear checkout action. A page built mainly to tell the brand story usually fails the visibility test, because the product isn't dominant enough.

The mechanics matter less than the result: the bookable item stays visible, actionable, and price-transparent. A WordPress booking widget can keep the product on your own site while still presenting the offer clearly — the point isn't the widget, it's whether the traveler can see and act on the price without hunting for it.

Rule of thumb: if the traveler has to hunt for the price, Google will treat the page as weak.

Why price matching matters so much

Price inconsistency creates friction before the booking even starts. If the feed says one thing and the page says another, the traveler loses confidence and review gets harder. Google requires the on-page price to be easy to see and to match the feed.

A strong landing page doesn't need to be flashy. It needs to be obvious. Clear product visibility, clean price matching, and a direct start-to-checkout path are the core conditions.

Wiring Bookings, Payments, and Conversion Tracking

The revenue path has to be connected end to end. A click lands on the trip page, the traveler checks out, payment clears, and the booking value returns to Google Ads as a conversion. If the account only measures visits or form submissions, the bidding model learns the wrong lesson and starts optimizing toward activity instead of bookings.

What the conversion should represent

The event that matters is the paid booking, not the inquiry. That is the point where the business has real value and can judge whether the spend made sense. A value-passing purchase event is critical for value-based bidding, because the strategy only works when the conversion amount reflects what was actually collected.

The booking and payment layer has to sit in that path: checkout connected to a processor like Stripe, with the paid booking record as the source of truth. If you're wiring that up, setting up online payments cleanly comes before any ad spend — a checkout that fires reliable purchase events is a prerequisite, not a nice-to-have.

The common failure mode is simple. Teams celebrate a high conversion count because every form submission fires a conversion, then discover the bookings never closed. That produces inflated ROAS, bad bidding signals, and a false sense of channel health.

What should fire and why

A clean setup tracks the journey in three stages:

• Begin checkout, to see whether ad traffic reaches the point of intent.
• Purchase, to mark the completed booking.
• Purchase value, to pass actual revenue back into Google Ads.

Those events have to reflect the real checkout, not an estimated value or a copied lead metric. If the feed says one thing and the checkout collects another, the whole system goes noisy.

Google also notes that Things To Do ads are generated automatically from business information and product feeds, and that feed data like images, title, and ratings only comes into play once accounts are allowlisted and linked to the feed integration (Google Things To Do overview). Tracking and allowlisting aren't side tasks; they're part of the same operational chain.

Bidding and Targeting Without Keyword Control

The hardest mindset shift is accepting that Things To Do gives no keyword-level control. The channel is triggered by broad destination intent, so the levers are geo-targeting, budget pacing, and bidding strategy. Narrower than standard search — but it forces the account to stay tied to real booking economics.

What to do with that constraint

Start with Maximize Conversion Value and keep the budget modest until the feed and landing page prove themselves. Google can't optimize for value if the account is starved of clean conversion data or the bookings are mis-valued. Raise spend only after the listings and checkout perform reliably.

Target ROAS can make sense later, once the account has enough conversion history to support a stable model. Jump to tight ROAS targets too early and the algorithm chokes delivery before it has the signal to learn. Feed quality comes before bid aggressiveness.

For a wider framework on when to run conservative versus aggressive bid settings, the HireMediaBuyers bidding strategy guide is a useful companion read. Things To Do is still its own environment, but the discipline around budget and return targets carries over.

How to sanity-check early performance

Independent travel-industry reporting gives a baseline to check yourself against. In 2023, tourism-marketing firm TOMIS reported that its average Google Things To Do campaigns for urban clients generated about 516,000 impressions, 2,750 clicks, a 0.75% click-through rate, $1,000 in cost, $2,000 in revenue, and a 2x ROAS; for outdoor recreation and activity clients, it reported about 514,000 impressions, 3,732 clicks, a 0.74% CTR, $1,200 in cost, $11,000 in revenue, and a 5x ROAS (TOMIS reporting).

Those numbers aren't a promise; they're a reference point. They help you judge whether the account is behaving like a workable direct-booking channel or just burning spend on thin inventory.

A 30-Day Launch Plan and Measurement Checklist

The first month is about wiring, not scaling. Week one belongs to the feed audit and eligibility checks: confirm the business is claimed on Google, confirm the booking system is a Things To Do connectivity partner (or connected through a channel manager that is), and confirm allowlisting — no campaign should launch before the account can receive and serve inventory. Week two is the campaign build and landing page QA, including price matching and checkout visibility.

Week three is the soft launch. Keep the budget capped, confirm that clicks land on the right product page, and verify that booking events fire with the correct value. Week four is the review point: weak listings get fixed, stronger ones stay live, and target ROAS only enters the conversation once the account has enough real booking data to support it.

A good measurement checklist asks hard questions:

• What is the cost per booking?
• Which bookings did Google Things To Do ads assist?
• Are repeat travelers showing up in the booking data?
• How much revenue is still routing through [OTAs instead of direct checkout](https://www.sambahq.com/ota-supplier-guide/ota-vs-direct-booking)?

If the answers aren't clear, scaling budget is premature. The goal is not more clicks — it's a cleaner route from destination intent to paid bookings.

For operators ready to connect ads, checkout, inventory, and operations in one place, Samba gives tour businesses a booking and payment layer that sits underneath direct-response campaigns like Google Things To Do ads. When the feed, landing page, and payment flow already have to work together, that's where to start.