If you advertise your rental on Meta, this OwnerRez feature would get you more bookings for less — please upvote.
I just started running direct-booking ads and hit this roadblock: When someone clicks your ad and books through OwnerRez, Facebook is supposed to record that booking as a "conversion" so it can learn who your best customers are and show your ad to more people like them. But right now, OwnerRez isn't sending Facebook enough info to reliably match the booking back to the person who clicked. So a chunk of your real bookings never get credited to your ads.
Why that hurts you:
- Facebook or Instagram thinks your ads are working LESS well than they actually are
- It can't optimize properly, so you pay more for worse results
- You can't tell which ads are truly driving bookings
The fix: A feature called "Advanced Matching" lets OwnerRez securely send Facebook a bit more (encrypted, private) info at checkout so more of your bookings get correctly counted. It's automatic and privacy-safe once turned on.
Bottom line: more accurate tracking = Facebook shows your ads to better prospects = more bookings for less money.
If you advertise to fill your calendar (now or in the future), please vote this up so it gets the dev team's attention!
Thank you!
Laura Wegner
The Suite Life™ Whistler
For the tech's at OR: Please add Meta Pixel Advanced Matching support! I would love to see OwnerRez pass hashed customer data (email, phone, name) to the Meta Pixel via an Advanced Matching object on the booking/checkout flow.
Currently, the Pixel initializes with a standard fbq('init') call and no matching data, so any conversions that browser tracking misses (ad blockers, iOS/Safari privacy limits, cross-device bookings) go unattributed. Advanced Matching would recover a meaningful share of those, giving hosts who advertise on Meta far more accurate conversion attribution and better ad optimization. Hashing happens automatically, so it's privacy-safe.
For those of us driving direct bookings through Meta ads, this would directly improve our ability to measure and scale what's working... and what's not. This would be a huge techy win!
Hey Laura!
Could you please submit a ticket to help@ownerrez.com about this so we can investigate?
I already did create a support ticket for this.
When I received the support response from Emond de Weerd (pasted below), he suggested I submit a feature request... so that's what I've done : )
This feature is needed.
**********************************************************************
Hi Laura,
1. Advanced Matching: OwnerRez does not currently pass hashed customer information to the Meta Pixel during checkout. Our Pixel initialization is the standard fbq('init', '<your pixel ID>') call without an Advanced Matching object. There isn't a setting for this; the feature isn't implemented in our integration today.
2. Conversions API (server-side): We don't currently send events to Meta server-side via the Conversions API. The OwnerRez Meta integration is browser-Pixel only.
3. Purchase event payload: The Purchase event fires with value, currency, content_category ("OwnerRez Property"), content_name, content_type ("product"), and content_ids (a single ID identifying the booked property). It does not include customer matching data (email/phone/name), that ties into question 1.
Both Advanced Matching and the Conversions API would be great candidates to file as feature requests on our forum so other hosts can upvote them and our product team can gauge interest:
https://www.ownerrez.com/forums/requests
Kind regards,
-Emond
