Skip to content

Commit 88ea1e6

Browse files
authored
Merge pull request #6621 from segmentio/tanjinhong72-patch-12
Add info that Mailchimp might reject misspelled email domains
2 parents 532ce15 + 5539f71 commit 88ea1e6

File tree

1 file changed

+7
-3
lines changed
  • src/connections/destinations/catalog/mailchimp

1 file changed

+7
-3
lines changed

src/connections/destinations/catalog/mailchimp/index.md

+7-3
Original file line numberDiff line numberDiff line change
@@ -130,11 +130,15 @@ Again, this will **NOT** work for new users. New users will always have their su
130130

131131
## Troubleshooting
132132

133-
### Why are my calls with trait arrays not showing up in Mailchimp?
133+
#### Why are my calls with trait arrays not showing up in Mailchimp?
134134
Mailchimp doesn't support arrays as traits values. This can cause calls to not show up.
135135

136-
### Why are there frequent 404 Bad Requests from Identify events without an error message?
137-
If you send concurrent requests for the same userId, MailChimp blocks the events because MailChimp restricts each API key to a maximum of 10 concurrent requests.
136+
#### Why am I seeing a `400 Bad Request` error?
137+
A **400 Bad Request** error can occur if the email address contains a misspelled domain name. For example, Mailchimp might reject`"[email protected]"` because "gmail" is misspelled.
138+
139+
#### Why am I seeing frequent `404 Bad Request` errors from Identify events with no error message?
140+
141+
Mailchimp blocks concurrent requests for the same `userId` if they exceed its rate limit. Each Mailchimp API key allows a maximum of 10 concurrent requests, so sending multiple requests for the same user at the same time may result in `404 Bad Request` errors without a detailed error message.
138142

139143
## Engage
140144

0 commit comments

Comments
 (0)