Sage CRM 2024 R2: Mailchimp - An Introduction (Part 7 of 7)

2 minute read time.

This is the final part of the revised series. In this article, I will examine the types of results and reports returned from Mailchimp into Sage CRM.

Mailchimp has its native information.

Within Sage CRM, a scheduled job retrieves the campaign results from the Mailchimp server. This job is scheduled to run every hour by default.

If you are very impatient and want to know almost minute by minute whether people are reading your emails, you can force a data fetch by clicking the refresh button.

There is also an additional full synchronisation that runs every 24 hours and fetches data such as opt-outs. Settings control all this behaviour.

The report within Sage CRM summarises the information displayed within the Mailchimp screens. However, within the Sage CRM screens, you can see all the critical details of a campaign. You can see how many people opened the email, who clicked links within the message, how many subscribers bounced, and which people chose to unsubscribe.

Each of the main totals is a hyperlink that can be followed to reveal the names of Sage CRM contacts who have interacted with the message you sent. For example, we can see those who opened the email.

From each result set for every campaign you create, you can create another Group. This group, in turn, can be saved and then sent to MailChimp to create a segment that targets subscribers who are most likely to take the action you desire.

Using the Sage CRM and Mailchimp integration, you can follow data from your Sage accounting system into CRM and on to when the data is used to create online campaigns, beautifully designed emails, and social media posts. You can then track those campaign results back into Sage CRM and ultimately back into the accounting system as a result of new orders.

The automated marketing emails from Sage CRM give you information about how your customers behave so you can analyse the effectiveness of each campaign.

The articles in the series are: