Google Ads
Your Travel Bids Still Work. The Field Names That Control Them Do Not.

Updated: October 22, 2026
Google Ads API v26 replaces hotel-specific bid-modifier field names with vertical-agnostic names while preserving the existing criteria and targeting behavior. The safe migration is a schema change with a business-logic regression test—not a fresh bidding strategy.
What changed in v26
Fields such as hotel date selection, advance booking window, length of stay, check-in day and check-in date range now map to more general names including user-set dates, advance booking window, length of booking, start day of week and start date range. Google states that criterion IDs and existing bid-modifier behavior remain the same.
That sounds mechanical, but production systems often embed field names in validation, data warehouses, dashboards, bulk editors and QA scripts. A compiler-clean client library does not prove that the reporting layer still labels a seven-night stay correctly.
Map the old and new concepts
| Old hotel concept | v26 concept | Regression check |
|---|---|---|
| Date selection type | User-set dates | Same eligible search behavior |
| Advance booking window | Advance booking window | Same day boundaries |
| Length of stay | Length of booking | Nights map to days without conversion |
| Check-in day | Start day of week | Timezone and locale unchanged |
| Check-in date range | Start date range | Inclusive boundaries preserved |
Run the migration in four layers
- Update typed client references and request builders.
- Map stored configuration keys without rewriting business values.
- Backfill warehouse dimensions or aliases used by reports.
- Compare pre- and post-migration requests against the same campaign sample.
Test edge cases, not only common bookings
Validate zero-day and long booking windows, minimum and maximum stay boundaries, week transitions, daylight-saving changes and date ranges spanning year end. If the system generates modifiers from a revenue-management feed, replay a historical file and compare the resource names, criteria IDs and modifier values.
Keep the commercial owner involved. Engineers can prove parity in payloads; revenue teams can identify a technically valid rule that no longer matches the property’s pricing strategy.
Separate migration noise from bidding performance
Freeze unrelated modifier changes during the cutover. Record the client-library version, deployment time and campaigns included. Monitor API errors, modifier counts and coverage first; evaluate revenue or booking outcomes only after technical parity is confirmed. This prevents ordinary demand shifts from being misdiagnosed as a migration defect.
For broader governance, connect the process to MTC’s channel-prioritization budget guide and offline conversion migration QA.
Frequently asked questions
Do existing bid modifiers need new values?
Google’s release notes say existing IDs, targeting behavior and values carry over; the integration fields must change.
Should nights be converted to days?
No additional conversion is required for the migrated minimum and maximum values.
What proves success?
Matching criteria, modifier values, API coverage and reporting labels across a representative campaign sample.
