How does consent/eAccept work with Mailchimp?

How does consent/eAccept work with Mailchimp?

This article explains how consent (eAccept) is handled when customers sign up for newsletters via the Mailchimp integration in Telaris.

The article covers when consent is recorded, where it is stored, and what limitations apply.

TABLE OF CONTENTS

• How does consent/eAccept work with Mailchimp?
• What is eAccept?
• When is consent recorded?
• When is consent not recorded?
• Where is consent stored?
• Main customer card vs contact person
• What happens if Mailchimp fails?
• Important limitations

What is eAccept?

eAccept is Telaris's registration of consent for electronic communication.

When a customer agrees to receive newsletters or other electronic communication, this is stored as consent on the customer card.

In connection with the Mailchimp integration, eAccept is used to document that the customer has signed up for newsletters at checkout.

When is consent recorded?

Consent is only recorded in one situation:

• A logged-in customer signs up for the newsletter at checkout

When the order is confirmed with the Subscribe to newsletter checkbox activated:

1. The email address is sent to Mailchimp

2. Mailchimp confirms that the contact was added

3. eAccept is recorded on the customer card in Telaris

The following consents are updated:

• General communication

• Email communication

When is consent not recorded?

In the following cases, eAccept is not recorded in Telaris:

• Newsletter sign-up via the footer of the webshop

• Guest customers (not logged in) signing up at checkout

Because footer sign-up does not require login, it cannot be linked to a customer card in Telaris, so eAccept is not recorded.

NOTE: Footer sign-up does not require login and is therefore not linked to a customer card in Telaris.

Where is consent stored?

Consent is stored on the main customer card in Telaris.

You can find it under the Newsletter section on the customer card.

This shows, among other things:

• Consent to general communication

• Consent to email communication

Main customer card vs contact person

It is important to understand the difference between the main customer card and contact persons.

The Mailchimp integration only records consent on the main customer card.

Contact persons have their own eAccept fields that are not automatically updated by Mailchimp sign-up.

What happens if Mailchimp fails?

The eAccept registration is dependent on a successful response from Mailchimp confirming that the contact was added or updated.

If the API call to Mailchimp fails:

• The contact is not added to Mailchimp

• eAccept is not updated in Telaris

This prevents the system from recording consent without the sign-up actually having been completed.

Important limitations

• eAccept is only recorded at checkout sign-up

• Footer sign-up does not update the customer card

• Guest customers do not get eAccept recorded

• Contact persons are not automatically updated

• There is no automatic sync between Mailchimp and eAccept status in Telaris

Mailchimp handles the actual subscription status, while Telaris only records consent at checkout.

Guide: Mailchimp integration – overview and what the module does
Guide: How newsletter sign-up works in the webshop footer and at checkout