.svg)
For hotels and resorts on
, running
or moving to it
Every PMS and CRS reservation, in Braze within seconds
The confirmation your guest opens is the one your team wrote. No custom build, and nothing for your engineers to maintain.
Listed Braze AmplifierPMS: Property Management System. CRS: Central Reservation System.
Guest books in OPERA Cloud
Branded Braze email in the guest's inbox
Sent by a campaign your team owns.
The same booking, without a live integration
Until then the guest has the confirmation OPERA sent.
Connects
Oracle OPERA Cloud to Braze
Through OHIP, Oracle's hospitality integration platform
Speed
Booking to inbox in 15 to 30 seconds
Measured in staging
Runs in
Your own cloud
Braze EU and US clusters
Live in
Under 10 days
For the deployment below, subject to scoping
Validated with Wynn Al Marjan Island before it opened
A luxury integrated resort on OPERA Cloud and Braze. CustomerIK scoped, configured and tested the integration end to end inside the resort's own cloud, so guest journeys ran from opening day.
Reservation created in OPERA to branded email in the guest's inbox, measured in staging
OPERA event to Braze, measured in staging
Sustained in load testing, beyond peak property volume
The same feed now runs pre-arrival, in-stay, post-stay and win-back journeys, with no further integration work.
There is no off-the-shelf connector between OPERA Cloud and Braze.
That is what any connector would have to do, and what generic integration tools and low-code platforms do not. Live reservation data leaves OPERA Cloud through OHIP, Oracle's streaming interface, so without a connector the alternative is a custom build.
- Generic toolsConduit
- Hold an authenticated session and manage the token lifecycle—✓
- Speak OHIP's streaming protocol—✓
- Hold and maintain an event subscription—✓
- Create a guest in Braze who does not exist there yet—✓
One feed, every guest journey
Conduit puts the reservation data into Braze and stops there. You build the confirmation, the upsell and the win-back as Braze campaigns and Canvases, change them whenever you want, and never wait on an integration ticket to add one.
BookingInstant confirmation
Branded and personalised, seconds after the booking.
Before arrivalPre-arrival
Upgrades, dining, spa and transfers, timed from the real arrival date.
Arrival dayCheck-in
Guidance and welcome messaging aligned with the front desk.
During the stayIn-stay
A booking change updates the profile, so journeys stay accurate.
After departurePost-stay
Feedback and rebooking triggered from departure.
One Conduit feed from OPERA Cloud
Created · Modified · Cancelled
Cancellation win-back
A cancellation in OPERA opens a recovery journey the same minute.
What your IT team will ask
Three questions, answered in the order they come up.
Can a booking be lost?
No. Every event is written to a ledger before it is processed, and cleared only when Braze confirms receipt.
- Duplicate suppression and automatic retry
- A scheduled sweep that reconciles against OPERA
- Alerting to your team
- Full event history, available for audit
An outage becomes a delay rather than a missing confirmation.
Where does guest data sit?
Not shared software. One deployment, inside your own cloud tenancy, in the region you pick. Outbound connections go to Oracle and Braze and nowhere else, and the Braze key is scoped to user tracking and campaign triggering.
Orchestration framework
Streaming client, processing pipeline, schedulers and error paths. CustomerIK IP.
Encrypted credential store
Oracle client secret, application key and Braze REST key. Never in workflow definitions or source control.
Event ledger
PostgreSQL. Holds guest data for audit and replay, under your retention and access policy.
Monitoring and alerts
Stale, failed and latency checks, streaming connection health, sweep anomalies, routed to your team.
Nothing inbound crosses the boundary. Inbound traffic is limited to the authenticated streaming-to-runtime hop inside your own environment.
Who runs it after go-live?
Your choice, settled during scoping. The deployment stays in your tenancy either way.
Building it yourself costs hours once and ownership forever
Custom build from scratchEstimated 300 to 400 hours
Conduit, configuredEstimated under 100 hours
A custom OPERA to Braze build runs an estimated 300 to 400 engineering hours before it carries a single booking. Conduit is configured in under 100. The framework already exists, so the work is configuration and validation rather than writing software. That is where the difference comes from.
The hours end. The ownership does not. OHIP changes, Braze changes, credentials rotate, and someone inside the hotel carries that for as long as the integration runs. With Conduit, CustomerIK carries it. We track OPERA Cloud and OHIP releases and patch the framework centrally, so your deployment stays current without anyone at the hotel scheduling it.
What ships today
Anything beyond this is scoped as part of the engagement rather than assumed.
Source
Oracle OPERA Cloud through OHIP. Other PMS platforms are assessed case by case.
Events
Reservation created, modified and cancelled. Further OPERA events on request.
Mapping
Guest and stay attributes mapped to your Braze data model, not a fixed schema.
Attributes carried
Arrival and departure dates, nights, room type, rate code, occupancy, confirmation number, property code, booking channel.
Conduit captures the event from the OHIP stream, adds guest and stay context, and writes a profile update and a custom event into Braze.
Your first ten days
What happens after the call, and who does what. Project timelines may vary, assessed case by case.
Scope
We review your OPERA setup and your Braze workspace, agree the events that matter, and settle who runs it.
Configure
Conduit is configured for your property and tested end to end outside production, with your team wiring the Braze campaign.
Go live
A controlled test window, verified delivery, and an audit trail from the first booking.
Get a quote
Thirty minutes with the person who administers your OPERA integrations and whoever owns your Braze campaigns. You leave with the events worth streaming, the operating model that suits your team, and a price for a one-time configuration with an optional managed service.
And a dated deployment plan.
If you are still moving to Braze, Conduit is scoped alongside the implementation, so reservation events are live at launch rather than after it.
Or write to hello@customerik.comThe team behind Conduit
CustomerIK is an independent martech firm and a Braze Solutions Partner. We work across the customer engagement stack, from the data upstream of Braze to the campaigns inside it. Conduit came out of that work.
.svg)
