Contact Support
Back to All

3.17 May 29th, 2024

2 months ago by Jerica Krakowski

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.

Sources:

  • Shopify Source:
    • In the Configure Custom Pixel Step, there is now instructions to configure the Customer Privacy settings. [Learn More]
    • In the dl_purchase event, there will be a discount_amount parameter in the products array. It will populate with the total discount amount that is applied to that product.
    • Added payment.payone.com and secure.payplug.com to our ignore referrer list.
  • DataLayer Debugger Tool - Added functionality to alert of additional issues with custom built datalayers, such as missing context pushes, incorrectly formatted data, duplicate events & more. [Full Overview]

Destinations:

  • Mixpanel available as a public beta [How to set up]
  • Taboola is no longer in beta! It is now an approved destination. [How to set up]
  • Awin is no longer in beta! It is now an approved destination. [How to set up]
  • GA4 Destination:
    • All purchase events include an total_discount_amount event parameter. This includes all discounts associated with the order (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]
    • The existing "Item discount amount" in GA4 will start populating with all discounts associated to that item. Can include order level and product level discounts. This allows merchants to easily calculate the final price the shopper paid for the product (item revenue - item discount).
    • If a tilde symbol is included in an event (e.g. a Product Name), it will be passed with correct formatting to GA4.
  • 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.
  • Facebook/Meta Destination:
    • Ability to send the email sign up event ("lead") server-side.
    • 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.
      • Why? 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. But Meta doesn't automatically include these orders in Custom Events, so we'll want to include these orders in the NewCustomerPurchase and ReturningCustomerPurchase events.
    • The client-side account sign up event ("CompleteRegistration") can be enabled/disabled in the Events Step. Previously it was always enabled.
    • NewCustomerPurchase and ReturningCustomerPurchase events are included in the default best practice selection for the Events Step.
  • TikTok Destination:
    • Orders from the Tiktok sales channel (channel code: tiktok) 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.
      • Why? 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 are included in the default best practice selection for the Events Step.
  • Google Ads Destination: NewCustomerPurchase and ReturningCustomerPurchase events are included in the default best practice selection for the Events Step.

Chrome Extension:

  • Bug Fix related to font file

Reporting:

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