Mailchimp Campaign RSS Feed: Share Every Newsletter Issue

Short answer: Mailchimp publishes your sent campaigns in a public campaign archive, and that archive has an RSS feed. Each new campaign you send appears as a feed item with its subject line and a link to the web version. Connect that feed to an RSS auto-posting tool and every newsletter issue is shared to your social networks and channels automatically, without anyone copying links after each send.

Why share newsletter issues on social media at all

A newsletter is often the most carefully written piece of content a small business or creator produces all month. It goes to subscribers, gets opened by a share of them, and then disappears into inboxes. The web version of each campaign stays online, but few people ever see it.

Sharing each issue publicly does three useful things:

• It shows non-subscribers what they are missing. A social post linking to the latest issue is the most honest advert for the newsletter itself, and the web version usually carries a signup link.
• It gives subscribers a second chance. Someone who skipped the email may click the same story when it appears in their feed.
• It fills social channels with substantial content. For businesses that do not run a blog, the newsletter is often their only long-form content, and it deserves more than one audience.

The obstacle is routine. After a campaign is sent, someone has to open the archive, copy the link, write a short post and publish it on each network. That step is easy to forget, especially when the newsletter goes out on a schedule while the team is busy with other work. A feed-based setup removes it entirely.

What the Mailchimp campaign archive is

Every Mailchimp audience can have a public campaign archive: a simple web page that lists campaigns sent to that audience, newest first, with a link to the web version of each one. Many senders already link to it from their website as “Past issues” or “Newsletter archive”, and some add it to the footer of every email.

The archive is created from campaigns that were sent to the audience. By default regular campaigns appear there once they are sent, and Mailchimp lets you keep individual campaigns out of the public archive when they should not be public. Test sends and drafts never appear.

Alongside the web page, the archive offers an RSS feed. The feed URL is on the campaign-archive.com domain and contains identifiers for your account and audience, in a form similar to https://us1.campaign-archive.com/feed?u=...&id=.... The server prefix and the two identifiers are specific to your account, so copy the real address rather than building it by hand.

How to find your campaign archive feed

Mailchimp moves menu items between interface versions, so the exact path may differ slightly from what you see. The process is always the same in principle.

1. Open your campaign archive page. In Mailchimp, look for the option to view or share the campaign archive for your audience. You can also open the web version of any sent campaign and follow its link to past campaigns, if your template includes one.
2. Turn the archive address into the feed address. The archive page address looks like https://us1.campaign-archive.com/home/?u=...&id=.... Replace /home/ with /feed and keep the u și id values exactly as they are. Some archive pages also show an RSS link you can copy directly.
3. Check the feed in a browser or validator. Paste the address into a new tab. You should see XML with a <channel> and one <item> per campaign. If the browser offers a download instead, that is normal for feeds.
4. Confirm the audience. If you have several audiences, each has its own archive and its own feed. Make sure you copied the one for the newsletter you want to share.

If you cannot find the archive page, the Mailchimp help centre has an up-to-date article about email campaign archives that describes where the archive link currently lives. The two identifiers in the address are the same ones shown in your audience’s public settings.

What each feed item contains

Before you automate anything, look at what an item actually carries, because that is what your social posts will be built from.

• Title: usually the campaign’s subject line. A subject line written for the inbox, such as “You won’t believe this week” or one full of first-name merge tags, may read oddly as a public social post.
• Link: the web version of the campaign on the archive domain. This is what readers click.
• Description: a summary or part of the campaign content, depending on how the archive builds it. It can be long and contain HTML from the email template.
• Date: the send date, which the auto-poster uses to decide which items are new.
• Image: email campaigns often lack a clean featured image in the feed. Many auto-posting tools then fall back to the Open Graph image of the linked page, if there is one.

The practical consequence is that the subject line becomes your social headline. If you plan to share every issue, write subject lines that make sense without the email around them, and put the topic of the issue into the words.

Writing subject lines that work in the inbox and on social

Because the subject line travels into the feed title, it now has two jobs: getting the email opened and making sense as a public post. The two goals overlap more than people expect, but a few inbox habits do not survive the trip.

• Drop personalisation from shared issues. “Anna, here is your March update” becomes a confusing public post. Keep first-name tags in the preview text or the body instead.
• Name the topic. “Issue 42” or “This week’s news” tells a social follower nothing. “Issue 42: three ways to cut delivery costs” works in both places.
• Avoid pure curiosity bait. Vague teasers may lift opens slightly, but on social networks they look like clickbait and attract fewer clicks from people who do not know you yet.
• Keep it reasonably short. Long subject lines are truncated by most email clients anyway, and shorter titles leave room for the link preview and hashtags in social posts.
• Use a consistent prefix. Starting every public issue with the newsletter’s name, such as “Garden Notes:”, makes posts recognisable in feeds and makes keyword filtering trivial.

