In this article, we are going to give you an overview of the main step in the integration process: a two-part step. Part 3a tells CCBChimp how we should pull data from CCB into MailChimp. Part 3b tells CCBChimp the reverse - pushing back data from MailChimp into CCB.

We do have a detailed overview of each part of Step 3 (a & b) but let’s revisit how we sync the applications.

Choosing how to sync:

You can choose to sync the required CCB groups to one single MailChimp audience (formerly known as list). Or sync the groups to multiple lists. It's very flexible. Each may impact your MailChimp cost. You can weigh the pros and cons. Our costs are flat rates per month. 

MailChimp treats all the audiences in your account separately, and your Monthly Plan billing is based on your total subscriber count across all your lists. It can be more costly to maintain multiple audiences, and you may run into compliance issues if bounced addresses are removed from one audience in your account but still exist in the subscribed section of another audience.

If you have duplicate subscribers across different audiences, consider combining your audiences into a master audience and use tags and/or groups to organize your subscribers. This can simplify your audience management and may reduce the cost of your monthly bill. However, if someone opts out from a specific email that you sent to a group, they will be opted out from the entire audience. 

NOTE: Using tags in CCBChimp depends on your plan. If you have the Pro plan or higher, you will be able to sync as either Groups or Tags at the campus level. If you are not on at least the Pro plan, syncing with tags at the campus level will not be available. To sync with tags, you will need to use the Group level.

To read more about using tags, open this article in a new tab.

Step 3a  ccbchimp.com/step3a  will walk you through how to setup the syncing from CCB to MailChimp. Setting up the syncing between MailChimp back to CCB is optional and see Step 3b here ccbchimp.com/step3b to learn more.

Did this answer your question?