Overview

Follow this guide to learn how to get the most value with Elevar.

Elevar is a data pipeline, not a reporting dashboard. That distinction matters. Every major paid media platform, Meta, Google, TikTok, Pinterest, and more, optimizes based on the conversion signals you send them. If those signals are incomplete, duplicated, or missing, the algorithms train on bad data, causing ROAS, CPC, and CPM to suffer across every channel.

Elevar is purpose-built to improve both the quantity and quality of data sent to every marketing destination, recovering data lost to iOS restrictions, accurately deduplicating events, and enriching every signal with attribution data before it reaches the platform. More accurate data in means better performance out.

How Elevar Works:

Elevar manages two tracking layers as a unified system:

• Client-side tracking: Elevar offers its own native client-side tracking, making it faster to connect destinations without needing to update tags in GTM. GTM is also supported for teams that prefer it.
• Server-side tracking via Elevar's infrastructure: Sends conversion data directly from the server to your marketing destinations, bypassing ad blockers, iOS restrictions, and browser limitations

The server-side layer is the priority for signal quality. Elevar listens to Shopify's order creation webhook, the most reliable source of truth for what actually happened, and enriches every purchase event with attribution data (fbclid, gclid, UTMs, session data) before sending it to destinations like Meta, Google, Klaviyo, and more.

Session Enrichment:

Elevar's Session Enrichment uses a 1-year server-set cookie to identify returning users, unaffected by the 7-day expiry that limits browser-set cookies. This means:

• Customers returning weeks or months later can still be identified
• Events like Viewed Product, Added to Cart, and Checkout Started are captured and enriched with session data
• Your abandonment flows stay active for a longer window, recovering more revenue

Data Accuracy You Can Verify:

Elevar's Channel Accuracy Report monitors order volumes by comparing events sent to each destination against Shopify's order creation webhook. If the numbers don't match, you know immediately. Elevar backs this with a 99% channel accuracy guarantee, and provides a detailed server event log showing exactly how many events were sent or failed, with error reporting for every destination.

Meta / Facebook

Once Meta is connected server-side via Elevar and client-side via GTM, the goal is simple — more accurate data flowing to Meta means better ad optimization, lower costs, and higher ROAS.

How to Measure Data Accuracy:

After running Elevar's tracking for at least 7 days (ideally 1 month), run a before/after report in Meta Ads Reporting to see the dollar impact:

• Go to Ads Reporting in Ads Manager and Create a Report.
• Title it something like "[Brand]: Pre vs Post Server-Side Tracking", select your Ad Account, then Create
• Choose Pivot Table layout
• Set your date range to start the day after you switched to Elevar — find this date in your History settings in Elevar
• Enable the Compare setting to show the prior period side-by-side
  • Focus on: ROAS, CPC, Amount Spent, Cost per Result, and CPM. Look for reductions in CPC, CPA, and CPM, and/or increases in ROAS

🚧

Note: For the most accurate results

This analysis works best outside of seasonal peaks or promotional periods. To get a true apples-to-apples comparison, the only variable that should change is Elevar — keep your creative, targeting, and spend consistent across both periods. Any changes to these during the test will affect the results.

📘

Learn More EMQ scores:

Event Match Quality (EMQ) is a secondary signal — strong scores (6–7 for pre-checkout events, 8–9 for checkout and purchase) indicate that Meta is accurately matching your events to real users, which supports better performance. But what matters most is the impact on your ROAS and CPA in Ads Manager.

🚧

Important: Data Sharing

Meta can only receive one source of server-side data. If you install Elevar, you must turn off data sharing in the Facebook app settings in your Shopify store. If both are active at the same time, Meta will receive two sets of server-side data, causing duplicated events that will skew your reporting and artificially inflate performance metrics.

Klaviyo (Email & SMS)

Connecting Klaviyo to Elevar is just the first step, on its own, it adds no value. Once connected, Elevar sends enriched server-side event data to Klaviyo, but you must then go into Klaviyo and configure your abandonment flows to actually use that data. Without this step, the additional events Elevar sends will go to waste.

Once Elevar is connected, follow these three steps to configure your flows:

• Clone each of your Browse, Cart, and Checkout Abandonment flows and rename them so they're easy to identify (e.g., Cart Abandonment – Elevar). This keeps your original flows intact while you set up the boosted versions.
• Change the trigger on each cloned flow to the Elevar equivalent event: Viewed Product - Elevar SS, Added to Cart - Elevar SS, or Checkout Started - Elevar SS
• Add a profile filter on each flow to prevent customers from receiving duplicate emails from both the original and Elevar-powered flows:
  • Browse Abandonment – Elevar: Viewed Product 0 times in the last 7 days
  • Cart Abandonment – Elevar: Added to Cart 0 times in the last 7 days
  • Checkout Abandonment – Elevar: Started Checkout 0 times in the last 7 days

Why this matters:

Klaviyo's default flows rely on client-side tracking, which is blocked by ad blockers, iOS restrictions, and poor network conditions, and the cookies expire after just 7 days. Elevar fills these gaps by sending events server-side with a persistent cookie that lasts up to a year, meaning customers who return weeks later can still be identified and your flows will still trigger.

(Optional) Review flow timing:

• Browse Abandonment: 3–7 hour delay
• Cart Abandonment: 2–4 hour delay
• Checkout Abandonment: ~1 hour delay
  • Also disable Smart Sending to ensure emails go out as soon as trigger conditions are met, and confirm each flow is set to Live.

If a flow shows $0 revenue, check that: the trigger metric is firing, exclusions aren't too restrictive, and the flow isn't in Draft status.

📘

Note: How to measure data accuracy, improvement & ROI:

Klaviyo is where you can most directly measure Elevar's revenue impact. View flow performance directly in the Flows section in Klaviyo and look for an increase in flow-attributed revenue for your Browse, Cart, and Checkout Abandonment flows after Elevar was activated. More events tied to profiles means more flows trigger, which means more recovered revenue.

To calculate ROI, compare the additional revenue generated by your Elevar-powered flows against your Elevar subscription cost. For example, if your subscription is $450/month and your Elevar flows generated $4,500 in additional revenue that month, your ROI is 10x.

Google Analytics 4 (GA4)

How to Measure Data Accuracy and Improvement:

In GA4, open your Traffic Acquisition report and compare unassigned traffic before and after joining Elevar. A reduction in unassigned traffic gives you greater clarity into where your website traffic is actually coming from, so you can see which channels are driving visits and conversions, the clearest signal that your data quality has improved.

Google Ads

Once Elevar is connected and sending server-side data to Google Ads, don't switch your bidding strategy straight away. First, observe the data by going to Google Ads > Conversions and confirm that the server-side conversions Elevar is tracking are recording more conversions than your previous setup. Once you've confirmed the volume is higher and the data looks accurate, set the Elevar-tracked conversion as the primary conversion action on your account. This is the step that actually impacts your bidding strategy and unlocks the performance benefit.

How to Measure Data Accuracy and Improvement:

Observe the secondary conversion action data in Google Ads. Whichever conversion action is tracking the most conversions should be set as the primary conversion action on the account, this is what impacts bidding and drives performance.