Currently, only the email address identifier is supported by the Emarsys Shopify plug-in for:

• Creating, updating and deleting contacts
• Triggering events
• Synchronising orders

No, if you have more than one Shopify store, you need to map each one to a separate Emarsys account.

To ensure that your Emarsys plug-in works as expected, follow the instructions in Emarsys plug-in for Shopify - Quality check of the plug-in.

No, the Emarsys Shopify plug-in does not support bundle products currently.

The "Multiple calls of go command" error message is not relevant to the Shopify extension snippet. However, please always make sure that only one Web Extend implementation is present.

The following can indicate that custom implementations are used in your Shopify shop:

• Multiple views or user identification is displayed in the Predict Inspector and
• Duplicate Web Extend events are shown on the Live Events page.
• In this case, we recommend that you remove the custom implementation from your shop because the plug-in sends the product catalog as described in Product catalog and Web Extend events and it will recognize this format automatically. However, the custom implementation needs to be changed according to the product catalog upload data.

After turning on Product upload on the UI, our service sets up the customer's Predict account so that the upload configuration will be hidden (catalog URL, scheduling). In this case, the service handles catalog submission by uploading the CSV catalogs to a given address, then by triggering the Emarsys Platform to process the catalog.

Also, the grouped_catalog option is enabled in the Predict configuration, so it can handle parent/child relations between product entities (i.e. parent products and their variants in Shopify).

In the case of parent products:

• the item field contains the ID/SKU preceded by the g/ prefix and
• the group_id field contains the ID/SKU in the product catalog.
• For example:
  • item: g/PRODUCT-SKU
  • group_id: PRODUCT-SKU

In the case of child products:

• the item field contains the ID/SKU and
• the group_id field contains the ID/SKU of the parent product in the product catalog.
• For example:
  • item: PRODUCT-SKU
  • group_id: PARENT-PRODUCT-SKU

The following output example shows you an example catalog that contains parent-child and single products:

Product in webshop (SKU)                                                     Lines in CSV

As a result of this, tracking events contain products in the following format:

• View event: g/PARENT-PRODUCT-SKU - As customers usually view parent products, view events are sent with the g/ prefix.
• Cart event: PRODUCT-SKU - Customers put configured products or variants into their cart, so cart events contain child product identifiers.
• Purchase event: PRODUCT-SKU - Customers purchase configured products or variants, so purchase events contain child product identifiers.

Web behavior tracking relies on the product catalog that has to be synchronized to Emarsys in a specific way. As the Emarsys Shopify plug-in synchronizes product data in the expected format and structure, we strongly recommend that you activate the plug-in's Web behavior tracking along with product data synchronization only.

If you activate Web behavior tracking without synchronizing the product data, then you need to integrate your product catalog by ensuring that its structure is appropriate. Please note that Emarsys cannot be held responsible for the consequences resulting from such cases.

Each catalog upload will replace the entire catalog in Predict, so if the customer previously uploaded the catalog from another source, then decides to use the connector "middleware", then as a result, the previous catalog will be overridden by the one coming from the plug-in.

In the following example, you can see how a sample order CSV file from Shopify looks like:

In the following example, you can see how a sample product catalog CSV file from Shopify looks like:

For more information on limitations related to field matching and data synchronization, see Field matching and data synchronization.

Order data does not contain taxes when it is synchronized to Smart Insight, Emarsys changed the sales data processing method on 10 March 2021, as a result, Emarsys synchronizes order data including all details (i.e. the price with and without tax and the delivery cost) and Smart Insight calculations use gross values. If it is required, you can set further purchase filters on the Smart Insight settings page.

To successfully reload your sales data, when using the Shopify plug-in, please contact Emarsys Support first.