Google has added an official notice that existing Travel campaigns will begin moving to the new Search campaigns for Travel structure in the third quarter of 2026. Google will automatically create new Search campaigns and mirror the closest equivalent settings from the original campaigns. Advertisers can also choose to transition manually before the migration date assigned to their account.
For travel brands, the significance is not a naming change. An account that uses feeds to promote hotels, experiences, events, or transportation inventory may be moving its budgets, bidding, conversions, search-term visibility, and reporting into a new campaign container. “Closest equivalent settings” does not mean identical outcomes. Teams need to make a deliberate choice between waiting for automation and running a controlled manual pilot.
What changed?
The warning in Google's Hotel Center Help is explicit. Travel campaign migration to new Search campaigns for Travel starts in Q3 2026. Google will create the new campaigns automatically, using the closest available equivalents for settings in the original Travel campaigns. The precise date will arrive through account notifications and email.
The notice appears on a reporting page in the Things to do documentation cluster. The most directly confirmed migration scope is therefore legacy Travel campaigns built around activity and experience inventory. Google's broader product page shows the direction of travel: Travel Promotion Ads, Booking Links, and travel feeds are moving into the Search campaign ecosystem, with expansion toward verticals such as Events and Car Rentals. It would still be unsafe to assume that every hotel, flight, or travel account will move on the same day under the same rules.
This text-free Fark Studio illustration shows separate Travel campaign structures moving through a migration gate into one Search campaign flow while equivalent settings are carried forward. It is not a Google Ads interface.
The new model continues the Search campaigns for Travel direction Google introduced in May. Google is positioning travel assets inside an AI Max-enabled Search ecosystem with the full Search bidding suite, data-driven attribution, keyword and search-term reporting, and tROAS automation for travel assets in one buying path.
Who is affected?
Businesses advertising activities and experiences through a Things to do or Actions Center feed are the first group. Tour operators, museums, theme parks, ticketing platforms, experience marketplaces, and their connectivity partners fall into this category. Reports, automations, and budget rules tied to the old campaign structure need to be tested against the new campaign identity.
Hotel groups, chains, and online travel brands connecting broader inventory to Search strategy form the second group. Google's product page places Booking Links, Travel Promotion Ads, and travel feeds within shared Search infrastructure. That can make brand demand, generic destination demand, and dynamic travel assets more visible in the same budget conversation. It can also make individual format contribution harder to read if the campaign is not segmented and reported carefully.
Agencies and measurement teams are the third group. The identity, naming standard, portfolio bidding relationship, conversion actions, reporting connectors, and dashboard filters of an automatically created campaign may not match the legacy campaign. Continued ad delivery is not proof that the data pipeline also continued without a break.
What is confirmed and what remains uncertain?
The confirmed facts are narrow but operationally important. Migration starts in Q3 2026. Google will create a new Search campaign and mirror the closest equivalents of the old Travel campaign settings. Advertisers can transition manually first. The exact timing will be delivered through account notifications and email.
Account scope is the first uncertainty. Google has not published one worldwide cutover date or a separate Türkiye schedule. Because the notice sits within Things to do reporting documentation, teams using other travel formats should not treat their own migration as confirmed until the relevant account notice appears.
Performance equivalence is the second uncertainty. “Closest equivalent” does not guarantee that budgets, bidding, targeting, and assets will behave identically. The new campaign type works with AI Max, Search bidding, and different reporting dimensions, so auction reach and optimisation signals can change.
Historical comparison is the third uncertainty. The notice promises a newly created campaign, but it does not promise that every report, custom column, external connector, or experiment design will automatically map to the new identity. Teams should create their own migration table for before-and-after analysis.
What should brands do now?
1. Identify affected accounts. Inventory Travel campaign types, Things to do or Actions Center connections, and active travel feeds across Google Ads and manager accounts. Record the connected product and data source, not only the campaign name.
2. Assign an owner for notifications. Because the exact date arrives by email and in-account notice, make sure it does not remain with a former employee or an agency-only user. Update administrator access and technical contact addresses.
3. Map dependencies. List automated rules, scripts, Looker Studio reports, warehouse queries, budget tools, and naming filters that use the legacy campaign identifier.
4. Freeze the conversion baseline. Verify which action records bookings, ticket sales, leads, calls, and revenue value. Separate primary and secondary conversions so the new structure does not optimise toward the wrong outcome.
5. Check feed health. Resolve product IDs, prices, availability, landing pages, and policy errors in Actions Center or the connectivity provider before migration. Moving broken inventory does not repair it.
6. Decide on a manual pilot. Instead of moving the entire high-volume account, choose a representative market, destination, or product group with contained spend. Compare reach, search terms, conversion value, and cost quality between the two structures.
7. Set guardrails. Put daily budgets, portfolio bidding, negative keywords, location, language, brand restrictions, and final URL behaviour into a pre-launch review.
8. Prepare reporting continuity. Store the old ID, new ID, migration date, and business objective in a common warehouse mapping table. Annotate the artificial break that will appear in trend reports.
9. Do not stack changes. If budget, creative, bidding, and the conversion model all change on migration day, you cannot isolate the cause of a performance shift. Sequence major changes.
10. Monitor the first two weeks separately. Set daily alerts for delivery, query quality, feed coverage, conversion delay, revenue, and tROAS, as well as under-spend or an unexpected traffic surge.
This Fark Studio workflow moves from account notification through dependency inventory, feed and conversion validation, manual-versus-automatic transition, and performance protection. It is not a product-screen reproduction.
Manual transition or automatic migration?
A manual transition is usually stronger for teams that understand a high-value account's dependencies and can run a controlled test. It lets them learn the new campaign structure with limited exposure, validate reporting mappings in advance, and observe budget guardrails. The cost is managing two structures temporarily and preventing auction overlap.
Automatic migration may be practical for a low-volume account or a team with limited operating capacity. But “Google will handle it” is not the same as a complete control plan. Mirroring the closest settings does not own the business objective, feed quality, or external reporting relationship.
Use four questions: How much revenue does the legacy campaign produce? How many external systems depend on its ID? How healthy are the feed and conversion data? Can the team support a two-week controlled test? High revenue and many dependencies increase the value of a manual pilot. A low-risk account may wait for the automated date, but the pre-migration audit still applies.
Where should teams wait?
If no notice is visible in the account, do not close campaigns based on an assumed cutover day. Google's official wording says account-level timing will arrive through notifications. Do not restructure every Hotel Ads or Performance Max setup from one industry report either.
Verify the measurement foundation before activating AI Max and the new Search capabilities. Broader query reach combined with weak conversion signals can amplify waste. The product promise is more control and one performance view, but actual account outcomes still depend on feed quality, bidding, demand, and measurement.
Fark Studio perspective
This migration shows the wall between a “feed campaign” and a “Search campaign” becoming thinner in travel advertising. Travel inventory is connecting more directly with Search bidding, search-term insight, and AI Max. The opportunity is a more unified decision model. The risk is misreading a complex account through one consolidated campaign view.
At Fark Studio, performance marketing, digital marketing, and tourism and healthcare sector experience share the same feed, conversion, and revenue vocabulary. Preserving that vocabulary through the campaign-type change can turn a technical migration into a better budget model.
If your Travel campaign, Actions Center feed, or tourism measurement architecture is affected, plan a pre-migration Google Ads audit with Fark Studio. The first step is not rebuilding the campaign. It is making the dependencies and business objective visible.
Sources
Google Hotel Center Help, About Travel Campaign Reporting in Report Editor, current official documentation; Q3 2026 migration notice.
Google Accelerate, Search campaigns for travel, May 20, 2026; product direction and announced capabilities.
Google Hotel Center Help, About Travel campaigns for Things to do, current official documentation; feed and account-linking scope.
Search Engine Roundtable, Google Travel Campaigns Migrating To Search Campaigns For Travel, August 11, 2026; radar coverage and summary of the official notice.
