A segment already exists for a reason. Now it can follow your guests onto Meta and Google too: no CSV exports, no manual re-uploads, no stale lists.
A guest checks out for the third time this year, and somewhere in GuestMaker a segment already knows it: "repeat guests, last 90 days," or whatever your team named it. That segment can trigger a WhatsApp message or drop the guest into a journey. Until now, it couldn't follow that same guest onto Instagram or a Google search results page.
That gap is common enough that most hotel marketers have a version of the same workaround: export contacts to a spreadsheet, hash the emails by hand, upload the file to Meta or Google Ads, and repeat the whole exercise every few weeks because the list is stale before it even finishes uploading. Some teams do this quarterly, if that. Most, reasonably, don't do it at all.
Segments in GuestMaker can now sync directly to Google Ads Customer Match and Meta Custom Audiences, continuously, from Settings → Integrations → Ad Audiences. Mark a segment for sync once, and its membership stays current on the ad platform from then on: a guest who enters the segment next week is added within the hour, one who drops out is removed the same way. No export, no manual re-upload, no spreadsheet sitting in someone's downloads folder going stale.
This isn't a tool that reads your contact list once and calls it done. It runs on the same segment engine already driving your journeys and broadcasts (static or rule-based, either works), so an audience built for "stayed in the last year but hasn't booked again" behaves in Google Ads or Meta exactly the way it behaves everywhere else in GuestMaker: it updates itself.
A retargeting pixel knows someone visited your booking page. A segment synced from GuestMaker knows they've actually stayed with you: how recently, how often, which tier of your loyalty program they're in, whether they've gone quiet since their last trip. That's a meaningfully different signal to hand an ad platform, and it opens up audiences a pixel alone never could. A loyalty program with real tier data makes an especially strong seed.
Three worth building first:
For Meta, this really is one click. Choose Continue with Meta, sign in, and GuestMaker finds your ad accounts on its own: no account ID to copy in, nothing to wait on. From there, mark the segments you want synced and they start uploading right away.
Google is usually where an integration like this quietly cuts a corner, so it's worth being precise about what you're actually getting.
The connection is real and it works today. It just isn't a one-click sign-in yet, because Google's own review of our app is still in progress. Until that clears, "Sign in with Google" sits in the product visibly marked Coming soon, rather than pretending to work when it doesn't.
The path that does work today takes a few minutes: open your Google Ads account, go to Admin → Access and security, and add GuestMaker's service account as a user. Back in GuestMaker, click "I've invited it, connect," and your Customer Match audience starts building. No password changes hands. This service-account connection uses the access granted in Google Ads rather than an interactive Google sign-in flow.
Once connected, syncing behaves exactly the same as on Meta: segments upload, membership stays current, nothing further to configure.
Every contact uploaded to either platform has to be marketing-consented and subscribed first, checked through the same consent logic that already gates a broadcast send. That's the same reachability and consent split that your contact database's own analytics already track. There's no separate, looser rule because the destination happens to be an ad platform instead of an inbox. A guest who opted out of marketing emails doesn't quietly reappear in a Meta audience because a segment happened to include them.
Emails and phone numbers are hashed before anything leaves GuestMaker, and formatted to each platform's own rules: Google and Meta don't even agree on how a phone number should look before hashing it, a detail worth having handled once, correctly, rather than by whoever exports the CSV that month.
One honest caveat, worth knowing before you check the dashboard: Google won't start serving ads against a Customer Match audience until roughly 1,000 of the uploaded contacts have matched a real Google account. A smaller segment can sync perfectly (connected, uploaded, green across the board) and simply not be targetable yet. That's a Google Ads rule, not something GuestMaker is holding back, and it's a reason to start with your wider segments: "stayed with us in the last two years" builds a targetable audience faster than "booked the presidential suite in March."
GuestMaker already treats WhatsApp, email, and your loyalty program as one guest record instead of three disconnected tools. Ad audiences are the same guest record showing up in a fourth place: one you don't manage from inside GuestMaker, but one that no longer needs its own separate list. A guest's consent, tier, and stay history stay attached to them wherever the segment sends them next.
Settings → Integrations → Ad Audiences. Connect the platform you already run campaigns on, mark a segment, and it stays synced from there. If Meta is your main channel, that's a two-minute setup. If Google is part of the mix, budget a few extra minutes for the service-account invite: short, and the one that actually works today.
A segment you already built for retention or a WhatsApp journey doesn't have to stay inside GuestMaker to be useful. It can just as easily be the audience your next ad campaign is built on.
Thirty minutes, your real properties, no generic demo environment.
The traditional loyalty build takes months of vendor calls and shifting launch dates. Here's what actually has to get decided, and how to launch fast.
Your best guest has stayed at four of your hotels, and your systems have no idea they're the same person. Here's what actually fixes that.
Seven live analytics tabs turn a hotel group's contact database into direct answers, and every number is one click away from the exact guests behind it.
