Add customer context
Create and read contacts, tags and events from your own systems.
Automation and data
Public REST API + Purple Engage
Build the connection your business needs.
What connects with Engage
A documented public API with 31 paths and 14 scopes lets your systems read and write contacts, tags, events and consent.
Explore customer data in EngagePut the connection to work
Two ways to use Public REST API with your Engage marketing.
Keep consent connected
Read and write consent as part of the integration you build.
From connection to campaign
Start with one useful workflow. Check the data and the consent it carries, then approve what your AI team prepares.
Connect your account
Choose the data source, destination and permissions for your connection. Your technical team can use the API, events or file workflow described above.
Check the data and permissions
Review a sample record and confirm the relevant marketing permissions before adding people to campaigns.
Approve the first campaign
Let your AI team prepare the work and, by default, approve each action before it reaches a guest.
Questions
What connects between Public REST API and Engage?
A documented public API with 31 paths and 14 scopes lets your systems read and write contacts, tags, events and consent.
Do I need Purple WiFi?
No. Engage works with customer data from your existing tools. WiFi is an optional source of guest and visit data.
Who controls the campaigns?
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.
Put this connection on one guest record
Bring your tools into one marketing platform and approve what your AI team stages.