Skip to content

Commit 80c169d

Browse files
authored
Add info that missspelling email domain name might result in Bad Request error
Added the following in Troubleshooting section ----------------------------------------------- Why is 400 Bad Request error encountered? Misspelling of email domain name in the email address might result in 400 Bad Request error as Mailchimp might reject such email, for example, "[email protected]" because Gmail was misspelled.
1 parent 4ef6116 commit 80c169d

File tree

1 file changed

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

1 file changed

+3
-0
lines changed

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

Lines changed: 3 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -133,6 +133,9 @@ Again, this will **NOT** work for new users. New users will always have their su
133133
### 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 is 400 Bad Request error encountered?
137+
Misspelling of email domain name in the email address might result in 400 Bad Request error as Mailchimp might reject such email, for example, "[email protected]" because Gmail was misspelled.
138+
136139
## Engage
137140

138141
You can send computed traits and audiences generated using [Engage](/docs/engage/) to Mailchimp as a **user property**. To learn more about Engage, schedule a [demo](https://segment.com/demo/){:target="_blank"}.

0 commit comments

Comments
 (0)