ogdynamic

What the Mailchimp integration covers.

Merge tag mapping

Map each dynamic field to a Mailchimp merge tag on the canvas integrations tab. The canvas remembers the mapping for every campaign.

Per-contact personalization

Mailchimp substitutes each contact’s data when the campaign sends, so every recipient sees an image with their own name and details.

No send-time design work

Design the image once in ogdynamic. Personalization happens at render time — no per-segment exports or duplicated templates.

From connection to generated images.

Setup stays close to the tool you already use, while ogdynamic handles template rendering and delivery.

Follow the step-by-step Mailchimp guide
01

Mark layers as dynamic fields

In the ogdynamic canvas editor, toggle "allow override" on the layers that should personalize — a first-name headline, a city badge, a plan label.

02

Map fields to merge tags

On the canvas integrations tab, connect each dynamic field to a Mailchimp merge tag such as *|FNAME|* or *|CITY|*.

03

Send the campaign

Drop the image URL into your Mailchimp email. Each contact’s data is substituted and ogdynamic renders their image on open.

Built for real Mailchimp workflows.

Field mapping

  • Map any dynamic field to any merge tag
  • Use default text when a tag is empty
  • Audience fields and custom merge tags supported
  • Mapping is saved per canvas

Privacy conscious

  • Contact data is only used to render the image
  • Renders are served over HTTPS with immutable caching
  • No audience data is stored by ogdynamic

Fast at scale

  • Deterministic renders, cached per parameter set
  • Images load fast even for large campaigns
  • CDN-backed delivery

Mailchimp fields

Values that flow between Mailchimp and your ogdynamic templates.

*|FNAME|* First name*|LNAME|* Last name*|EMAIL|* Email address*|CITY|* City*|COMPANY|* Company*|PLAN|* Custom fieldAny audience merge tag

How personalization flows

The canvas exposes its dynamic fields on the integrations tab. Each field is mapped to a Mailchimp merge tag once, and the mapping travels with the canvas.

When Mailchimp sends the campaign, it substitutes each contact’s data into the image URL. ogdynamic renders the personalized image deterministically and serves it from cache.

Mailchimp integration questions.

Practical details for teams connecting ogdynamic to Mailchimp.

How do personalized images work in Mailchimp?

Design an image in ogdynamic with dynamic fields, map those fields to Mailchimp merge tags, and use the image URL in your campaign. Mailchimp substitutes each contact’s data into the URL, and ogdynamic renders a unique image per recipient.

Which Mailchimp fields can I use?

Any merge tag your audience exposes — built-in tags like *|FNAME|* and *|CITY|* as well as custom audience fields you have defined.

What happens when a field is empty for a contact?

Dynamic fields fall back to the default text configured on the layer, so the image still renders cleanly for contacts with missing data.

Does every recipient get a different image?

Yes. Each contact’s merge tag values become URL parameters, producing a deterministic, cached render unique to that recipient.