If you want different wording on social media than in the inbox, the cleaner route is to publish each issue on your own site with a separate headline and share that feed instead. For most senders, though, a well-written subject line is good enough for both.

Setting up automatic sharing, step by step

1. Decide where issues should go. Typical choices are a Facebook Page, LinkedIn for B2B newsletters, X, Threads, Bluesky or Mastodon for public audiences, and a Telegram or Discord channel for communities.
2. Add the archive feed as a source in your auto-posting tool and connect the target accounts.
3. Choose the message format. For newsletters, the title plus link usually works best. Long email descriptions rarely make good social text.
4. Set a start date. Decide whether older issues should be posted or only campaigns sent from now on. Posting a long backlog at once can flood your followers.
5. Add tracking parameters to links if you want to see in analytics how many readers the social posts bring to the web version and the signup form.
6. Send the next campaign and check. After the send, confirm that the item appears in the feed and then on each connected channel, and look at how the preview renders.

After that, the routine is simply to send newsletters. Every issue that reaches the public archive reaches your social channels too.

Privacy and content checks before you go public

The campaign archive is public, and a feed makes it more visible. That is the point, but it also means some campaigns should never be in it.

• Segmented or personal campaigns: a message to a small segment, such as existing customers with a renewal notice, may not be meant for the whole world. Keep such campaigns out of the archive.
• Merge tags: the web version replaces personal fields with defaults, but check how greetings and personalised blocks look to a stranger.
• Coupon codes: subscriber-only discounts become public discounts once the issue is shared. Decide whether that is acceptable.
• Transactional-style content: anything that looks like account information or order details has no place in a public archive.

A simple rule works for most senders: only campaigns you would happily post on your website should reach the archive, and therefore the feed.

Alternatives when the archive feed is not enough

The archive feed is the quickest route, but not always the best one.

• Publish issues on your own site. If you paste each newsletter into a blog post as well, the blog feed carries better images and descriptions, and the traffic lands on your domain instead of the archive domain. This is the approach many publishers prefer for search visibility.
• Use a dedicated “Newsletter” category. On WordPress and similar platforms, a category feed for newsletter posts keeps them separate from regular articles, so each can go to different channels.
• Keep the feed for internal use. Even if you do not share issues publicly, sending the archive feed to a team chat keeps staff informed about what customers just received.

Mailchimp also offers the reverse workflow: an RSS-to-email campaign that turns a blog feed into automatic newsletters. The two can work together. The blog feeds the newsletter, and the newsletter archive feeds your social channels, or the blog feeds both directly.

How PostRSS works with a Mailchimp archive feed

PostRSS accepts any RSS or Atom feed as a source, including a Mailchimp campaign archive feed, and checks it every 5 minutes on all plans, or every minute on Enterprise plans. When a new campaign appears in the archive, PostRSS publishes it to each target you connected, choosing from 66 networks such as Facebook Pages, LinkedIn, X, Telegram, Discord, Bluesky, Mastodon and team chats. You can choose which parts of the item form the post, add UTM parameters to every link, and set a start date so that older issues are either posted or skipped. Keyword filters can exclude campaigns whose titles contain words you do not want shared. Plan limits and the networks each plan includes are listed on the pricing page.

Related reading

• Beehiiv RSS Feed: How to Find It and Auto-Post New Newsletter Issues
• Substack RSS Feed: Auto-Post to Social Media
• RSS to Email: Turning Your Blog Feed into an Automatic Newsletter Digest
• How Podcasters and Newsletter Creators Automate Cross-Posting with RSS

The bottom line

If you send newsletters with Mailchimp, you already have a feed of every public issue. Find the RSS link on your campaign archive, check that the items look right, keep private campaigns out of the archive, and connect the feed to the channels where your audience spends time. From then on, each send becomes a social post automatically, and the effort you put into the newsletter reaches far more than the people who open it.

FAQ

Does Mailchimp have an RSS feed for sent campaigns?

Yes. The public campaign archive for each audience has an RSS feed that lists sent campaigns with their subject lines and web version links. You get its address by replacing /home/ with /feed in the archive page address.

Will private or segmented campaigns appear in the feed?

The feed mirrors the public archive, so anything visible there can appear in the feed. Keep campaigns meant for a small segment out of the archive before you automate sharing. Test sends and drafts do not appear.

Why does my auto-posted newsletter have no image?

Email campaigns often do not provide a clean featured image in the archive feed. Many tools then use the Open Graph image of the linked page, if one exists. Republishing issues on your own site with a featured image gives more control.

Is this the same as Mailchimp’s RSS-to-email feature?

No, it is the opposite direction. RSS-to-email turns a blog feed into newsletters, while the archive feed turns sent newsletters into feed items for other tools. You can use both at the same time.

Can I share only some newsletter issues?

Yes. Keep unwanted campaigns out of the public archive, or use keyword filters in your auto-posting tool to include or exclude issues by words in the title. A consistent word in the subject line of shareable issues makes filtering easy.