20-minute walkthrough with 2–3 personalized examples on your real pages.
Email, chat, or 24/7 phone support included on every paid plan.
One visitor profile behind all of it. Anything you build in one place is available in the others.
Connect with an API key, and send what happens on your site anywhere a Make scenario can reach — with a webhook action to push the other way when a campaign fires.
Make · PERSONYZE
Make lays a workflow out as a map rather than a list, which suits the branching, multi-step processes that grow around a marketing team. Personyze fits in it the same way anything else does — a module with credentials, an output, and whatever you connect downstream.
Pull visitor profiles, list membership and campaign results into a Make scenario and branch on what you find.
Update profiles, add and remove people from user lists, and report events into Personyze from anywhere in the map.
The Webhook action means a campaign can call a Make scenario at the moment it fires — no polling, no schedule.
Authenticate with the account API key — the same one the REST API and the other connectors use.
Add the module where it belongs on the map and pick what it should read or write.
For the outbound direction, add a Webhook action to a campaign and paste the scenario URL. It fires when the campaign does.
An API key and a scenario, and the two are talking.