The short answer: a non-profit can automate relevant newsletters by publishing different content types to separate RSS feeds, recording supporter interests as Mailchimp Groups, and matching each feed to the appropriate Groups. One scheduled campaign can then assemble a different mix of content for donors, volunteers, campaigners and service users.
This guide is for teams that currently rebuild a general newsletter by hand or maintain several overlapping campaigns. It explains the content and audience decisions that need to be made before configuring the technology.
Why one general newsletter becomes difficult
Non-profits often communicate with several groups at once. A donor may want impact stories and appeals. A volunteer needs opportunities and practical updates. A campaign supporter wants policy news and actions. A service user may need local information rather than fundraising messages.
Sending everything to everyone is operationally simple, but it transfers the work to the reader. They must scan every email for the material that matters to them. Running a separate newsletter for every group solves the relevance problem but multiplies campaign production, testing and reporting.
The alternative is to maintain one audience and one automated campaign while changing the content included for each subscriber.
The feed, preference and campaign model
The workflow has three layers:
- RSS feeds provide the content. Each meaningful content category has a stable feed—for example Campaigns, Volunteering, Impact Stories and Service Updates.
- Mailchimp Groups record preferences. Subscribers select the subjects they want on a signup form or preference centre. Mailchimp describes Groups as contact-facing categories for interests and preferences in its Groups documentation.
- FlipRSS matches content to people. Each feed is mapped to the corresponding Group. The campaign includes the right combination when it is assembled for each subscriber.
This retains a single operational workflow without forcing every supporter to receive the same content.
Audit the content before building anything
List the content your organisation publishes and where it lives. For each source, record:
- the intended audience;
- the RSS feed URL;
- publishing frequency;
- whether it must appear in every newsletter;
- the maximum number of items per send;
- who owns the source when it breaks or changes.
Do not create a preference merely because a website category exists. A useful preference describes something a supporter recognises and genuinely wants to choose. Four dependable options are better than fifteen overlapping labels.
If you cannot locate a source URL, use our guide to finding the RSS feed for a website. Validate each source before connecting it to a campaign.
Design supporter preferences
Start with the questions supporters already ask. A practical first version might include:
| Preference | Typical content source | Likely audience |
|---|---|---|
| Campaign updates | Campaign or policy feed | Campaigners and advocates |
| Ways to help | Volunteering and events feeds | Volunteers |
| Impact stories | Case studies and programme news | Donors and partners |
| Service updates | Service or location feeds | Service users |
Allow subscribers to select more than one option. Someone can be both a donor and a volunteer, and the system should assemble one useful newsletter rather than sending two competing emails.
Link to the preference centre from welcome emails and every newsletter footer. Describe the expected content and frequency in plain language so the choice is meaningful.
Configure the automated campaign
Once the feeds and preferences are stable:
- Connect the relevant Mailchimp audience.
- Confirm the Group names exactly match the intended preferences.
- Add each RSS feed and assign its audience rule.
- Set item limits independently so a high-volume source does not dominate.
- Mark organisation-wide content for all subscribers where appropriate.
- Choose a template that tolerates missing images and variable excerpt lengths.
- Test with representative subscribers carrying different combinations of Groups.
- Schedule the campaign only after every test profile receives the expected mix.
The Mailchimp RSS-to-email integration guide covers the platform steps. The broader multi-feed planning guide explains duplicate handling, feed balance and sending rules.
Test the combinations, not just the template
A visually correct test email is not enough. Create test subscribers for the combinations that matter:
- donor only;
- volunteer only;
- donor and volunteer;
- all interests;
- no recorded preference.
Decide explicitly what the final case should receive. A short default digest may be appropriate, or the subscriber may need a prompt to update their preferences. Do not let missing data produce an empty or unpredictable email.
Measure whether the workflow is helping
Track operational and subscriber outcomes separately.
Operationally, record campaign preparation time, failed sends and feed issues. For the audience, compare engagement by preference group, monitor preference updates and watch unsubscribes over time. Avoid attributing every change to personalisation: publishing cadence, subject lines, list quality and the content itself also affect results.
Review the feeds and preference labels quarterly. Remove choices the organisation no longer publishes reliably and add new ones only when there is a durable content source behind them.
What FlipRSS contributes
FlipRSS connects multiple RSS sources to Mailchimp and applies Group-based visibility rules when the newsletter is assembled. Teams retain Mailchimp for audience management and delivery while FlipRSS handles feed aggregation and content matching.
For a broader overview of the model, visit RSS-to-email automation. You can also review FlipRSS pricing or start a 30-day free trial.