Mailchimp

Trigger Mailchimp Customer Journeys from Evident events, with loyalty data kept current on every contact.

On this page

Set up in Settings → Integrations

Connect Mailchimp and Evident fires events into a Customer Journey rather than sending review request emails itself.

Connect

Settings → Integrations → Mailchimp → Connect, and authorise. Pick the audience Evident should write contacts to.

Create the Customer Journey

In Mailchimp: Automations → Customer Journeys → Create Journey. Name it “Review Request — Evident”.

Set the starting point to API — the Customer Journey API trigger. Evident calls that trigger when a request is due.

Add a Send Email action immediately after the trigger. Do not add a time delay — Evident already waited your configured delay, and another one stacks.

Merge fields

Evident keeps these up to date on each contact. Use them in a template as *|EVPOINTS|*.

Merge tagContents
EVPOINTSLoyalty points balance
EVTIERLoyalty tier name, e.g. GOLD
EVREVIEWSTotal approved reviews
EVRATINGAverage rating given
EVVBUYYes if a verified buyer
EVLASTREVDate of the most recent review

These make useful segments as well as personalisation — “verified buyers who have never reviewed” is a good audience, and EVVBUY plus EVREVIEWS gives it to you.

Add a reminder

After the first email, add a delay of 5–7 days and a second email, with a rule that skips contacts who have reviewed since entering the journey.

The events

evident_review_request · evident_review_submitted · evident_review_approved · evident_review_with_photo · evident_points_earned · evident_points_redeemed · evident_tier_upgrade · evident_referral_converted · evident_referral_reward · evident_birthday_soon

Notes

  • Contacts are upserted into the selected audience before an event fires.
  • Suppression and deliverability become Mailchimp’s once connected.
  • Mailchimp’s Customer Journey API trigger has to be created and published before Evident can call it — a journey left in draft receives nothing.
  • Disconnecting reverts to Evident sending directly.

Something missing or out of date? Email [email protected] — docs corrections go straight to the team that builds the feature.