Personyze
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.
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.
REST API integration

Everything the panel does, over HTTP

One authenticated API covering profiles, lists, catalogs, campaigns, decisions and reporting — plus server-side SDKs for Node, PHP and Python, and native SDKs for Android and iOS.

{;} + P

REST API  ·  PERSONYZE

HTTP Basic with your account keyServer-side decisions in one callNode, PHP, Python, Android, iOS
The problem

Some pages are rendered before a browser is involved.

Server-rendered frameworks, native apps, kiosk screens, and anything behind a login all need the decision before the markup exists. The same audiences and the same campaigns are reachable from your own code, in one call, without waiting for a tag to load.

What it unlocks

Four ways in.

The REST API

Visitor profiles and custom columns, user lists and membership, ranked interests, product and content catalogs, campaigns, actions, placeholders, goals, events, forms and aggregated results.

Server-side SDKs

Node, PHP and Python ports of one endpoint, with a shared written contract so all three behave identically — sessions, decisions, events and purchases in a single call.

Mobile SDKs

Android and iOS handle the session lifecycle, report navigation and interactions, and render returned content into a view you position.

How it works

It fails in the right direction.

01

A budget, not a hope

The whole decision, retries included, is bounded at 1000 ms. It does not get to hold your page open.

02

Fail open on reads

A timeout, a connection error, a 5xx or simply no matching campaign all resolve to an empty decision set. Your page renders either way.

03

Fail loud on configuration

A 400 or 401 raises, even from the decision call — because a bad key is a bug, not weather.

Questions

Before you connect it.

How is it authenticated?
HTTP Basic: the username is the literal api and the password is your account API key. The same key the MCP server, Zapier and the community nodes use.
What happens if Personyze is slow?
Nothing, on your side. The read path is fail-open with a one-second ceiling on the whole operation, so a slow or unreachable service produces an empty result rather than a blocked render.
Can I run an A/B test server-side?
Yes, but the decision endpoint only returns actions built for it. Assemble a server-side test from the server-side decision action type rather than from ordinary browser actions, or it will return nothing.
Do I need the JavaScript tag as well?
Not for decisions. The tag is what collects behaviour automatically; if you are server-side only, you report what matters through the same API.
Ready when you are

Read the reference, or just try it.

The API key is in your account settings on every plan, including the free one.

FREE PLAN · NO CARD NEEDED · NOTHING TO INSTALL ON REST API