Mailchimp and MailAdx: The Complete Newsletter Ad Integration Guide

Mailchimp is the most widely used email platform among newsletter publishers who are new to programmatic advertising. Connecting Mailchimp to MailAdx takes under two hours and requires no backend development — just three configuration steps in your Mailchimp account and a code snippet in your email template. This guide walks through every step from account connection to your first live impression.

How the Mailchimp–MailAdx Integration Works

The integration works through a standard HTML image element inserted into your Mailchimp email template. When a subscriber opens your newsletter, their email client requests the image URL — which points to MailAdx's ad server. The ad server receives the request, selects the best available ad for that subscriber and that moment, and responds with the ad creative. The subscriber sees the ad; you earn revenue; the impression is logged.

The key technical element is the subscriber hash. To enable frequency capping and audience targeting, the ad URL includes a SHA-256 hash of the subscriber's email address. Mailchimp provides this through a merge tag (*|SHA256:EMAIL|*) that is automatically replaced with the correct hash value for each subscriber when the campaign sends.

This architecture means:

• No API integration between Mailchimp and MailAdx is required
• No subscriber data (email addresses, names, or other PII) is transmitted to MailAdx
• The integration works with any Mailchimp plan that allows custom HTML in templates
• Once the template is set up, no action is required on a per-campaign basis

For background on why open-time serving works this way and what it means for fill rates and CPMs, read the open-time ad serving guide first.

What You Need Before Starting

• A Mailchimp account (any paid plan, or Free plan with access to custom HTML templates)
• A newsletter with at least one existing campaign template
• A MailAdx publisher account (create one at mailadx.com/signup)
• Access to edit HTML in your Mailchimp template

The Mailchimp Free plan does allow custom HTML templates, so you do not need to be on a paid Mailchimp tier to use this integration. The custom HTML editor is available in the Mailchimp template builder under "Code your own."

Step 1: Create Your Publisher Account

Go to mailadx.com/signup and create a publisher account. During setup you'll be asked for your newsletter name, URL, and approximate subscriber count. Your account is approved and active immediately — there is no review delay.

Once inside the publisher portal, navigate to the "Placements" section. This is where you'll configure each ad slot in your newsletter.

Step 2: Create a Placement and Copy the Ad Tag

In the publisher portal under Placements, click "New Placement." You'll set:

Placement name: A descriptive internal name, e.g. "Header Banner" or "Mid-Content." This is only visible to you in reporting.

Placement key: A URL-safe identifier used in your ad tag, e.g. headeror mid_content. Keep it short and without spaces.

Ad sizes: Select the dimensions you'll use in your template. For a header placement in a 600px-wide newsletter, 600×90px and 600×100px are standard. See the ad unit best practices guidefor size recommendations by placement.

Floor CPM: The minimum CPM for paid impressions. Start with the recommended starting floor for your niche — detailed guidance in the floor CPM guide.

After saving the placement, the portal displays your ad tag — an HTML image element that looks similar to this:

<img
  src="https://ads.mailadx.com/serve
    ?pub=YOUR_PUBLISHER_ID
    &pk=header
    &eh=*|SHA256:EMAIL|*"
  width="600"
  height="90"
  alt=""
  style="display:block;border:0;"
/>

Copy this tag exactly — you'll use it in Step 4. Leave the *|SHA256:EMAIL|* merge tag exactly as shown; Mailchimp will replace it with the correct subscriber hash at send time.

Step 3: Add the SHA-256 Merge Field to Mailchimp

Mailchimp supports SHA-256 email hashing natively through its merge tag system. You do not need to install anything or enable a special feature — the *|SHA256:EMAIL|* merge tag is available in all Mailchimp accounts.

The merge tag is processed at send time: for each subscriber in your list, Mailchimp computes the SHA-256 hash of their email address and substitutes it into the URL. The raw email address is never transmitted to MailAdx — only the irreversible hash is included in the ad tag URL. This satisfies both GDPR and CCPA requirements for subscriber data handling.

No action is required in Mailchimp to enable this — the merge tag simply needs to appear in your template HTML exactly as written: *|SHA256:EMAIL|*.

Step 4: Insert the Ad Tag into Your Template

Open your Mailchimp campaign template in the HTML editor. Find the location where you want the ad to appear — immediately after your newsletter header for a header placement, or after your first content section for a mid-content placement.

Insert the ad tag HTML at that position. Wrap it in a table cell or div that matches your template's column structure. For a single-column 600px template, the tag itself fills the column width. An example with minimal wrapper:

