Personyze
Scan your siteA first AI personalization plan for your site: the best ideas drawn on your own pages, before you have any data.
Starts right away · about 4 minutes · no email needed
Website & app
Website PersonalizationContent, offers and layout shaped to each visitor — one 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 whole page recomposed per visitor — headline, imagery and offer from the ad they clicked and their own interests. On pages you already run.AI Search & Chat AgentAnswers from your own pages and catalogue, and a search box that replies in a sentence.Banners & Pop-UpsYou decide who sees each banner or pop-up — by behavior, source, location or CRM field — and when it appears.AI Promotion ManagerYou list the offers; the AI picks the one each visitor sees and keeps learning from what converts.Social ProofLive scarcity, ratings and what other people just did.
Email, push & SMS
Email PersonalizationContent and recommendations picked per reader at open time — sent from Personyze or pasted as one block into your ESP.Push, SMS & WhatsAppFired by what they just did rather than by a schedule.Hosted Landing PagesThe same per-visitor page, served by us — your domain or ours, no site to deploy to.
Targeting & analytics
Behavioral TargetingSegments that update themselves from what people actually do.Audience DiscoveryPlain-language audiences found in your own data — visitors who convert several times more often than average, targetable in a click.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.
Platform & integrations
MCP ServerRun your account from Claude, ChatGPT or any MCP client.IntegrationsHubSpot, Salesforce, Twilio Segment, Tealium, GTM and the REST API.App MarketplaceThe integrations built in to every plan, and apps from other companies that Personyze reviews before listing.APIs, SDKs & AutomationOne REST endpoint over every object, server and mobile SDKs, rules and reports that run on their own.Inspire meType your site: who visits, what to show each of them, and the best ideas drawn on your own pages.
Reviews, surveys & chat
Reviews & TestimonialsReviews from 17 platforms and your own site, matched to each visitor.Surveys & NPSOne question or a whole survey — every answer ready to target.AI Chat AgentAnswers visitors’ questions from your own pages, and hands over to a person.Meeting SchedulerThe right visitors book time with your team, on your own page.
PricingVideosProduct TourShort narrated videos of the real platform, one feature at a time.
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