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
Your systems add and read contacts, tags, events and consent in Engage.
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, then decide how much control to give your agent.
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.
Set your goal
Let your agent prepare the work. Approve each action, or enable autopilot within the limits you set.
Questions
What connects between Public REST API and Engage?
Your systems add and read contacts, tags, events and consent in Engage.
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?
You choose. Approve each action and campaign, or let your Engage agent run agreed workflows on autopilot within your limits. External assistants connected through MCP have read and draft access.
Make your connected data work harder
Bring your tools into one marketing platform. Set the goal and choose your level of control.