Contact Support
Changelog
Back to All

3.21 October 24th, 2024

about 2 months ago by Dana Boehm

This release includes enhancement for improving consent availability for web tags when consent mode is enabled.
Mixpanel is officially out of beta, and newly released Omnisend is available as a private beta (limited seats available)!

Data Layer

  • When consent mode is enabled additional logic has been added when events are pushed to the GTM dataLayer, we will now look for Google Consent Mode values before pushing these events to the GTM dataLayer. This improves performance of web tags that rely on the Google Consent Mode values for proper function. In the event no Google Consent Mode values can be found, the events will be pushed to the GTM dataLayer have the allowable time limit has been reached. This should improve the
  • Bug Fix: Resolved a race condition that would result in incorrect product list data for some stores using the non-Shopify subdomain attribution tracking script.

Destinations

  • Mixpanel is no longer in beta! It is now an approved destination. [How to Set Up ]
  • Omnisend is now in private beta! Please let us know here if you'd like to be a beta tester. [Elevar's Fully Managed Server Only]
  • CJ Affiliate: Server-side events are now passing the expected value for 'return' for the CustomerStatus value for returning purchasers
  • Impact Radius: Server-side purchase events are now populating ItemCategory
  • For destinations that require a web container to be downloaded the download will now vary from a .json or .zip in relation to if multiple GTM containers need to be updated. Multiple GTM containers are experienced when using the Shopify Markets functionality to send data to different pixel by market group.
  • GA4: Additional payment gateways will be removed from server-side events to maintain original attribution of the session. This added gateways include tabby.ai, tamara.co, checkout.sezzle.com, paytr.com
  • No longer able to activate the Google Ads add to cart event
    • Google's API Team originally shared that their API has no rate limits. Now, they have informed us that their API does have a variable rate limit. To ensure your Google Ads purchase tracking does not get affected by this rate limit, we'll no longer allow users to enable the add to cart event only in the Google Ads destination.
    • If you already had the add to cart event enabled, your tracking will continue to work. However, we'll be reaching out to all users over time to migrate their add to cart tracking client-side instead of server-side.
    • You can help us reduce Google Ads rate limit errors by disabling your Google Ads server add to cart event and setting it up client-side instead.

Platform

  • Updates have been made for an improved experience when canceling your plan with Elevar
  • Refer a friend has been added to the "Settings" navigation within the Elevar app.
  • Bug Fix: Resolved an endless spinner following the removal of a destination

Reporting

  • Bug Fix: Real-time reporting not loading for some users