Skip to content
Personyze

How a Personalization Engine Actually Decides What Each Visitor Sees

The decision at request time, layer by layer: the data the engine knows (default dataset, AI-read interests, integrations, account data), the profile and the visit so far, targeting and discovered audiences, the recommendation model and the settings that steer it, per-audience testing, the render, and the loop that learns.

The Chat That Books the Meeting

When a visitor asks for a demo, the Personyze AI chat agent answers with real times and books the meeting in the thread – the same scheduler rules deciding host, length and availability.

Open the Chat With an Answer, Not a Question

The assistant can work out its opening line before the window opens — on the visitor’s own industry or city — and name a discount only to the audience entitled to hear it.

Personyze Is Now a Claude Connector: Build Personalization Campaigns by Asking

A Claude conversation building a Personyze welcome-offer popup that is saved to staging, with a publish button the user controls

Personyze is now available in the Claude connector directory. Connect it once, and you can build and review website personalization campaigns from inside a Claude conversation — no switching to the panel, no dev ticket, no template gallery. Here it is running end to end: Add Personyze to Claude → What this actually does You […]

Rules-Based vs AI Personalization: Which Decisions Belong to Which

Every personalization vendor now leads with AI, which makes the honest version of this comparison harder to find. So here it is: rules-based and AI-driven personalization are good at different things, and nearly every working programme runs both. The interesting question isn’t which wins — it’s which decisions belong to which. What each one actually […]