When a visitor matches a Personyze campaign, their Mailchimp member record is created or updated in the audience you name — matched on email address.
This is an Automation-only destination. It calls the API from Personyze’s own servers with a key, so there is no on-page equivalent and it does not need that tool’s script on your page. Tick it on a Send Event to Analytics action.
What you need
| Field | Where to find it |
|---|---|
| API key | Mailchimp → Account → Extras → API keys |
| Audience ID | Audience → Settings → Audience name and defaults |
The API key must end in its data centre — like
…-us6. That suffix is how Mailchimp says which server your account lives on, and Personyze refuses a key without it rather than sending your data nowhere.Two rules worth knowing before you rely on it
An existing member’s subscribe status is never changed. Somebody who unsubscribed stays unsubscribed. A status is only set when Personyze creates the member.
The tag is applied only when the member is created. The event name becomes a Mailchimp tag on a member Personyze adds. For a member who already exists, their details and audience membership are updated but the tag is not added. If your automation has to fire for existing members too, trigger it on the audience rather than on the tag.
Troubleshooting
| Symptom | Almost always |
|---|---|
| Mailchimp rejects the key | It was pasted without its -us6 style suffix. |
| An automation does not fire for people you know are in the audience | They were already members, so the tag was not added. Trigger on the audience instead. |
| “the recipient has no email” | The matched visitor has no email on their Personyze profile. |