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.
One decision layer over your site, your email, your push and your data — and the sixty-odd capabilities that layer is made of. Grouped the way the platform is built, not the way a price list is written. Where a capability has a page of its own, the card links to it.
Every campaign begins with a rule about who is on the page. Personyze resolves that person from behaviour on your own site, from the systems you already pay for, and from the request itself — before the page finishes painting.
Rules over what a visitor has actually done — pages and page groups seen, products and articles viewed, searches run, time on site, scroll depth, visit number, days since last visit, cart and purchase history.
Match the anonymous session to a record you already hold and target on it: lifecycle stage, plan, owner, renewal date, open opportunity. The lookup is server-side, so the rule is decided before anything renders.
Resolve the company behind an anonymous visit from its IP and firmographics, then treat every visitor from that company as one account — industry, size, revenue band, technologies, intent.
Country, region, city, timezone and language off the request, with no round trip. Enough to greet a New Yorker differently from a Londoner, and to know what the weather is doing where they are.
Your own fields on the visitor profile — written by the tracking code, an API call, a form submission or an integration — and then targetable like anything else. First-party data, kept as yours.
Named, reusable segments built from any combination of the above, with a live forecast of how many visitors match before you turn anything on.
Referrer, search term, UTM parameters, ad campaign and QR entry — so the landing experience can finish the sentence the ad started.
Device class, OS, browser, screen size, connection and whether this is the first session on this device.
All of it is targeted by the same audience rules, all of it is A/B testable, and none of it needs a developer once the tracking code is in.
Modal, slide-in, bar, corner, full-screen and inline — built in a visual editor, targeted by audience, capped by frequency, and measured against a control group.
Fire on the mouse leaving for the tab bar, on a back gesture, or on a mobile scroll-up — the last honest moment to make an offer.
Change the page rather than cover it: replace text, swap an image, change a number, rewrite a CTA, reorder a menu — picked with a visual picker, no code, no flicker.
Multi-step forms, live forms that save as they are typed, and refill forms that already know the returning visitor. Submissions land on the profile and in whatever you have connected.
Recent-activity notifications, live viewer counts, stock scarcity, countdowns and review badges — driven by your real numbers rather than a fixed string.
Ready-made designs for every action type, editable in the same visual editor, and able to take on your brand — colours, fonts and voice — in one step.
Spin-to-win wheels, scratch cards and reveal mechanics, wired to the same coupon and audience machinery as everything else.
Issue a code that belongs to one visitor — balance codes, AI-credit codes and percentage discounts — with the rules for who may receive one written once and enforced everywhere, including by the chat.
It learns from real behaviour, and it runs in three places: on the site, inside an email at the moment it is opened, and over an API for a front end we never see.
Widgets that pick from your catalog per visitor — on the homepage, the product page, the cart, the category page and the 404.
The same engine over articles rather than products, for publishers, media and anyone with a content library worth circulating.
Bought-together, viewed-together, also-read, recently viewed, best sellers, trending, category affinity, personal affinity and strongest-match scoring — chosen per widget or left to the engine.
What is gaining or losing momentum right now against its own 7-day and all-time baseline — as a widget, and as a report you can act on.
Products and articles arrive by feed, by crawl, by API or from the tracking code watching real pages. Stock, price and availability stay current without anyone re-uploading a CSV.
Ask for the recommendation set as JSON and render it yourself — in a native app, a composable front end, or a framework we will never see.
The image is computed when the email is opened, not when it is sent — so a week-old newsletter still shows what is in stock and what that reader wants today.
One answers your customers. The other builds the campaign for you, on brand, and stops for your approval before anything runs.
An assistant that answers from what you taught it and from your catalog, and refuses to invent a price or a promise. It knows who it is talking to before the first word.
The chat can open with the answer to a question the visitor never asked — built from their industry, their location, their account or their history. They never see the variable that powered it.
What the assistant may offer, and to whom. Each offer belongs to one of your audiences, and the assistant may only repeat what you wrote.
Describe the campaign in a sentence and it builds it — audience, action, design, goal — on brand, and stops for your approval before anything runs.
Write a targeting rule in English, edit an element by describing the change, have the platform read your site and propose the goals and placeholders worth having.
Personyze speaks MCP in both directions: your assistant can build and inspect campaigns, and Personyze can call the tools you connect to it.
Search over your own catalog and content that understands the question rather than matching the string.
A number nobody can defend is a number somebody will ask you to remove. Split any campaign, hold back a control, and read the result per audience rather than as one blended average.
Split any campaign, hold back a control, and read the lift with a confidence figure rather than a vibe.
The variant that wins overall usually loses for somebody. Personyze reports per audience and can serve a different winner to each.
Test several elements at once and read both the winning combination and the main effect of each group.
Define what counts — a page, a click, a form, a purchase with its value, an offline event pushed in later — and every campaign is measured against it.
Decide what share of traffic a test gets, ramp a winner, and pause anything that goes wrong without touching your site.
One profile, one set of audiences and one recommendation engine — rendered into an inbox, a notification, a hosted page or your own server response.
Personalized blocks, banners and recommendations inside emails you send from the ESP you already use — rendered at open time, from the same profile.
Browser notifications with the same targeting and the same recommendation engine, including product and article payloads.
The same campaign machinery over messaging, for the moments where a push notification is not enough.
Pages Personyze hosts at your own domain, personalized on the server and served from a CDN — so the first paint is already the right page.
Let a visitor book time with your team from a popup, a page or anywhere a campaign can reach — with the visitor profile attached to the booking, and hosts that cost no seat.
Ask for the decision over REST and render it yourself. No tag, no flicker, and it works where a browser never runs.
Personalized images rendered on request for places that will not run JavaScript — an email client, a marketplace listing, a partner site.
Campaign results and site traffic in one place, down to the individual visitor, and pushed on a schedule rather than waited for.
The overview screen is a preset, not a fixed page. Build your own from the same cards and keep the one that answers your question.
Your own traffic — visits, visitors, sources, engagement — campaign or no campaign, and down to the individual visitor rather than a bucket.
Per campaign, per action, per audience and per goal, with the control group kept beside the treated one.
Who is on the site right now, what they are doing, and which campaigns they are seeing as they see them.
What the engine learned from real behaviour, which widgets earn their space, and which products move together.
Have the numbers arrive rather than be fetched, and be told when one crosses a line you set.
Rules that run without you: pause or publish a campaign on its own, call a webhook, notify a channel, react to a number.
Personyze is a decision layer, so most of its surface area is getting data in and getting decisions back out — into the tools you already run.
One tag, installed directly or through a tag manager, with first-class handling for single-page applications and consent gates.
Catalog, cart and purchase events from the platform you already run, without a bespoke integration project.
Personalize pages you did not build, on the CMS you did not choose.
Take the audiences you already built somewhere else and act on them on the page, in the same session.
Two-way: target on the record, and write back what happened on the site.
Recommendations and personalized blocks inside the ESP you already send from.
Put a company name to an anonymous B2B session, from the providers who do it best.
Move an event out of Personyze into whatever runs your business, in the tool your team already automates in.
Everything the panel does, over an API — plus server-side SDKs for the decisions you want to make before a page exists.
Seats, caps, consent, retention and billing. Nobody puts these on a feature page, and everybody asks about them before signing.
Named logins with roles, an operator seat for whoever answers the chat, and meeting hosts who need no seat at all.
How often one visitor may see one thing, and how often they may see anything — set per action and per campaign, so a good idea does not become a nuisance.
One vocabulary across campaigns, actions, audiences and templates, so a large account stays findable.
Consent-aware tracking, an unsubscribe page, data retention you set, and an opt-out that actually stops the profile.
Chat, landing pages and the rest are priced as modules on top of the plan, so you pay for the ones you turn on.
Raise a ticket from inside the panel, on the screen you are stuck on, and follow it there.
Run many client accounts, clone a working setup between them, and put your own brand on the panel.
Nobody turns on sixty things. Most accounts start with one audience, one popup and one recommendation widget, prove the lift against a held-back control, and grow from there.