Understanding Mailchimp Tags in Alpine

This article explains how Mailchimp tags sync with Alpine, how the Do Not Sync tag works, and what to do if you encounter unexpected tag behavior.

The Mailchimp integration uses tags to help keep constituent information aligned between Alpine and Mailchimp.

Tags can originate in either system:

• Tags created in Mailchimp can sync to constituent profiles in Alpine.
• Email segments created in Alpine can be sent to Mailchimp as tags for campaign targeting.

Understanding how tags sync can help you manage audience segmentation and email communications more effectively.

Most Mailchimp tags sync between Alpine and Mailchimp during the nightly integration sync.

This means that tags added or updated today will typically appear in the connected platform the following day.

Exception: Email Segments

When you use the Create Email Segment feature in Alpine, the segment is pushed to Mailchimp much more quickly, typically within a few minutes.

The [Mailchimp] Subscription Status: Do Not Sync tag allows you to prevent a constituent from being synced to Mailchimp in future syncs.

What the Tag Does

When this tag is applied to a constituent:

• Alpine will stop sending that constituent to Mailchimp during future syncs.
• Future updates for that constituent will not be synced to Mailchimp.

What the Tag Does Not Do

Applying the Do Not Sync tag does not remove an existing contact from your Mailchimp audience.

If the constituent was already present in Mailchimp before the tag was added, they will remain in Mailchimp until they are removed directly within Mailchimp.

To fully prevent a constituent from receiving future Mailchimp campaigns:

1. Add the [Mailchimp] Subscription Status: Do Not Sync tag to the constituent's profile in Alpine.
2. Archive or delete the contact directly in Mailchimp.

Both steps are required if the contact already exists in your Mailchimp audience.

Note: The Do Not Sync tag is processed during the nightly sync cycle, so changes may not take effect immediately.

Over time, organizations may accumulate duplicate tags or legacy tags from previous email platforms.

Examples include:

• Duplicate Mailchimp tags
• Tags imported from a previous email provider
• Outdated segmentation tags that are no longer in use

If you need assistance cleaning up tags in bulk, contact your Customer Success Manager. 

Some organizations use household or group constituent records alongside individual constituent records.

A common best practice is to apply the Do Not Sync tag to household or group profiles while allowing individual constituent profiles to sync to Mailchimp.

This helps:

• Reduce duplicate emails
• Prevent multiple records from syncing for the same household
• Improve audience quality and reporting

If you're using household records, make sure the individuals you want to receive communications do not have the Do Not Sync tag applied.

If you notice that:

• A tag is not syncing
• A tag appears multiple times
• A constituent is syncing despite having a Do Not Sync tag
• A Mailchimp tag is missing from Alpine

Please contact your Customer Success Manager.

To help us investigate, include:

• The constituent's name
• The tag name
• When the tag was applied or updated
• Screenshots, if available

This information allows our team to review the sync history and identify the cause more quickly.

How often do Mailchimp tags sync?

Most tags sync during the nightly integration process.

Are email segments synced nightly?

No. Email segments created using Create Email Segment are typically pushed to Mailchimp within minutes.

Does the Do Not Sync tag unsubscribe someone from Mailchimp?

No. The tag prevents future syncing from Alpine but does not remove an existing Mailchimp contact.

Do I need to remove the contact from Mailchimp separately?

Yes. If the contact already exists in your Mailchimp audience, you must archive or delete the contact directly in Mailchimp.

Why am I seeing duplicate tags?

Duplicate tags can occur due to historical imports, legacy integrations, or audience changes. If you need help cleaning up duplicate tags, contact your Customer Success Manager.