Contact Support
Back to All

3.11 Dec 11th, 2023

5 months ago by Jerica Krakowski

This release includes support for the new vs returning user data, releasing Attentive as a public beta integration, the ability to send a subscribe (subscription purchase) event server-side, and the ability to segment subscription vs one-time vs recurring orders in GA4.

Platform:

  • Chrome Extension - Now supports the use of Google's new GA4 Configuration Tag Type (the Google Tag).
  • Developer Beta: Custom Pixels Script - If you require upgrading to Shopify's Thank You Extensibility (which prevents you from using your Order Status Page and checkout.liquid code), you can request to trial our Custom Pixels script by submitting a Support Ticket.
    • This script will fire the dl_begin_checkout, dl_add_shipping_info, dl_add_payment_info, and the dl_purchase data layer events. It will also fire the dl_user_data event on your checkout & thank you pages. It will also load your GTM script + Elevar's DataLayer Listener script.
    • Event mapping:
      • dl_begin_checkout is mapped to the Web Pixel checkout_started event.
      • dl_add_shipping_info is mapped to the Web Pixel checkout_shipping_info_submitted event.
      • dl_add_payment_info is mapped to the Web Pixel payment_info_submitted event.
      • dl_purchase is mapped to the Web Pixel checkout_completed event.
    • This is limited to whatever Shopify's Web Pixel provides. E.g. Shopify's OrdersCount value in the Web Pixel only populates if the shopper is logged into their account.
    • Since Shopify's Web Pixel is hosted in an iframe, you won't be able to see these Data Layer events in chrome extensions like "datalayer checker" or at the top level of the Developer Console. In addition, GTM preview mode will also not load on the Thank You or Checkout pages when using this script (again due to the iframe limitation). Follow these steps if you need to see these events for troubleshooting.
  • Added street address to Session Enrichment so that future events can be enriched with more granular location data.
  • When in the onboarding state, after the Destinations Step is completed, the Pre-Built Tag library will be available as a navigation option.
  • When in the onboarding state, on the Remove Previous Tracking Step, you'll see a list of destinations you have live in your Elevar App & links with how to disable each one's native Shopify Integration.
  • Change to Extra Order Fees when no destinations are live:
    • For non-Starter plans, if there are no destinations live, no extra order fees will be charged. Just your monthly plan fee.
    • For Starter plans, if there are no destinations live, usage will be based on orders created in Shopify. Extra order fees will be capped at $50.

Destinations:

  • Attentive - Available as a Public Beta! [Set Up Today]
  • New vs Returning User Data: [Set Up Today]
    • Added a "customer_order_count" parameter to the dl_purchase event. This maps to Shopify's customer.orders_count value. Update your Order Status Page code for this value to start appearing. [How to update]
    • Once you've updated your Order Status Page code, the following will automatically occur:
      • GA4: Server-side purchase event will start passing the following user parameters: total_order_count & customer_type (either New or Returning).
      • Impact Radius: Server-side purchase event will automatically start passing the CustomerStatus parameter.
      • Awin: Server-side purchase event will automatically start passing the customeracquisition parameter.
      • Rakuten: Server-side purchase event will automatically start passing the custstatus parameter
      • Facebook: Server-side purchase event will automatically start passing the customertype parameter. _Pre-built web tags updated to pass customer_type. Must re-import your web tags for this to take affect.
      • Snapchat: Server-side purchase event will automatically start passing customerstatus parameter. _Pre-built web tags updated to pass customer_status. Must re-import your web tags for this to take affect.
      • Partnerize: Server-side purchase event will automatically start passing the customertype parameter.
      • ShareASale: Server-side purchase event will automatically start passing the newcustomer parameter.
  • Send a separate Subscription Purchase Event server-side:
    • Trigger: An order is created with an order tag of "Subscription First Order". If your order creation software adds this tag after the order is created, this feature will not work.
    • This feature is available to enable in the Events Step of the following destinations:
      • Facebook: Sends an event titled "Subscribe".
      • TikTok: Sends an event titled "Subscribe".
      • Snapchat: Sends an event titled "Subscribe".
      • GA4: Sends an event titled "first_subscription_purchase".
    • The Block Transaction Step will apply the same logic to the Subscription Purchase events as it does the Purchase events.
    • This feature uses the order-creation-based logic as the Purchase event meaning that you get the same 100% order accuracy!
  • You can now differentiate between first time subscription orders, one-time purchases, and recurring orders in GA4 using the new purchase_type event parameter! You can use this to create segments or add in filtering logic to your GA4 reports.
    • All GA4 server-side purchase events will automatically start passes an event parameter titled purchase_type.
    • Purchase_type will be set as "recurring" if the following is true: the order's sales channel is subscription_contract or the order is tagged with “Subscription Recurring Order” or “Prepaid”.
    • Purchase_type will be set as "first_subscription" if the following is true: the order is tagged with "Subscription First Order".
    • Purchase_type will be set as "one_time" if none of the above apply.
  • The following destinations will now be included in your Channel Accuracy Emails: Google Ads, Outbrain, Smartly, & Voluum.
  • Facebook:
    • The best practice for the Block Transaction Step now includes blocking the Facebook/Instagram Sales channel. All existing Facebook destinations were not modified
    • Updated client-side pre-built tags to pass the Country Code as a 2-letter code instead of the entire word. Reimport your Facebook pre-built tags for this changes to take affect!
    • Changed "Pixel ID" to be "Dataset ID"
  • Email/SMS destinations pass the Product URL instead of the Page URL for Add to Cart events:
    • Klaviyo - "URL", "url", & "Url" in the Add to Cart event now map to the Product URL.
    • Attentive - "productURL" in the Add to Cart event now maps to the Product URL.
    • Sendlane - "url" in the Add to Cart event now maps to the Product URL.
    • Iterable - Added "productURL" to the Add to Cart event, which maps to the Product URL.
  • Google Ads - Updated integration to use Google's API v15.
  • View Anonymized data in GA4 if the user opts out of consent.
    • How to turn this feature on: This is an optional setting that an Elevar employee must enable for you. It is not automatically enabled. Please submit a support ticket if you'd like this setting enabled.
    • How it works: If you've enabled Consent Mode in Elevar + you've requested us to enable this setting + your GA4 destination only requires ad_storage and/or analytics_storage for data to be sent, a user's server-side events will be sent to GA4 with Google's gcs parameters if they have opted out of either consent category (just like what Google does automatically with their GTM GA4 tags). If you require consent categories for more than just ad & analytic_storage + the shopper has not granted that category, the server-side data will not be sent.
  • Outbrain - Out of Beta! [Set up today]
  • Pinterest - Added support for Pinterest's click_id (the &epik= query parameter in the URL)