Mailchimp Developers Release Notes

MARKETING

WHAT

We’ve launched new Audiences endpoints (BETA) as an alternative to our List Members endpoints. These allow for contacts to be added with just an SMS number. These endpoints are still in BETA but includes the following capabilities: create, update, read, forget and archive a contact without reliance on an email value.

The Audiences Endpoints (BETA) are available for evaluation or testing purposes only, may contain bugs or errors, and may not be as reliable as other Mailchimp features. Intuit may modify or discontinue this feature at any time without notice. By accessing the endpoints you agree to the Audiences Endpoints (BETA) Terms of Use. Consent must be accurately mapped to the supported marketing consent values. Unsupported values, including opt-outs, must be updated manually. See the Audiences (BETA) developer document for terms and additional details.

WHY

Previously, the creation of a contact via our API relied on the presence of an email. We’re launching this new endpoint to allow for SMS customers to bring over their full contact list, including contacts with no email.

MARKETING

WHAT

We've started writing over the campaign_id or outreach_id values on Orders to align with our new attribution model and user-configured settings. If your integration is sending campaign_id or outreach_id with Add Order or Update Order API calls, we recommend deprecating that logic.

WHY

We’re rolling out Mailchimp's native attribution model across all e-commerce integrations. This new model gives you more complete insights into how marketing campaigns contribute to customer purchases. It also improves marketing performance reporting for all Mailchimp customers using e-commerce integrations. Additionally, this reduces the need for complex custom logic for attributing orders to specific marketing messages.

TRANSACTIONAL

WHAT

We've published an updated package for the PHP client library that is compatible with PHP 8.2.

We've also published an updated package for the Node.js client library that uses the latest version of Axios to address a security vulnerability.

WHY

Older versions of the PHP client library caused errors when used with PHP 8.2.

A vulnerability was found in versions 0.8.1 through 1.5.1 of Axios, which unintentionally exposed the XSRF-TOKEN that was stored in cookies by including it in the X-XSRF-TOKEN HTTP header for all requests to any host. This allowed malicious actors possible access to sensitive data. To address this issue, we have updated the Node.js client library to use the latest version of Axios.

TRANSACTIONAL

WHAT

Beginning on March 15, 2024, we'll be enforcing new sending domain authentication requirements that you'll need to act on.

WHY

Google and Yahoo recently announced new sending requirements that will go into effect soon. To comply with these changes, Mailchimp Transactional users will have to update their DKIM records and enact a DMARC policy on any sending domain that might be used.

If you fail to update your domain’s authentication, we’ll use a mandrillapp.com subdomain as the sending domain for your email address, but replies from recipients will still go to your email address. This change will apply to any email sent through Mandrill that is currently authenticated but doesn't meet our new authentication requirements after March 15.

Here's how you can get started:

DKIM

• Create two CNAME records: one with the name mte1._domainkey.yourdomain.com with the value dkim1.mandrillapp.com, and another with the name mte2._domainkey.yourdomain.com and the value dkim2.mandrillapp.com

DMARC

• Create and save a TXT record in your DNS with a name of _dmarc.yourdomain.com and a value of v=DMARC1; p=none

Replace yourdomain.com with the domain you're setting up. Some domain hosts automatically add yourdomain.com after the initial value—contact your domain provider for any specifics.

We’ve updated the Mailchimp Transactional app and documentation to include these instructions, and to give you the ability to test these records on your Sending Domains page.

TRANSACTIONAL

WHAT

We’ve been updating our API responses recently to provide a more semantic response for the requests you make. With this release, we’re changing the way our API responds if you provide an invalid template name when requesting template information or if you try to send a message using a template that doesn’t exist. Once this change goes live, we’ll respond with an HTTP 404 Not Found.

If you’re specifically targeting HTTP response codes other than 200, you may need to update your code. We’re releasing this change incrementally over the next few weeks.

WHY

Previously, we responded with an HTTP 500 Server Error when you provided an invalid template name or slug. We’re updating this to bring our response in line with proper semantics and allow more efficient status monitoring.