Contact Support
Changelog
Back to All

3.13 Jan 24th, 2024

10 months ago by Jerica Krakowski

This release includes enhancements to prevent Elevar's tracking from being blocked by ad blockers. It also includes updates to our Google Consent Mode v2 & GA4 integration, as well as Taboola available as a public beta.

Destinations:

  • Elevar's tracking cannot be blocked by an ad blocker: [Learn more]
    • Elevar's action-based purchase/checkout tracking has always been able to bypass adblockers. We're taking this a step further by proxying all of our code via Shopify's App Proxy, which makes it look like Elevar's code is part of the website.
    • To get this enhancement live on your website:
      • If you're not on App Theme Embed, then upgrade to App Theme Embed today.
      • If you are on App Theme Embed, replace the code on your Order Status Page Additional Scripts box or in your Custom Pixel with the new code available in your Shopify Source.
    • Works on Shopify hosted pages only.
    • Note: Ad blockers may adjust to prevent this in the future. If they do, we will continue to ideate on ways to ensure 100% data collection.
  • Taboola - Available as a Public Beta! [Set Up Today]
  • Making "View Anonymized data in GA4 if the user opts out of consent" compatible with Google Consent Mode v2.
    • In 3.12, we added the functionality where if Consent Mode was enabled in your Shopify Source but set to "No" if your GA4 destination, anonymized data would be sent.
    • Now with 3.13, when Consent Mode is enabled in your Shopify Source, your GA4 destination will show the Consent Step as always enabled & defaults to sending anonymized data to GA4 if a user opts out of tracking. This matches exactly Google Tag Manager's functionality where you cannot disable the Built-In consent checks for the GA4 tags. [Note: this is a cosmetic change only]
    • Any merchant who had Consent Mode enabled in their Shopify Source & their GA4 destination set to "No" for consent, will be defaulted to using the Built-In Consent Checks only.
    • Any merchant who had Consent Mode enabled in their Shopify Source & their GA4 destination set to "Yes" for consent, the selected consent categories will be enabled in the Additional column, which fully blocks data from being sent to GA4 if Additional Consent Checks are not approved by the shopper.
    • Why did we do this? If the server-side GA4 data didn't use Built-In Consent but client-side GA4 data does, this will distort GA4 metrics - as client-side data would be randomized & only available in modeled reports, but server-side wouldn't be.
  • GA4: Value Parameter
    • Updated the client-side GA4 tags to pass a "value" parameter to GA4 when relevant. This means, if you mark the event as a conversion, it will show revenue data associated with that event.
    • To get this update live, re-import & publish the GA4 Pre-Built Tags available in your GA4 destination.
  • Block Transaction Best Practice Update: Recommend blocking Matrixify's historical import orders.
    • Our best practice for blocking transactions will include blocking all orders created by Matrixify, which is used to import historical orders from your previous ecommerce platform into Shopify.
    • Existing merchant's destination settings have not be changed. If you'd like to ensure you're blocking Matrixify's historical import orders, update your Block Transaction Step to the best practice.
    • Newly added destinations will default to blocking Matrixify orders as the recommended best practice.
  • Voluum: Ability to send Custom Conversions
    • Added support for the following events: Pageview, Product View, Add to Cart, Begin Checkout, & Add Payment Info.
    • Note: Non-purchase events require an ET value to be input. The purchase event, if the ET value is left blank, will be sent without an ET parameter & will look like a generic "conversion" in Voluum.
  • Pixel Validation: Validation to prevent identical inputs when unqiue values are expected. E.g. the Pixel ID and Access Token should have unique values.
  • Updated Consent CMP Pre-Built Tags to support Google Consent Mode v2. Please reimport the OneTrust, Cookiebot, or Pandectes CMP tag from the Pre-Built Tag Library for these changes to take affect.

Platform:

  • Usage Billing Updates:
    • Non-Starter Plan:
      • If no destinations are live for the entire billing period, then no usage is calculated & merchant is just billed for their base plan fee.
    • Starter Plans:
      • If no destinations are live for the entire billing period, than usage will use all orders created in Shopify (capped at a max fee of $50).
      • If destinations are live for any portion of the billing period, then usage will count processed orders only.
  • Chrome Extension: GA4 Name Formatting
    • If an event parameter of "category" and/or "action" is included in the tag, the Chrome Extension will default the tag name to be: GA4 Event - {{Dynamic Event Name}} - {{Dynamic Category Value}} - {{Dynamic Action Value}}.
      • E.g. GA4 Event - behavior - navigation - navigation click
    • If both category & action are not included as event parameters, then the GA4 tag name will be: GA4 Event - {{Dynamic Event Name}}
      • E.g. GA4 Event - hero image click
    • This allows you to follow our best practice of bucketing your custom event data in GA4 to all be under the event name of "behavior" with a breakdown available for category & action.
  • Chrome Extension Bug Fixes
    • If you close the extension, you can reopen it without needing to refresh the page
    • Bug fix so user does not need to reinstall when the website previously logged in for no longer exists

Sources:

  • Added an "image" property into the "impressions" object of the dl_view_item_list event. This will automatically start sending an "ImageURL" and "imageUrl" parameter in Klaviyo Category View events if on App Theme Embed. This allows merchants to include product images in their Category Abandment Klaviyo emails.
  • Added a "compare_at_price" property into the "impressions" object of the dl_view_item_list event. This will allow merchants to include this value in their Category Abandment Klaviyo emails.
    • Note: Shopify does not support the ability to include a "compare_at_price" for the dl_add_to_cart events.
  • Console Warning when Consent Check Limit is Hit:
    • If Consent Mode is enabled in your Shopify Source, Elevar's code will wait to fire until consent values are received by a consent banner. If no consent values are received after a significant period of time, a warning will be logged into your Developer Console saying that the reason for the delay is due to no consent values being received.
  • Non-Shopify Subdomains: Apex Domain Validation
    • Automatically removes http://, https://, or www
    • Automatically removes subomain values (e.g. us.website.com will be turned into website.com)
    • If an invalid domain is entered (e.g. website.c ) then an "Invalid Domain" warning will be shown.