How can we help?

Poplar integration


Our integration with Poplar empowers you to leverage all of your customer data in Cordial to build highly relevant and personalized one-to-one direct mail to customers. From passing in unique codes tied to individual customers to pulling in relevant categories, you can utilize the most impactful data in your messaging campaign.

In addition, you can easily add direct mail to any new or existing email or SMS automation. Start sending automated direct mail from Cordial with an easy integration that you can launch in minutes—and with no development. 

Create a Poplar mail campaign

1. In order to integrate Poplar with Cordial, you first need to create a mail campaign in Poplar. 

2. Upload your creative content into Poplar and create the campaign.

3. Once your Poplar mail campaign is created, you'll receive a unique Campaign ID.

You need a Poplar Campaign ID in order to pass the desired recipient data from Cordial to Poplar.

Set up the Poplar integration

1. Navigate to the Message Automation dropdown and select Rest Automations.

2. Create a new message automation by clicking the New button.

3. Give the message automation a unique name based on use case, select any applicable tags, leave the Channels section set to "Rest," and select Continue.

4. You'll be brought to the automation settings, where you'll see a list of REST Parameters and REST Post Processing scripts.

5. Click the Edit button to the right of REST Parameters and enter the following settings:

Parameter Value
HTTP endpoint
HTTP request method POST
HTTP request header Authorization : Bearer <Test or Production API Token>
Content type application/json

We strongly recommend you use a test API key to start. Once your workflow is set up successfully and running in test mode, go back into the REST Parameters settings and swap it out for a production API key to begin mailing.

5. The Script section at the top is where you'll enter logic for the recipient data being passed to Poplar.

  • If your campaign has address enrichment enabled, only email and any other custom merge tag data needs to be passed.
  • If mailing to existing customer addresses, you'll pass in the full address.

Examples of each can be copy, pasted, and adjusted as needed.

Mailing address

"recipient": {
"full_name": "{$contact.first} {$contact.last}",
"address_1": "{$contact.geo_mailing.street_address}",
"address_2": "{$contact.geo_mailing.street_address2}",
"city": "{$}",
"state": "{$contact.geo_mailing.state}",
"postal_code": "{$contact.geo_mailing.postal_code}"
"campaign_id": "XXXXX-insert unique campaign ID-XXXXX",
"creative_id": "XXXXX-insert unique creative ID (optional)-XXXXX"

Address enrichment

"recipient": {
"email": "{$}"
"campaign_id": "XXXXX-insert unique campaign ID-XXXXX",
"creative_id": "XXXXX-insert unique creative ID (optional)-XXXXX"

6. Click the Preview button in the top right to see a preview of the request. Make sure all of the data maps properly. If everything looks correct, select Back in the top right and then Save the settings.

7. Once your settings have been saved, click the Send Test button in the top right to test the integration. If the connection is successful, you'll see a mailer appear under the campaign's History tab.

8. If the connection is successful, select Publish.

9. Select Event Triggered under Sending Methods to set the desired trigger conditions. Audience filters can also be added to refine your target audience.

10. Be sure to Save and then Enable the trigger to set it live. Recurring sending methods can also be enabled for use cases such as buyer anniversary, monthly customer birthday discounts, and other time-specific events.

This integration was built with daily automated workflows in mind and cannot support a data push exceeding 15,000-20,000 API calls in one batch due to API rate limiting. For large batched mailings, you'll want to export your audience segment 'from' and then mail with a one-time send. If you have any questions, reach out to Cordial Support for assistance.

Merge tags and variable Data

Coupon codes, loyalty status, and even browsed items are among many examples of variable data stored in Cordial that can be passed to Poplarand utilized in design with custom merge tags.

To pull variable data into your creative content, it must be uploaded to the platform as an HTML file.

1. When setting up your REST automation, you'll need to include merge tags and their dynamic values as an object in the Script section of your REST Parameters. Here's one example:


{foreach$browseditems as $item}



2. You'll know the request is successful and the merge tags are mapping accordingly if a test mailer appears in the campaign's History tab. Click into the mailer and scroll down to see the request details.

Reach out to Cordial Support for additional assistance.



Please sign in to leave a comment.