3.15 Apr 1st, 2024

This release introduces a better way to send new vs returning user data server-side. It also includes the option to use a Custom Pixel script instead of the Order Status Page script if on Checkout + Thank You Extensibility, as well as Bing + Sendlane available as a public betas.

Sources:

  • Accurately send New vs Returning User data server-side:
    • Previously, the way to send new vs returning user data was to rely on Shopify's orders_count value in the liquid or Shopify's ordersCount value in the web pixel. These had limitations such as a 15 minute delay between the value including the most recent order and the web pixel value only populating if the shopper was logged in.
    • Now, when a shopper makes a new purchase, Elevar receives the order count data offline directly from Shopify and merges this into the server-side purchase event. This offline data always includes the latest purchase in the order count and does not require that the shopper be logged in.
    • To set this up on your account, you'll only need to grant your Elevar app Customer Permissions from Shopify. [How to do this]
    • Note: Works server-side only. Available only to merchants on our latest plan options.
  • In your Shopify Source, the "Configure Order Status Page" script has been updated to "Configure Checkout Script" with the option to use Shopify's Customer Events for tracking checkout/thank you pages if on both Checkout + Thank You Extensibility.
  • Custom Pixel:
    • Include an order_name parameter in the dl_purchase event that maps to the Order ID value. Why? Shopify currently doesn't pass an order name value in the web pixel checkout_completed event, but merchants may currently be using the order name value in their GTM web containers. This allows data to continue populating if the merchant switches to the Custom Pixel.
    • Include a discount_amount parameter in the dl_purchase event. This will equal the sum of the discount amounts from the line item discountAllocations in the web pixel checkout_completed event. This noted web pixel property doesn't include shipping discounts but appears to reflect all other discounts.

Destinations:

  • Bing available as a public beta [How to set up]
  • Sendlane available as a public beta [How to set up]
  • Reddit available as a private beta. Please let us know here if you'd like to be a beta tester. [Elevar's Fully Managed Server Only]
  • Mixpanel available as a private beta. Please let us know here if you'd like to be a beta tester. [Elevar's Fully Managed Server Only]
  • Pub/Sub is no longer in beta! It is now an approved destination. [How to set up]
  • Voluum is no longer in beta! It is now an approved destination. [How to set up]
  • GA4:
    • Include a GCD parameter in server-side hits (in support of Google's new Consent Mode v2)
    • If you want to enable GA4's User-provided data collection, you can now enable the "Activate user-provided data collection" option in your GA4 Settings step to include user parameters in your server-side hits. Note: once enabled, this setting cannot be disabled just like GA4's User-provided data collection setting. If you accidentally enabled this setting, delete your current GA4 destination and add a new one.
  • Block transactions based on Customer Tags. Example use cases:
    • Tag your internal team's Shopify customer profile with an "InternalTraffic" tag + block this customer tag in your destinations to prevent test orders from being sent.
    • Tag your list of customers who have submitted a "do not share/sell my data" request with "NoConsent" customer tag + block this customer tag in your destinations to prevent any order (online or POS) from these customers from being sent to your destinations.
  • Attentive: Changed "ProductURL" parameter to "ProductUrl" to avoid sent events being dropped by Attentive.
  • Added more pre-defined channels to the Block Transaction Step for: Refundid, TikTok, Faire, Reamaze, Narvar, Shopify Mobile, Indigo8, Shopify Collective, OpenBorder, Upfluence, Convictional, and Amazon by Codisto (includes amazon-us as well as the existing amazon channel code).
  • Google Ads: When creating conversion actions, if there is an error due to needing a unique name, we will try to create a new conversion action (adding ”-2”, “-3”, “-4” to the end of the name) up to three times before stopping.
  • Disabling/Re-enabling Consent Mode in the Shopify Source:
    • If Consent Mode is disabled in the Shopify Source, all destinations + Session Enrichment’s "consent mode steps" will go to the disabled state.
    • If Consent Mode is re-enabled in the Shopify Source, all destination’s (and Session Enrichment’s) previous consent mode steps will be reapplied.
  • Update to prevent invalidation of caches via the “unload” event

Platform:

  • Chrome Extension:
    • When creating a GA4 tag, the "GA4 ID Variable" will populate with any Constant variable in Google Tag Manager where the value starts with "G-"
    • Ability to select multiple events to import, download, or delete.
  • Real-Time Activity - Ability to expand/collapse all orders.
  • Add Team Member - Ability to select all websites when assigning access to new team members.