AI AgentPlatform
PricingSign inBook a demo
Personyze
On your site
Website PersonalizationOne profile across every page and every session.Recommendation EngineWhat each visitor wants next, ranked by the algorithm you pick or one you write.A/B TestingA winner per audience, promoted mid-campaign rather than after it.Dynamic Landing PagesThe headline matches the ad they clicked.AI Search & Chat AgentAnswers from your own pages and catalogue, and a search box that replies in a sentence.Banners & Pop-UpsRight message, right moment, right page — without a developer.Social ProofLive scarcity, ratings and what other people just did.Meeting SchedulerVisitors book time on your own page — the meeting type, host and times picked by who they are.
Off your site
Email PersonalizationSend it from Personyze, or paste one block into the ESP you already use.Push, SMS & WhatsAppFired by what they just did rather than by a schedule.Hosted Landing PagesWe serve the whole page, on your domain or ours. No site to deploy to.
Know who they are
Behavioral TargetingSegments that update themselves from what people actually do.ABM MarketingThe company behind an anonymous visit, joined to your CRM.Website AnalyticsSessions, bounce and revenue — then click a row and there is a person.
Build & connect
MCP ServerRun your account from Claude, ChatGPT or any MCP client.IntegrationsHubSpot, Salesforce, Twilio Segment, Tealium, GTM and the REST API.APIs, SDKs & AutomationOne REST endpoint over every object, server and mobile SDKs, rules and reports that run on their own.
Pricing
Make integration

Personyze as a step in your scenario

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.

M + P

Make  ·  PERSONYZE

Connect with your account API keyRead Personyze data in a scenarioOr let a campaign call Make directly
The problem

The visual builder, for people who think in scenarios.

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.

What it unlocks

Both directions, from one connection.

Read into a scenario

Pull visitor profiles, list membership and campaign results into a Make scenario and branch on what you find.

Write back from one

Update profiles, add and remove people from user lists, and report events into Personyze from anywhere in the map.

Or start from the campaign

The Webhook action means a campaign can call a Make scenario at the moment it fires — no polling, no schedule.

How it works

Connect once, then build.

01

Add your API key

Authenticate with the account API key — the same one the REST API and the other connectors use.

02

Drop Personyze into the scenario

Add the module where it belongs on the map and pick what it should read or write.

03

Or point a campaign at Make

For the outbound direction, add a Webhook action to a campaign and paste the scenario URL. It fires when the campaign does.

Questions

Before you connect it.

Which direction should I use?
Read into a scenario when Make is driving and something in Personyze is an input. Use a campaign Webhook when the site is driving and Make is what should happen next.
Is it the same key as the API?
Yes. One account API key covers the REST API, the MCP server, Zapier, n8n and Make.
What can a webhook carry?
The action posts JSON to any endpoint you name, so the scenario receives the context of the campaign that fired it.
Ready when you are

Put the site on the map.

An API key and a scenario, and the two are talking.

FREE PLAN · NO CARD NEEDED · NOTHING TO INSTALL ON MAKE