This release includes the ability to send discount data to GA4. You can also send the email sign up event server-side to Meta. In addition, you can include filtering logic based upon the app_id of an order (e.g. to exclude all app orders regardless of the payment method used). Finally, we've added enhancements to our DataLayer Debugger tool for our Headless and Non-Shopify merchants.

Destinations

New Beta Releases:

• Mixpanel: Mixpanel is now available as a public beta! [How to Set Up]

New Destinations:

• Taboola: Taboola is no longer in beta! It is now an approved destination. [How to Set Up]
• Awin: Awin is no longer in beta! It is now an approved destination. [How to Set Up]

Google Analytics 4:

• Purchase Events: All purchase events now include a total_discount_amount event parameter, which includes order level, product level, and shipping discounts. This will allow merchants to easily see how much discounts were applied to the whole transaction. To use this data in GA4, you'll need to set up an associated custom dimension. [How to set up]
• Item Discount Amount: The "Item discount amount" in GA4 now includes all discounts (order level, product level), allowing merchants to calculate the final price paid for the product (item revenue - item discount).
• Tilde Symbol Handling: If a tilde symbol is included in an event (e.g., product name), it will now pass with correct formatting to GA4.

Facebook/Meta Destination:

• Email Sign-Up Event ("Lead"): Now able to send the email sign up event ("lead") server-side.
• Facebook Orders: Orders from the Facebook sales channel (channel code: 2329312) will be included in the NewCustomerPurchase and ReturningCustomerPurchase events, regardless as to the setup of the Filter Transaction Step. All other filters in the Filter Transaction step will still apply to these custom events.
  • This is because Meta already includes purchases that come from the Facebook Sales channel in the main "purchase" event, so we want to exclude these orders from the main purchase event to avoid duplicate transactions. However, Meta doesn't automatically include these orders in Custom Events, so we want to include these orders in the NewCustomerPurchase and ReturningCustomerPurchase events.
• CompleteRegistration Event: The client-side account sign-up event ("CompleteRegistration") can now be enabled or disabled in the Events Step.
• NewCustomerPurchase and ReturningCustomerPurchase Events: These events are included in the default best practice selection for the Events Step.

TikTok Destination:

• TikTok Orders: Orders from TikTok’s sales channel (channel code: tiktok) will be included in the NewCustomerPurchase and ReturningCustomerPurchase events, regardless of the Filter Transaction Step setup. All other filters will still apply to these custom events.
  • This is because TikTok already includes purchases that come from the TikTok Sales channel in the main "purchase" event, so we want to exclude these orders from the main purchase event to avoid duplicate transactions. But TikTok doesn't automatically include these orders in Custom Events, so we'll want to include these orders in the NewCustomerPurchase and ReturningCustomerPurchase events.
• NewCustomerPurchase and ReturningCustomerPurchase Events: These events are included in the default best practice selection for the Events Step.

Google Ads

• NewCustomerPurchase and ReturningCustomerPurchase events are included in the default best practice selection for the Events Step.

Filter Transaction Step:

• You can now filter by app_id. [Learn More]
  • Example use case: Merchant is using TapCart and offers ShopPay. As Elevar does not do app tracking for merchants, merchants wants to exclude TapCart in their GA4 destination. However, app purchasers that use ShopPay have an order source_name of "web", which is what all online store orders use. Now, merchants can add in an additional filter to exclude all orders where the associated app_id is TapCart's app_id.
• If you've selected to filter transactions, you must have at least 1 filter added.

Filter Transaction Step Updates:

• Filter by App ID: You can now filter transactions by app_id. [Learn More]
  • Example Use Case: Merchant is using TapCart and offers ShopPay. As Elevar does not do app tracking for merchants, merchants wants to exclude TapCart in their GA4 destination. However, app purchasers that use ShopPay have an order source_name of "web", which is what all online store orders use. Now, merchants can add in an additional filter to exclude all orders where the associated app_id is TapCart's app_id.
  • Note: At least one filter must be added when using the Filter Transaction Step.

Sources

Shopify Source:

• Configuration: Added instructions for configuring Customer Privacy settings. [Learn More]
• dl_purchase Event: Added a discount_amount parameter in the products array, which will populate with the total discount amount applied to each product.
• Referrer List Updates: Added payment.payone.com and secure.payplug.com to the ignore referrer list.
• DataLayer Debugger Tool: Enhanced tool function to alert for additional issues such as missing context pushes, incorrectly formatted data, duplicate events, and more. [Learn More]

Platform

Chrome Extension:

• Bug FixFixed an issue related to font file loading.

Reporting:

Real-Time Reporting and Channel Accuracy:

• Improvements: Enhancements to Real-Time Reporting and Channel Accuracy Alerts.