Go to the Destinations overview page and click the Add destination
button. Select Poplar and click Continue. You can then authenticate Hightouch to Poplar by entering a Poplar API key.
To access your API keys, navigate to Integrations > API in Poplar. If you want to create a new one, click Generate Access Token.
We recommend using a Production mode API key. If you use a Test mode API key, you can only use the Campaign Trigger sync type due to Poplar API limitations. To learn more about Poplar API keys, check out Poplar's docs.
Once you've set up your Poplar destination and have a model to pull
data from, you can set up your sync configuration to begin syncing data. Go to the Syncs overview
page and click the Add sync button to begin. Then, select the relevant model and
the Poplar destination you want to sync to.
Hightouch lets you use records from your models to trigger mail campaigns. This sync triggers a campaign for your Poplar customers based on the recipient's information.
Once configured, your Hightouch sync triggers your campaign once rows appear in your model. Hightouch triggers your campaign for every row in your model the first time you run the sync, whenever you do a full resync, and for every new row added to your query results in subsequent syncs.
You can optionally provide a Poplar creative ID for the campaign you want to trigger. If you don't enter a creative ID, Poplar uses the default creative. If you haven't sent a default creative, Poplar alternates between all active creatives.
This destination doesn't check for duplicates. Hightouch recommends that you set suppression control in Poplar to prevent duplicate campaign messages in case your model has duplicates.
Hightouch supports syncing rows from your model to customer records in your Poplar Do Not Mail list. Members of this list are automatically suppressed across all campaigns.
To date, our customers haven't experienced any errors while using this destination. If you run into any issues, please don't hesitate to . We're here to help.
Hightouch provides complete visibility into the API calls made during each of your sync runs. We recommend reading our article on debugging tips and tricks to learn more.