This is what the header does on the homepage, a blog post, pricing or docs: cream from the first pixel, dark labels, the same panel. Nothing waits for a scroll.

Start Free Or book a demo

content

Two ways to run it

Send it from Personyze, or paste it into what you already send.

Same recipient profile, same recommendation engine, same reporting. The only question is who puts the email in the inbox.

Sent by Personyze

Build the campaign here and send it

Newsletters, lifecycle journeys and promotions, composed in the same visual editor that builds your on-site personalization.

Sent over Amazon SES with nothing to configure, or your own SMTP under your domain
Per-recipient send times learned from when each person actually opens
Frequency caps and fatigue suppression counted across every campaign, not inside one
Subject line, sender and content tests with the winner promoted mid-send
Audiences from your CRM, a file, a scheduled feed, on-site capture or the API

Best when you want the whole campaign, the audience and the reporting in one place.

Sent by your ESP

Paste one block into the template you have

Mailchimp, Klaviyo, HubSpot, SendGrid, Marketo, Salesforce — anything that sends HTML keeps sending it. Personyze fills the block.

One HTML block, pasted once into the template — not into every campaign
Swap the placeholder for your platform’s email tag and every future send is personalized
Blocks render at the moment of opening — live stock, current price, this morning’s behaviour
The same block works in order confirmations, newsletters and win-backs
Fallback content for recipients you do not know yet, so nothing arrives broken

Best when the sending stack stays exactly where it is and only the content gets smarter.

Both at once is normal

Most teams move newsletters and lifecycle campaigns to Personyze and leave transactional mail in the ESP with a block pasted in it. One recipient profile feeds both, so caps, segments and reporting still line up.

BarPlacements