This article explains how to integrate Emma and Shopify using Zapier, in order to replace an existing Shopify connection.

The Emma for Shopify integration was sunset in 2023 and all remaining connections will be removed in September 2024. Information about the sunset integration can be found here. This article provides instructions for Emma accounts who have an existing Emma for Shopify connection so that they can use Zapier, a third-party platform, to establish a new connection between Emma and Shopify.

In this article How to get a Zapier account How to set up the Emma side Users and API keys Contact fields Segments Destination group Helpful tips Zap templates How to authenticate Shopify and Emma in Zapier How to set up a zap Which data do you need from Shopify? Action step fields How to configure your zap data

How to get a Zapier account

In order to set up the Emma-Shopify connection through Zapier, you will need a Zapier account. Zapier is a third-party platform that allows you to connect Emma with over 6,000 different applications. While Zapier does have a free account, they classify Shopify as a "premium" app, which requires a Professional account, at minimum. Zapier is a third-party product with its own billing and support separate from Emma. Zapier has an FAQ on their pricing page, that will help you learn more about plans, billing, and how it works. Emma Support cannot answer questions about Zapier billing or pricing.

Ⓘ

Part of Zapier's billing model is based on "tasks". A task is an action your zap successfully completes. Each step of a zap will count as one task. Every time your zap runs, it will use that amount of tasks to complete. For instance, if you have three steps, and 10 customers are processed through that zap, that would be 30 tasks.

How to set up the Emma side

Users and API keys

We recommend that you create a new user whose API key pair you will use solely for this integration. As an alternative, you may also select an existing user who has not yet generated an API key pair, have them generate an API key pair, and then use that API key pair for this integration. This is important because if a user regenerates their API key pair, it will break the existing key pair and disconnect all integrations that used that key pair. Thus, to prevent disruptions, we recommend that you create a specific user, who will not be deleted, and whose API keys will only be used for this purpose. If you have an existing API key pair that you would like to use for this integration, you may do so, however, we do not recommend it.

1. Create a new user. We recommend using the Manager or Administrator role; if applicable, be sure to assign the user to all subaccounts that you want to connect to Shopify.
2. Have the new user log in to Emma.
3. The new user will need to follow the instructions in this article to generate an API key pair. They must record the public and private API keys somewhere safe, as the private API key will only be shown once.

Contact fields

The legacy Shopify integration should have already created five contact fields when you originally set it up. You should already have these, but if you don't, then you'll need to create them. The fields that you'll need are in the table below.

Field	Type
Total number of orders	Numeric
Total purchased (Money spent)	Numeric
Highest purchase ($)	Numeric
Average purchase ($)	Numeric
Last purchase date	Date

Segments

The legacy Shopify integration should have already created six segments when you originally set it up. You should already have these, but if you don't, then you'll need to create them.

• Average purchase is greater than $50
• Cumulative purchases are greater than $100
• Have more than one total order
• Purchased in last 30 days
• Purchased in last year
• Subscribed, but have not purchased

Destination group

The legacy Shopify integration should have already created a group when you originally set it up. For most accounts, this group was named Shopify customers, but the name may vary depending on your organization. If you do not already have a group for your Shopify contacts, then you'll need to create one.

Helpful tips

1. Before setting up the integration, be sure that you have the required fields, segments, and group in your Emma account.
2. Create test orders in Shopify and mark them as fulfilled. Also create test contacts in Emma. When you configure your zap in Zapier, it will look for the most recent Shopify orders, so this will allow you to test to confirm that the connection is working.
3. If you created a user who has access to all subaccounts that will be using the integration, then you can reuse the same user in Zapier for all accounts. You'll only need to change the subaccount ID in Zapier.

Zap templates

We've created seven pre-built zap templates to make it easy to set up your integration. We recommend that everyone use the first five templates, but the last two templates are helpful if you want to utilize product creation and tracking.

• Add new Shopify order to Emma contact or create new contact: When a new order is created in Shopify, add the order to the appropriate contact in Emma and create a new Emma contact, if necessary
• New Shopify order and create new contact in Emma: When a new customer is created in Shopify, create a contact in Emma
• Updated customer information in Shopify and update Emma contact: When a customer's information is updated in Shopify, update their information in Emma
• Updated Shopify order and update Emma contact: When an order is updated in Shopify, update the order for the appropriate contact in Emma and create a new Emma contact, if necessary
• Update Emma contact when Shopify order is cancelled: When an order is cancelled in Shopify, update the order for the appropriate contact in Emma
• Create product in Shopify and update Emma product: When a new product is created in Shopify, create or update the appropriate product in Emma
• Update Shopify product and create or update product in Emma: When a product is updated in Shopify, create or update the appropriate product in Emma

