In this guide you'll learn about the new features for our app previously known as "Google Tag Manager Suite" on the Shopify app store.
This 2.0 release guide is originally from December 2020. Some items may be outdated based on improvements from Elevar and/or Shopify integrations.
- Facebook Conversion API
- Native GA4 integration
- Sitewide Add to Cart & Buy Now Event Support
- Automated Data Layer Error Monitoring
- Product List Enhanced eCommerce Reports
- Checkout Behavior Funnel
- Variant Selections Pushing view_item Event
- Site Speed Improvements
- Ability To Enable/Disable Data Layer Events
- User Privacy Consent Integration
- Visualize What's Tagged On Your Website
NOTE: This is an optional upgrade to version 2.0. Our original GTM Suite Data Layer will continue to function and we'll continue to support both versions.
Want Elevar to handle the upgrade for you? Contact Support
We're excited to share all of the amazing improvements that help improve the accuracy of your data and stay ahead in the world of tracking.
Over the past 3 months we've been testing our Facebook Conversion API integration via Google Tag Manager. We've implemented on stores like Perfect Keto, Privacy Pop, PelaCase, and many more. We are now making this available as part of our basic plan package as well.
Here's a breakdown of how Elevar compares to native Shopify:
This integration will continue to evolve in 2021 as the integration requirements change.
We've already released pre-built containers for GA4 that work in our version 1.0 of the data layer.
Now we've enhanced our implementation to support more GA4 events and data schema structure. The following events are supported out of the box with version 2.0:
GA4 now runs in parallel with Universal Analytics in our base containers. We recommend continuing to run these two property types in parallel.
As many of you know our original version did not support add to cart events that might happen on your homepage, collection page, or cart page upsells. We were only able to capture add to cart events on product pages targeting the add to cart action.
But now we are able to capture add to cart events across the entire website without any customization required. How? We are now using the shopping cart as a signal for add to carts (and remove from carts). Here's an example:
- A user lands on your homepage from an ad (so their shopping cart is empty)
- The user then clicks add to cart on a featured product on the homepage so they now have 1 item in their shopping cart
- Once that user completes another action (viewing another page, etc), Elevar pushes an
add_to_cartevent to the dataLayer with the data of the product by comparing the difference/change in the user's cart.
This also fixes missing events from Buy Now buttons that native Shopify doesn't catch either.
You can still customize your add_to_cart event actions yourself within the codebase but now this solution automatically catches these events for you that previously went undetected.
Have you encountered broken tags or data layer variables in the past? But they went unnoticed for weeks until you finally realized it?
We released our data layer error monitoring in February 2020 and have implemented on our customers like Rothys, Thrive Causemetics, Snow Teeth Whitening to automate the process of QA'ing the data layer and associated marketing tags to ensure they are still accurate.
This is now enabled by default on all plans and available in your Elevar dashboard with our 2.0 plans.
You can learn more about how tag error monitoring works here.
A gap in our 1.0 version was the incomplete Product List reporting in the eCommerce reports. We've now fixed this as well so you get a complete picture of your product list (aka collection pages) performance.
When a user navigates to a product page via collection page and performs actions like add to cart, checkout, purchase we store the product list so you can analyze the full funnel journey of products within collection pages (note: product checkout metrics are only available on Shopify Plus).
As outlined in the GA4 overview above, we've broken out the checkout steps based on function of the checkout:
- begin_checkout (aka initiate checkout)
These are now codebase events that don't rely on page URLs, etc.
Another feature that we had in version 1.0 that worked on some stores w/o customization but not all was our variant change event.
Specifically sending another view_item (or productDetailView) event when a user changed a variant on a product page like color or size.
We've rebuilt this feature as well so now this works across almost all Shopify themes.
The JSON payload has been minimized to only include fields necessary for the dataLayer events. Previously, the entire collection would be converted to JSON resulting in thousands of characters of product data that was processed in JS that could result in degrading performance.
We've now added the option to allow you to toggle certain events on/off in the data layer.
So if you still wanted to disable the data layer for collection pages then you could do so like this:
The vast majority of stores now require some type of compliance - CCPA, GDPR, etc - to manage user privacy preferences. But this places a strain on a marketer's job to attribute performance of ad spend to make strategic decisions.
The problem with the way that most of the Consent Providers (like One Trust) are implemented is that they block the entire tracking library for services (e.g. Google) instead of limiting the data collected.
The ultimate goal for marketers is to comply with regulations without impacting your ability to attribute conversions. This is a great overview from Google and visually how they explain this:
This is essentially how Facebook's LDU implementation works as well if you are setting this flag for California visitors.
In our version 1.0 we released a way for brands to implement CCPA compliance for Facebook and Google Ads via GTM form tracking (see here).
But this was still manual.
Now we've integrated with consent providers to automatically populate a data layer variable with the user's preference selection:
- yes (they've provided consent)
- no (they've opted out)
- null value (no interaction)
This variable can then be used to populate consent flags like:
- Facebook LDU
- Google Consent Mode
Here are the providers we support:
- Shopify Customer Privacy
- One Trust (coming soon)
- Evidon (coming soon)
- Cookiebot (coming soon)
Have others that you'd like us to integrate with? Email us at [email protected]
If you haven't used our Chrome Extension yet to automate the process of tagging your website with Google Analytics custom events you should give it a try!
Now instead of guessing what part of your website is tagged with event tracking, Elevar shows you visually!
Once you connect GTM to your Elevar account we:
- Sync the events created in our GTM account with your Elevar account (& tags created in our Chrome Extension)
- Match your trigger rules to DOM elements on your website
- Match the tags to the triggers you've created
To visually show you what is tagged like this:
The result: you can now browse your website to view all of the tags created on your website to quickly match to the Google Analytics events.
Want to learn more about the plans available? Check them out here.
Updated 1 day ago