Reference Guides
Integrations
Versioning
Shopify
If you use Shopify, the easiest way to integrate with Poplar is via the Poplar Mail Shopify application.
Poplar for Shopify supports Abandoned Cart, New Order, New Customer, and Cancelled Order trigger events along with a number of highly specified filter options. If your use case requires another trigger event not listed, please check the Zapier section for an alternative approach.
Setup
2. Enter your store url if prompted. Once logged in, you'll be brought to the setup guide:
At the top, you can navigate between viewing your preconfigured triggers, creating new triggers, and the settings page.
3. Before creating a trigger, you'll first have to set up the Test and Production environments for them to operate under. Click Get API keys to be brought to the API page of your Poplar account. Copy and paste both keys under Settings and be sure to Save:
4. Abandoned Cart Delay (Optional)
The delay represents the amount of time to wait between a customer starting their checkout and when the checkout is considered "abandoned" upon which it would trigger the mailing. This delay is helpful if you have an Abandoned Cart email flow - set the delay to only mail if the cart is still abandoned after the email flow is complete.
5. Transactional Reporting (Recommended)
If you enable transactional reporting, order data will be shared with your Poplar account and used to generate in-platform reporting metrics. It will also auto-populate the Customers (Orders API) audience with both billing and shipping addresses which can then be selected for suppression from other campaigns. Please refer to the Orders API documentation for details on what information is being passed in the call.
Trigger Creation
Navigate to the Create Trigger page at the top. Before setting up your trigger, make sure the following tasks are completed in your Poplar account:
- Campaign is created and Active (not Paused).
- Creative artwork has been uploaded to the campaign.
Under the trigger section, you can set a name for the trigger as well as what type of event you would like to target. The event types available are: Abandoned Cart, New Order, New Customer, and Cancelled Order.
If you don't see a specific campaign in the dropdown make sure it is "Active" and has a Creative uploaded in Poplar. When A/B testing multiple creatives, make sure none of them are set to "Default" in your account.
Filters
After selecting your event type, a section for filters will pop-up. Here you can choose which events to filter out.
When selecting filter rules you have two main options. You can either choose to allow the event to mail if all filters are true, or allow the event to mail if any of the filters are true. If you choose to not configure any filters, every event will mail, provided there is enough customer information to do so.
Each individual filter can also be customized. By default, each trigger comes with accepts marketing is true as a filter, although this filter can be changed or even removed.
For a trigger to be valid, all filter fields must be filled out, or there must be no filters configured.
For filters such as line item skus and product title, the matches condition means that the specified sku or product title matches (case insensitive) a sku or product title within the list of all products for a specific order.
Some filters such as accepts marketing and verified email can only be applied once. However, filters like order count and product title can be included multiple times (e.g. Total Price > 10 and Total Price < 20).
Additionally, the greater than or less than conditions actually mean greater than or equal to and less than or equal to.
To trigger mailings only for new orders set the filter to Order count equals 1
Campaign & Creative
Selecting your campaign and creative is easy. The campaign options are already populated with the campaigns associated with your Poplar API keys. (Note it will hide any that are missing creative or paused)
After selecting your campaign you can also optionally select a creative. If you choose not to select a creative, we'll pick a random one from your campaign to use for each mailing.
After finishing the above steps, your trigger is ready to save!
Final Touches
If you wish to delay your mailing for a period of time after an event is triggered, you may do so here. One use case for the mailing delay is for an automated customer reminder. For example, if a customer buys an electric toothbrush, you could create a mailing with the New Order event and a 90 day delay reminding them to buy a brush-head replacement.
This Mailing Delay is independent from the abandoned cart delay set on the Poplar Shopify App settings page.
To finish configuring your trigger, choose a deployment key and whether the filter is enabled or disabled. We recommend enabling the trigger and leaving in Test Deployment and ensuring everything looks correct on your Poplar history page for a few days before switching to Production. Disabled triggers do not send requests to Poplar regardless of deployment environment. Once your trigger is all set, hit save trigger and you'll be redirected to the triggers page where you'll be able to see your newly configured trigger.
Trigger Page
From the main trigger page, you can view all of your mailing triggers. A green checkmark indicates an enabled trigger while a red X indicates a disabled one. You can edit each trigger by clicking on the edit button next to the name.
You can delete a trigger by clicking edit and scrolling down to the bottom of the creation page. There should be a delete trigger button next to the save button.
Filter Engine
Below is a brief description of each filter and their applicable events.
Event
Key
New Order
NO
Cancelled Order
CO
Abandoned Cart
AC
New Customer
NC
Condition
File Type
Description
true
booleanIf the value is true (eg. customer verified email)
false
booleanIf the value is false (eg. customer didn't opt into marketing)
≥
integerIf the value is greater than or equal to the specified threshold
≤
integerIf the value is less than or equal to the specified threshold
=
integerIf the value is equal to the specified threshold
matches
textIf the specified threshold is equal to (case insensitive) one or more item properties within an order (e.g. applicable to line item skus)
does not match
textIf the specified threshold does not equal (case insensitive) any item properties within an order. (e.g. applicable to line item skus)
Name
Events
Description
Total Price
NO, CO, AC
The total price of the order
Accepts Marketing
NO, CO, AC, NC
Whether the customer agreed to receive marketing
Order Count
NO, CO, AC
How many orders the customer has placed in the past
Line Item Skus
NO, CO, AC
Whether an order contains an item with the specified SKU (case insensitive)
Product Title
NO, CO, AC
Whether an order contains an item with the specified product title (case insensitive)
Variant Title
NO, CO, AC
Whether an order contains an item with the specified product title (case insensitive)
Total Spend
NO, CO, AC, NC
The total amount spent by the customer
Verified Email
NO, CO, AC, NC
Whether the customer has verified their email
Last modified 6mo ago