Question 1

What is server-side tracking?

Accepted Answer

Server-side tracking is a method that sends conversion events from your Shopify server to ad and email platforms instead of from the shopper's browser, so the data that browser pixels lose to ad blockers, iOS privacy and consent banners is still captured. A browser pixel fires from the visitor's device, where ad blockers, Safari and iOS restrictions, and declined consent banners stop a large share of events from ever reaching the platform. Server-side tracking moves that work to your server, which is far harder to block, and sends each event through an official platform API. The result is more complete, more reliable conversion data feeding your ad and email tools.

Question 2

What is the difference between client-side and server-side tracking?

Accepted Answer

Client-side tracking fires from the shopper's browser through a pixel, while server-side tracking fires from your server through an API, and the difference decides how much conversion data actually arrives. A client-side pixel like the Meta Pixel runs in the browser, so anything that blocks scripts also blocks the event: ad blockers, Safari ITP, iOS limits and declined consent. Server-side tracking sends the same event from your server, which those browser-level blockers cannot reach. Most stores run both and deduplicate, so they keep the speed of the pixel and the coverage of the server.

Question 3

What is the Conversions API (CAPI)?

Accepted Answer

The Conversions API is a server-to-server connection that lets platforms such as Meta receive conversion events directly from your server, separate from the browser pixel, so ad blockers and iOS restrictions are bypassed. Each ad platform has its own server-side endpoint: Meta calls it the Conversions API, Google has Enhanced Conversions, TikTok the Events API and Pinterest its Conversions API. Instead of relying on a script in the browser, your server posts the event straight to the platform. This keeps measurement working when the browser path breaks, and it lets you attach richer first party data to each event.

Question 4

What is event deduplication?

Accepted Answer

Event deduplication is the process of merging the same conversion event when it arrives both client-side from the pixel and server-side from the API, so the platform counts it once instead of twice. When you run a browser pixel and a server-side connection together, many conversions are sent twice. Deduplication uses a shared event ID and event name so the platform recognises the pair and keeps a single event. Without it your reported conversions inflate, bidding learns from wrong numbers, and ROAS looks better than it really is.

Question 5

What is first-party data?

Accepted Answer

First-party data is information you collect directly from your own Shopify store and shoppers, such as email, order details and on-site behaviour, as opposed to third-party cookies set by outside parties. Because it comes straight from your store and your customer relationship, first party data is accurate, consent-aware and not dependent on cookies that browsers keep restricting. It is the fuel for server-side tracking: the email, phone and order data that platforms use to match an event to a real user. As third-party cookies fade, first party data is what keeps targeting and measurement working.

Question 6

What is session enrichment?

Accepted Answer

Session enrichment is the practice of adding first party data to an event, such as shopper identifiers, product and cart context and session details, so platforms receive richer and more matchable signals. A raw conversion event is thin, often just a value and a timestamp. Enrichment attaches the context a platform needs to match the event to a user and to learn from it, like hashed email, click IDs, product IDs and cart contents. Richer events raise match quality, which improves targeting, bidding and reporting.

Question 7

What is data hashing and why is it used for tracking?

Accepted Answer

Data hashing is the one-way conversion of personal data such as an email address into a fixed, irreversible string, commonly with SHA-256, so it can be sent to ad platforms for matching without exposing the raw value. Platforms need identifiers like email or phone to match an event to a user, but sending those in the clear would be a privacy problem. Hashing turns the value into a fingerprint that cannot be reversed, yet still matches when the same input is hashed the same way on the platform side. It is the standard that makes privacy-safe first party matching possible.

Question 8

What is Event Match Quality (EMQ)?

Accepted Answer

Event Match Quality is Meta's score from 1 to 10 for how well your conversion events can be matched to Facebook and Instagram users, where a higher score means better targeting, optimisation and lookalikes. Meta calculates EMQ from the customer information you send with each event, such as hashed email, phone, name and click ID. Thin events score low and match poorly, so Meta has less to optimise against. Richer, server-side events score higher, which is why EMQ is one of the clearest levers for ad performance on Meta.

Question 9

What is Enhanced Conversion Coverage in Google Ads?

Accepted Answer

Enhanced Conversion Coverage is the share of your Google Ads conversions that include hashed first party data such as email, and the higher it is, the more accurately Google can measure and bid. Google Enhanced Conversions attach hashed customer data to each conversion so Google can recover matches that cookies alone would miss. Coverage is how much of your conversion volume carries that data. Higher coverage gives Smart Bidding more accurate signals, which improves both reporting and automated bidding.

Question 10

What is Meta Advantage+?

Accepted Answer