If desired, you can create your own zaps. However, we strongly recommend using the templates in order to ensure that you're using the correct Shopify triggers and actions in Emma.

Ⓘ	All newly created contacts in Emma will automatically have an active opt-in status. As a result, you'll need to be sure that you're adding customers to Emma based on their opt-in status in Shopify.

How to authenticate Shopify and Emma in Zapier

In order to create a zap, you'll need to authenticate your Shopify and Emma accounts in Zapier. You'll only need to do this step once, unless your Shopify domain or Emma user changes.

1. Open the zap editor to create a new zap.

   

2. Click on the Event in order to authenticate Shopify.

3. On the next screen, scroll down to the Account field and click on the Select button.

   

4. When prompted, enter the root domain of your Shopify store. For example, if your Shopify store's domain is mycoolstore.myshopify.com, then you'll enter "mycoolstore".
5. When prompted, enter your Shopify username and password.
6. Click on the Continue button.
7. On the next screen, click on the Test trigger button to test the Shopify connection.
8. Click on the Action in order to authenticate Emma.

9. On the next screen, scroll down to the Account field and click on the Select button.

   

10. When prompted, enter your public API key, your private API key, and the appropriate account or subaccount ID.

    

How to set up a zap

In Zapier, each Emma action set uses data from your Shopify store. When a Shopify event occurs, it sends data to Emma through the zap. In order for this to work, you must configure each Shopify event and Emma action in the zap workflow. Several of our suggested events have two action steps, so you'll need to configure the data for both actions. Each time you configure an action step, Zapier will test that step and provide a warning if it's not configured correctly and would fail to work. It will also show a green checkmark when the action step test is successful.

When testing your zap configurations, Zapier will use example data from your Shopify store. This is to help you accurately map the field data in your action steps using example data. Once you've mapped your data fields using the example Shopify data, your zap will be configured to automatically populate those fields each time that the event occurs.

Which data do you need from Shopify?

The data that you'll need from Shopify will vary based on the action steps you're using and which Shopify data you want to collect in Emma. Certain fields are required, but others may be populated if the customer has chosen to provide them, such as phone number. Other fields may be used for more advanced data tracking, including other contact field data, but this is entirely dependent on your marketing efforts and how you track your campaigns.

Action step fields

Ⓘ	Required fields are marked by a red asterisk and must be populated in order to proceed. Any fields without the red asterisk are optional.

 

Zapier differentiates between static and dynamic fields and allows you to determine whether you want a field to be static or dynamic. Static fields are for data that does not change. In a static field, you can enter a specific value that you always want that field to be. For example, if you have a zap that triggers when an order is fulfilled, you can set the Order status field to be a static field and enter Fulfilled as the value. This way, the data for this field is always consistent when it is sent to Emma and we can determine that data has only come from orders that have been fulfilled.

Dynamic fields are for data that may or will change. Most of the data that you'll send to Emma through Zapier will be dynamic. For example, Email address should always be a dynamic field, since it will be different for each customer who places an order.

Ⓘ	To change a field from static to dynamic, or vice versa, click on the three dots next to the field and select the desired option from the dropdown menu. Zapier typically makes all fields static by default, so you'll need to switch them to custom (dynamic).

 

Once you switch a field to custom / dynamic, you can click on the + icon to select a field from a dropdown menu. This allows you to select data that was generated by a previous step, such as member ID or order number. This information can't be predicted, so using the Custom option lets us add in that dynamic value.

How to configure your zap data

Once you've authenticated your Emma credentials, you'll see a Configure screen each time you click on an action step. This screen will have a list of available fields, which will vary based on the action step.

In the example below, we'll walk through how to configure the action steps for the Add new Shopify order to Emma contact zap. When an order is created in Shopify, this zap will add that contact to your Emma audience with the contact information that they've provided. Then, it will populate the contact's data in Emma with their Shopify purchase data.

1. The first action step in the zap is the Create member step. To begin configuring this step, simply click on it and a panel will open on the right. The only required field in this step is the Email field. All other fields are optional, but you can choose to map them to data from Shopify.

   

2. To configure a field, click on the three dots and select Custom from the dropdown menu.
3. Next, click on the corresponding plus icon. A dropdown menu will appear showing recent order data from Shopify.

4. Click on the field that you want to use and the data from Shopify will populate for that field. For example, if you click on the Email field in the action step, then you would select the Email field with the Shopify icon from the dropdown menu.

   

5. Repeat this process for each field that you want to map.

6. After you've mapped your fields, you'll be able to test the action step and see what fields are populated with example data. If the example data does not contain one of the mapped fields, that section of the test will show a message saying that no data could be mapped.

   

7. In the zap builder, click on the Add member order action step. Repeat the steps above to map the desired fields for this action step.
8. Once you've mapped all of your fields and tested each step, click on the Publish button.