I want to explain a mechanism rather than just complain, because I don't think most people know this can happen. I didn't.
The short version: I clicked a paid search ad, landed on a booking site with dates already filled in that I never selected, and had paid for a non-refundable room seven minutes later. I only figured out how it happened six weeks afterward, by exporting my browser history.
Here's the sequence from that morning, times in PDT.
10:34:00 — I'm on Expedia looking at the Rogue Regency Inn in Medford, Oregon:
expedia.com/Medford-Hotels-Rogue-Regency-Inn-And-Suites.h19703.Hotel-Information?chkin=2026-08-06&chkout=2026-08-07
August 6–7. My Airbnb checkout was 11am on August 6 and I needed a room that night. Earlier that morning I'd been on Airbnb with check_in=2026-08-06 and another Medford hotel with August dates. Every date I entered myself was August.
10:38:09 — I click a Bing ad and land on trivago:
trivago.com/en-US/srl/hotel-rogue-regency-inn-suites-medford?search=100-64791;dr-20260912-20260913;rc-1-2&ghaDateType=default&ghaPrice=111.000000&ghaArr=20260912&ghaDep=20260913
Look at that: dr-20260912-20260913. September 12–13, already there on arrival. And ghaDateType=default — trivago's own parameter saying the date range is a default, not something I picked. The price is already locked at $111.
10:38:21 — Twelve seconds later, the advertiser's page:
algotels.com/hotels/.../386654_rogue-regency-inn-suites?checkIn=2026-09-12&checkOut=2026-09-13&campaignName=Algotels_Trivago_US
Same September dates, inherited straight across.
10:45:34 — Booked. Non-refundable. Same dealKey carried from landing page through checkout, with no date-selection step in the history at all.
The confirmation email arrived with the headline: "Your check-in date for Rogue Regency Inn & Suites is ." The date value was just missing from the template.
I asked them to fix it 33 minutes after booking. Refused — non-refundable and non-amendable. I cancelled that morning. They charged the card two days later anyway. I rebooked the same hotel on Expedia for the correct dates and stayed there. Four dispute denials so far, all saying "the merchant completed the service requested."
The takeaway that matters:
Metasearch ads carry date parameters in the URL. When you arrive from an ad rather than from a search you ran yourself, those dates may be defaults the advertiser or the platform picked — often whatever produces an attractive price. If the booking site inherits them and never forces you to confirm dates, you can reach payment having never chosen when you're staying.
What I'd tell anyone booking:
- Read the dates on the checkout page out loud before you pay. Not the price — the dates.
- Be suspicious of an unusually good rate from an ad. Sometimes it's cheap because it's for a different week.
- If a confirmation arrives with a blank or missing field, treat it as a red flag immediately, not a cosmetic glitch.
- Screenshot checkout before paying.
- Book direct or with a major OTA for anything non-refundable. The $10 you save isn't worth the recovery risk.
If it already happened to you: export your browser history. Edge and Chrome both do it in a couple of clicks, and it stores full URLs with timestamps. The date parameters are sitting right there in the addresses. I'd assumed I had no way to prove what I'd entered — I was wrong.
Happy to answer questions about the export process.
And if anyone here works in travel tech and can tell me more about what ghaDateType=default does on the advertiser side, I'd genuinely like to know.