Mailchimp + Make – SEEN Documentation

Prerequisites:

Minimum Essential Plan needed in order to use Customer Journey Builder in Mailchimp.

MAKE plan with enough monthly Ops to support the volume of contacts.

This guide will help you set up a trigger-based integration between Mailchimp and SEEN using webhooks in Customer Journey Builder to send data to SEEN via Make, and receive landing page URL and an email thumbnail URL back to Mailchimp as an event.

This example uses the profiles first name and last name as the personalisations, and their email address as the identifier.

This example expects that the Event is used to trigger a Customer Journey, in order to use the properties (landing page URL and the email thumbnail URL) in communication.

Send data to SEEN

A) Mailchimp Customer Journey Builder

Set up a new Customer Journey in Mailchimp, choose “Build from Scratch” and name your flow.

Choose the conditions in the “Choose A Starting Point” node to decide which profiles will receive a personalised film.

Add a “Webhook” journey point to your flow, and fill it out with following information:

Webhook name → Choose your name

URL Destination → your MAKE webhook URL (you can add this later when we set up the MAKE flow)

Click “Payload”

You can use the code below as a starting point

{
  "first_name": "*|FNAME|*",
  "last_name": "*|LNAME|*",
  "email": "*|EMAIL|*"
}

Remember to add the Contact Data needed for your film personalisation.

B.1) Custom MAKE Scenario

Create a new scenario, and add the “Webhook” module.

Click “ADD” to create a new webhook and choose “Custom webhook”. You will now receive the webhook URL to add to your Mailchimp Customer Journey webhook node.

You can now send a test payload from Mailchimp to MAKE to create your data structure.

After you get a “Successfully determined” message, add an HTTP module, and choose “Make an API Key Auth Request”, and fill it out with the following:

Credentials → Add

Under “Key” add “Token {token}” (you will receive your Token from SEEN)

API Key placement → “In the header”

API Key parameter name → Authorization

URL → https://api.seen.io/v1/campaigns/{campaign_slug}/receivers/

You will receive your {campaign_slug} from SEEN to call the correct endpoint.

Body type → Raw

Content type → JSON

Request content:

You can use the code below in this example (you might need to modify the values by dragging and dropping in the MAKE UI):

[
	{
		"first_name":"{{1.first_name}}",
		"last_name":"{{1.last_name}}",
		"email":"{{1.email}}",
		"customer_id":"{{1.email}}"
	}
]

If your film contains other personalisations, refer to our documentation for the payload structure.

You can now click “Run once” and send a new contact from Mailchimp to test your integration.

If everything worked, you can now activate your Customer Journey.

B.2) Make & Mailchimp native integration

You can also use Make’s native Mailchimp integration (App) to create triggers.

More information on Make’s documentation and Mailchimp’s documentation.

After the trigger has been determined, you can follow the “B.1 Custom Make Scenario” guide from Step 4 onwards.

Send data to Mailchimp

Share the following information with SEEN in a safe manner:

Your API key

Event endpoint

Which subscriber ID you wish to use (Email address in this example. Remember that you need to include the ID you wish to use in your payload).

The name you wish to use for the event (”SEEN” in this example)

Which fields you would like to be returned with the event (”Landing page URL” and “Email thumbnail URL” in this example).

After you have received a confirmation from SEEN that these have been applied, you can now test the full flow.