Advantage+ is Meta's suite of automated campaign and audience tools that lean heavily on your conversion data quality to target and optimise on their own. Advantage+ Shopping Campaigns and Advantage+ audiences hand targeting and budget decisions to Meta's automation. That automation is only as good as the events feeding it, so weak match quality leads to weak results. Clean, enriched server-side events give Advantage+ the signal it needs to find buyers efficiently.

Question 11

What is Meta Andromeda?

Accepted Answer

Andromeda is Meta's machine-learning ad retrieval engine that selects which ads to show from a huge candidate set, and it depends on rich, accurate event data to make good choices. Andromeda is the system behind Meta's recent jump in personalisation: it scores and retrieves the most relevant ads for each person in milliseconds. Better conversion signals let it learn faster and match ads to buyers more precisely. Stores that send complete, enriched events get more out of Andromeda-driven delivery.

Question 12

What is Smart Bidding in Google Ads?

Accepted Answer

Smart Bidding is Google's set of automated bidding strategies, such as Maximize Conversions and Target ROAS, that use machine learning and your conversion signals to set bids in real time. Smart Bidding decides how much to bid for each auction based on the conversions you report. If those signals are incomplete or delayed, it bids on a distorted picture and wastes spend. Accurate, well-matched server-side conversions let it bid toward the customers that actually convert.

Question 13

What are lookalike audiences?

Accepted Answer

Lookalike audiences are groups of new people that an ad platform finds because they resemble your existing customers, built from a source audience you provide. The platform studies the traits of a seed list, like your purchasers, and looks for similar users to target. The quality of the lookalike depends entirely on how clean and complete that seed data is. Enriched, well-matched conversion events build sharper seed audiences and therefore better lookalikes.

Question 14

What is the GA4 Measurement Protocol?

Accepted Answer

The GA4 Measurement Protocol is Google's server-side method for sending events directly to Google Analytics 4, so conversions are recorded even when the browser tag does not fire. The standard GA4 tag runs in the browser and loses events to blockers and consent the same way ad pixels do. The Measurement Protocol lets your server send events straight to GA4. That keeps your analytics complete and consistent with what your ad platforms see.

Question 15

What is the TikTok Events API?

Accepted Answer

The TikTok Events API is TikTok's server-to-server connection for sending conversion events directly from your server, the TikTok equivalent of Meta's Conversions API. Like other browser pixels, the TikTok Pixel loses events to blockers and privacy limits. The Events API sends conversions from your server instead, so TikTok receives more complete data to optimise and report on. Pairing it with the pixel and deduplicating gives the best coverage.

Question 16

What is the Pinterest Conversions API?

Accepted Answer

The Pinterest Conversions API is Pinterest's server-side connection for sending conversion events directly from your server, independent of the browser tag. The Pinterest tag fires in the browser and misses events to the usual privacy and blocking issues. The Conversions API lets your server report conversions to Pinterest directly. That gives Pinterest fuller data for optimisation and more accurate conversion reporting.

Question 17

What is iOS App Tracking Transparency (ATT)?

Accepted Answer

App Tracking Transparency is Apple's iOS feature that forces apps to ask permission before tracking users across other apps and sites, and because most people decline, it sharply cuts the data ad platforms receive. Since iOS 14.5, apps like Facebook and Instagram must show the ATT prompt, and the large share of users who opt out can no longer be tracked the old way. That broke a lot of browser-based attribution and shrank the audiences platforms could match. Server-side tracking with first party data is the main way stores rebuild that lost signal.

Question 18

What is Intelligent Tracking Prevention (ITP)?

Accepted Answer

Intelligent Tracking Prevention is Apple's Safari feature that limits and quickly expires tracking cookies, which shortens attribution windows and breaks cross-device measurement. ITP caps how long cookies set by scripts survive, often to a day or even hours. That means a shopper who returns later looks like a brand new visitor, so conversions get misattributed or lost. Server-side tracking and persistent first party identifiers are how stores keep measuring past ITP's limits.

Question 19

Do ad blockers block conversion tracking?

Accepted Answer

Ad blockers are browser tools that stop tracking scripts from loading, which means any conversion that relies only on a browser pixel is never recorded for that visitor. A meaningful share of shoppers run ad blockers or privacy browsers that block pixels outright. Every blocked pixel is a conversion your ad and email platforms never see, so your reporting under-counts and your bidding learns from gaps. Because server-side events come from your server, ad blockers cannot stop them.

Question 20

What is Google Consent Mode v2?

Accepted Answer

Consent Mode v2 is Google's framework that adjusts how tags behave based on a visitor's consent choices, and it is required for stores serving EU and UK shoppers who use Google Ads and GA4. When a visitor declines cookies, Consent Mode v2 stops tags from setting them and instead sends limited, cookieless signals that Google uses for modelling. Implemented well, it keeps you compliant while preserving as much measurement as the rules allow. It works hand in hand with server-side tracking to keep data flowing within consent.

