Contact Support
Changelog
Back to All

3.18 July 2nd, 2024

4 months ago by Jerica Krakowski

This release includes enhancements to subscription vs one-time order tracking, Reddit as a new public Beta, and TikTok/Postscript/Sendlane officially out of beta.

Sources:

  • Accurate Subscription vs One-Time Order Data:
    • Added selling_plan_name to products array for checkout funnel data layer events
    • If a received dl_purchase has a known selling_plan_name for at least 1 product, this will trigger Subscription Purchase Events.
    • If a received dl_purchase has a known selling_plan_name for at least 1 product, this will trigger the purchase_type custom dimension to be first_subscription.
    • Facebook/TikTok/Snapchat client-side Subscription Purchase tags will use the selling_plan_name in our data layer rather than from the Shopify object in their triggers. Please re-import your web tags for these changes to take affect.
    • To get this update: Make sure your Shopify Source is fully up to date & re-import your Web Tags for destinations that have Subscription Purchase enabled.
  • The Shopify Connection has been moved from the general "Connection Settings" to the "Store Connection" Step within your Shopify Source.
  • Even if you haven't updated your Shopify Source, you can see if Elevar's App Theme Embed is detected on your live theme when on My Tracking.
  • An email alert will be triggered if we no longer detect Elevar's App Theme Embed on your live theme.
    • For this email to trigger:
      • At least 1 destination must be live
      • App Theme Embed was previously detected 24 hours ago
      • App Theme Embed is now no longer detected on the live theme
  • For checkout datalayer events, removed the "_64x64" from the image URL so that Checkout Abandonment campaigns can pass full size images instead of thumbnail images.
  • Standardizing the Data Layer's Variant value when no variants exist
    • If a product does not have multiple variants, Shopify's theme returns "default title" as the variant name. However, Shopify's Cart API and Web Pixel return null or undefined in this scenario.
    • In order to standardize the data, when we receive a null from the Cart API or an undefined value from the Web Pixel, we'll instead pass "Default Title".
  • For headless merchants, we've implemented a fix for if the collection value wasn't passing the expected collection.
  • Enhancement to ensure the dl_user_data (used for pageview events) passes a currency code value.
    • It'll pull the currency code value from Shopify Web Pixel's cart object. If that is not available, it'll fallback to Shopify Web Pixel's shop object.
  • Non-Shopify Source Updates:
    • If you remove the Non-Shopify Subdomain Source, we will clear the Main Overarching Domain value to prevent race condition issues.
    • If you previously had the Non-Shopify Subdomain Source set up and removed it, the stored Main Overarching Domain has been cleared.
    • If you currently have the Non-Shopify Subdomain Source live, your tracking will continue to work status quo.

Destinations:

  • Reddit available as a public beta [How to Set Up]
  • Tiktok is no longer in beta! It is now an approved destination. [How to Set Up]
  • Sendlane is no longer in beta! It is now an approved destination. [How to Set Up]
  • Postscript is no longer in beta! It is now an approved destination. [How to Set Up]
  • Universal Analytics destinations will stop processing data.
    • As you may have been previously notified by Google: on July 1, 2024, Google Analytics 4 properties will have fully replaced Google Universal Analytics properties. From that date, Google will begin turning off all Universal Analytics services and Universal Analytics APIs, meaning Universal Analytics properties will be inaccessible through the Google Analytics front-end and APIs.
    • For any accounts where a Universal Analytics destination is live, this destination will no longer send events.
  • Customer Tag logic can no longer be selected when using the Allow Specific Transactions in order to prevent scenarios where all non-purchase events are being blocked due to no customer tags in event.
  • Enhancement for Facebook that increases the amount of browser-side events that pass a Facebook cookie value. This will improve performance & EMQ scores.
  • No longer able to activate the Google Ads Pageview 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 pageview event only in the Google Ads destination.
    • If you already had the pageview event enabled, your tracking will continue to work. However, we'll be reaching out to all users over time to migrate their pageview tracking client-side instead of server-side.
    • You can help us reduce Google Ads rate limit errors by disabling your Google Ads server pageview event and setting it up client-side instead.