Bring in data from any system
Post signed JSON from your own booking engine or script to the connection's address, and map its fields to the guest record.
Automation and data
Bring data in from any system, and let your systems react to Engage events.
Signed JSON comes in from your own booking engine or script, and signed webhooks send contact, email, visit, purchase, form and voucher events out to your own endpoint.
Explore customer data in EngageTwo ways to use Webhooks with your Engage marketing.
Post signed JSON from your own booking engine or script to the connection's address, and map its fields to the guest record.
Receive the contact, email, visit, purchase, form and voucher events you choose at your endpoint, and use them to trigger your own processes.
Start with one useful workflow. Check the data and the consent it carries, then approve what your AI team prepares.
Choose the data source, destination and permissions for your connection. Your technical team can use the API, events or file workflow described above.
Review a sample record and confirm the relevant marketing permissions before adding people to campaigns.
Let your AI team prepare the work and, by default, approve each action before it reaches a guest.
Signed JSON comes in from your own booking engine or script, and signed webhooks send contact, email, visit, purchase, form and voucher events out to your own endpoint.
No. Engage works with customer data from your existing tools. WiFi is an optional source of guest and visit data.
By default, you approve each action and campaign before it reaches a guest or spends money, and the AI can never launch or fund an ad. External assistants connected through MCP can read, draft and ask for approval, never send.
Bring your tools into one marketing platform and approve what your AI team stages.