Question 21

What is signal loss in conversion tracking?

Accepted Answer

Signal loss is the gap between the conversions that actually happen in your store and the ones your ad and email platforms manage to record, caused by ad blockers, iOS and Safari limits and declined consent. Browser pixels miss a large share of events, so platforms optimise and report on an incomplete picture. That gap quietly inflates CAC, hides your best campaigns and starves bidding of accurate data. Recovering lost signal is the core reason stores move to server-side tracking.

Question 22

What is the difference between last-click and data-driven attribution?

Accepted Answer

Attribution is how credit for a conversion is assigned across the touchpoints in a customer journey, where last-click gives all credit to the final click and data-driven attribution spreads credit across touchpoints based on their real influence. Last-click is simple but flattering and misleading, since it ignores everything that warmed the customer up. Data-driven attribution uses your conversion data to weigh each touch by its actual contribution, which is fairer but only as good as the data behind it. Incomplete tracking distorts either model, so clean server-side data has to come first.

Question 23

What is cross-device tracking?

Accepted Answer

Cross-device tracking is the ability to recognise the same shopper across phone, tablet and desktop, so a journey that spans devices is measured as one customer instead of several strangers. Shoppers routinely discover on mobile and buy on desktop, and cookie limits make each device look like a different person. Linking those sessions with persistent first party identifiers reconnects the journey. That gives you accurate attribution, deduplicated customers and better audience building.

Question 24

What are persistent shopper profiles?

Accepted Answer

Persistent shopper profiles link a shopper's activity across sessions and devices into one durable profile, so you can recognise returning and anonymous visitors over time. Instead of treating every visit as a fresh anonymous hit, a persistent profile stitches sessions together using first party identifiers. That makes it possible to trigger email flows for anonymous visitors, separate new from returning customers and measure long journeys. It is the backbone of cross-device tracking and anonymous-visitor recovery.

Question 25

What is anonymous visitor tracking?

Accepted Answer

Anonymous visitor tracking is the ability to recognise and remember a shopper who has not identified themselves yet, so you can act on their behaviour before they ever submit an email. Most store traffic is anonymous, and standard tools cannot do anything with it until the visitor hands over an email. By keeping a persistent first party profile, you can connect that email to the earlier anonymous behaviour the moment it appears. That unlocks abandonment flows and personalisation for visitors who would otherwise be invisible.

Question 26

What is the new vs returning customer signal?

Accepted Answer

The new vs returning customer signal tells ad platforms whether a converting shopper is a first-time buyer or an existing customer, so you can stop paying prospecting budget to acquire people you already have. Without this signal, platforms optimise toward easy repeat purchases from existing customers and call it new growth, which inflates results and wastes acquisition spend. Sending a clear new-versus-returning flag, derived from your Shopify customer data, lets campaigns optimise for genuine new customers. It sharpens both targeting and the way you read performance.

Question 27

What is cart and browse abandonment?

Accepted Answer

Cart abandonment is when a shopper adds items and leaves without buying, and browse abandonment is when they view products without adding anything, both of which are prime moments to recover with a timely email or ad. These are the highest-intent moments a store has, but recovery flows only fire when the abandonment is actually captured and tied to a contactable profile. Browser-only tracking misses many of these events, especially for anonymous or cross-device shoppers. Server-side capture with persistent profiles lets you trigger far more of them.

Question 28

What are UTM parameters?

Accepted Answer

UTM parameters are tags added to a link's URL that tell your analytics where a visitor came from, such as the source, medium and campaign, so traffic and conversions can be attributed to the right channel. A consistent UTM scheme is what lets GA4 and your other tools group sessions by campaign and compare channels fairly. Sloppy or missing UTMs scatter traffic into direct or unattributed buckets and break reporting. Clean UTMs are the foundation that attribution and channel analysis are built on.

Question 29

What are ROAS, CAC and MER?

Accepted Answer

ROAS (return on ad spend) measures revenue per advertising euro, CAC (customer acquisition cost) measures what you pay to win a new customer, and MER (marketing efficiency ratio) measures total revenue against total marketing spend across all channels. ROAS is reported per platform and is easily inflated by duplicated or misattributed conversions, while MER takes a store-wide view that is harder to game. CAC focuses on the cost of genuinely new customers, which is why the new-versus-returning signal matters. All three are only as trustworthy as the conversion data underneath them.

Server-side tracking glossary

Foundations

Match quality & platform signals

Server-side channels

Privacy & signal loss

Attribution, profiles & metrics

Foundations