Personalized email at every open.

Most email tools personalize at send time — the moment the email is queued, content is locked in. Personyze personalizes at open time. When the recipient opens the email, the embedded image request fires to Personyze, and we render fresh content based on the latest data: current inventory, today’s price, the recipient’s most recent behavior, even local weather.

The same template can produce dozens of different rendered emails depending on who opens it and when.

Personyze open-time blocks work with any ESP that accepts HTML emails or merge tags. That includes Mailchimp, Klaviyo, HubSpot, SendGrid, Iterable, Marketo, Salesforce Marketing Cloud, ActiveCampaign, MailerLite, Constant Contact, Brevo, Omnisend, Drip, ConvertKit, AWeber, Customer.io, Braze, and many more.

You keep your existing send infrastructure — Personyze adds the open-time personalization layer on top.

No. The whole flow is a wizard. You connect a product feed or content source, design the recommendation widget visually, and Personyze generates the HTML snippet. You paste it into your email template once — replacing the placeholder with your ESP’s email merge tag (*|EMAIL|* in Mailchimp, {{ email }} in Klaviyo, etc.).

After that, every send is automatic. Same snippet works across order confirmations, newsletters, win-back campaigns — everything.

The HTML snippet contains your ESP’s email merge tag in the URL. When the email is sent, the ESP substitutes the actual recipient’s email address into that URL.

When the recipient opens the email, the image request hits Personyze with that email. We look up that user’s profile (purchase history, browsing behavior, segments, location, etc.) and render the appropriate content in real time.

You define a fallback when you build the widget. Personyze renders default content for unknown recipients — typically your top sellers, trending products, or featured content based on segment.

Recipients always see something relevant, never a broken email.

We’ve tested across all major clients (Outlook desktop and web, Gmail web and mobile, Apple Mail macOS and iOS, Yahoo, AOL, Samsung Mail) using Litmus and Email on Acid.

Personalized content degrades gracefully: if a recipient’s mail client blocks images (rare — about 3% of opens), they see your fallback content instead of a broken email.

From a fresh account, most teams have their first open-time block live in under 30 minutes: connect a product feed, design a recommendation widget in the wizard, paste the snippet into one email template, send.

The same snippet works across every send forever — no per-campaign setup. Most teams add new use cases (cart recovery, win-back, weekly newsletter) in 5–10 minutes each after the first one.

No. Personyze’s rendering infrastructure is global CDN-backed with median response under 200ms. The image loads asynchronously alongside other email content — recipients don’t notice a delay.

We monitor render latency and serve fallback content instantly if a render takes longer than threshold, so your emails always look complete even under failure scenarios.