<!-- MailAdx header placement -->
<tr>
  <td align="center" style="padding:12px 0;">
    <img
      src="https://ads.mailadx.com/serve
        ?pub=YOUR_PUBLISHER_ID
        &pk=header
        &eh=*|SHA256:EMAIL|*"
      width="600"
      height="90"
      alt=""
      style="display:block;border:0;max-width:100%;"
    />
  </td>
</tr>
<!-- End MailAdx header placement -->

HTML comments marking the start and end of the ad tag block are optional but make future template maintenance easier. Save the template.

Step 5: Test Your Integration

Before your first live send, verify the integration by sending a test email to yourself through Mailchimp's "Send a test email" function.

Open the test email and check:

The image loads: The ad placeholder or a live ad should appear in the position where you placed the tag. If the image is broken or missing, check that the ad tag URL is correctly formed and that the publisher ID matches your MailAdx account.

The SHA-256 hash is present in the URL: If Mailchimp is processing the merge tag, the URL in the loaded image should contain a hex string in the ehparameter rather than the literal text *|SHA256:EMAIL|*. View image in a new tab and check the URL to confirm.

Check the MailAdx dashboard: After opening the test email, log into the MailAdx reporting dashboard. You should see a test impression registered for your placement. This confirms end-to-end connectivity.

If the merge tag is not being processed (the URL still contains *|SHA256:EMAIL|*literally), check that you're using an HTML template rather than Mailchimp's drag-and-drop builder, which processes merge tags differently in some contexts.

Troubleshooting Common Issues

Image not appearing in the email

The most common cause is a malformed ad tag URL — typically a copy-paste issue that introduced extra whitespace or removed a required parameter. Re-copy the ad tag from the MailAdx publisher portal and replace the template tag entirely. Ensure no line breaks were introduced inside the src="" attribute.

SHA-256 merge tag not being replaced

Mailchimp processes merge tags differently in its code editor vs. its drag-and-drop builder. If you're using the drag-and-drop builder, add a "Code" block and paste the raw HTML tag into that block rather than into a standard content block. Alternatively, switch to an HTML template (Mailchimp → Templates → Code your own).

Impression registered but showing house ad

If you see your configured house ad rather than a paid ad, this means no paid demand met your floor price at the time of the test impression. This is normal — particularly at the start, when the platform hasn't yet built a history of your audience's attributes. Paid demand will increase as campaign targeting data accumulates. Lower your floor temporarily to see paid ads appear during testing, then raise it to your target floor for live sends.

No impression appearing in the dashboard

Check that Apple Mail Privacy Protection isn't causing the issue. If you're testing on an Apple Mail client with MPP enabled, the prefetch from Apple's servers may be logged differently than a genuine open. Test on a Gmail or non-Apple email client to verify end-to-end connectivity without MPP interference. See the MPP guide for more detail.

Adding Multiple Placements

Once your header placement is live and verified, adding a mid-content or footer placement follows the same process: create a new placement in the publisher portal with a different placement key (e.g. mid_content), copy the new ad tag, and insert it at the appropriate position in your template.

Each placement has its own floor price, category blocklist, and demand waterfall — configure them independently. The header and mid-content placements will show separate performance data in your reporting dashboard. See the complete guide to publisher ad unit best practicesfor how to configure multiple placements optimally.

Frequently Asked Questions

Does this integration require the Mailchimp API?

No. The integration works entirely through HTML template editing and Mailchimp's native merge tag system. No API credentials, Mailchimp app installs, or backend configuration is required.

Will this work with Mailchimp's plain-text emails?

No. Ad tags require HTML email rendering — the image tag needs to be loaded by an email client. Plain-text campaigns cannot serve ads. The integration is for HTML campaigns only.

Does the ad tag slow down email loading?

MailAdx's ad server returns a response in under 10ms for the vast majority of requests. This is imperceptible in the context of email rendering. If a subscriber's network is slow, the image may take longer to load, but this is true of any image in any email and is not specific to ad serving.

Can I use this with other ESPs besides Mailchimp?

Yes. The core integration approach — HTML image tag with SHA-256 email hash via merge tag — works with any ESP that supports custom HTML and merge variables. The syntax for the merge tag differs by platform (Klaviyo uses a different format; Beehiiv has its own variable syntax). See the ESP integration documentation for platform-specific instructions.

What happens if a subscriber has images disabled in their email client?

If images are blocked, the ad tag image doesn't load, no impression fires, and no revenue is earned for that open. This is identical to what happens with any image in any email with images disabled. The proportion of subscribers with images disabled is generally low (below 5% in most newsletter audiences) and declining as email clients default to showing images.