Shopify
How to Send Shopify Acquisition Events to Meta and Google Ads
Send Shopify acquisition events (purchases, carts, checkouts, sign-ups) to Meta and Google Ads: which events matter, how to set them up and avoid duplicates.
By PixlBridge Team
Updated 20 min read
On this page
Every product view, add to cart, checkout and order on your Shopify store tells your ad platforms something about who buys. To send Shopify events to Meta and Google Ads, you connect your store to each platform separately: Meta receives events through the Meta Pixel and the Conversions API, and Google Ads through the Google tag and the conversion actions in your account.
Both platforms use these events for the same three jobs: reporting which ads led to sales, building audiences such as people who added to cart, and steering delivery and bidding toward people likely to buy. When events go missing, the platforms learn less. When the same purchase arrives twice, your reported ROAS (return on ad spend) looks better than it is.
A note on PixlBridge: PixlBridge publishes this guide. It’s a Shopify app that sends your store’s events to Meta through the Conversions API and reports your Meta ad results next to your Shopify sales. It doesn’t send anything to Google Ads, so the Google half of this guide uses Shopify’s and Google’s own tools.
How to send Shopify events to Meta and Google Ads: the short version
- Pick your events. Make Purchase the main conversion on both platforms, and send add to cart, checkout started and product views as supporting signals.
- Connect Meta. Connect your Meta Pixel through Shopify’s Facebook & Instagram app, then add server-side events through the Conversions API, using either that app’s data-sharing setting or a Conversions API app such as PixlBridge.
- Connect Google Ads. Install Shopify’s Google & YouTube app and link your Google Ads account. The app adds the Google tag and sets up conversion actions for purchases, add to carts and checkouts.
- Set priorities in Google Ads. Keep Purchase as the only primary conversion, set the others to secondary, and turn on enhanced conversions.
- Use one sender per event per platform. Remove old tags and overlapping apps so each sale reaches each platform once.
- Test, then compare. Place a test order, check Meta Events Manager and Google Tag Assistant, and compare both platforms with your Shopify orders.
What are Shopify acquisition events?
Shopify acquisition events are the actions shoppers take on your store on the way to becoming customers: viewing a product, adding it to the cart, starting checkout, signing up and buying. Each action is recorded as an event that can be shared with an ad platform, which uses it to measure results, build audiences and optimize campaigns.
The ones that matter for acquisition:
- View content: a shopper opens a product page.
- Add to cart: a product goes into the cart.
- Initiate checkout: the shopper starts checkout.
- Add payment info: the shopper enters payment details, a later checkout step.
- Purchase: a completed order, with its value and currency.
- Lead or sign-up: a newsletter sign-up or a new customer account.
- First purchase: an order from someone who hasn’t bought from you before.
Each system names these differently: Shopify’s customer events use names such as product_added_to_cart, Meta’s standard events use AddToCart, and Google uses add_to_cart. Page views and on-site searches are events too, but they’re rarely worth optimizing for.
Which events to send to each platform, and why
Purchase is the event to optimize for on both platforms. The others are supporting signals, and the two platforms use them differently:
| Shopper action | Meta event | Google Ads conversion | Why send it |
|---|---|---|---|
| Completes an order | Purchase | Purchase (primary) | The sale itself: optimization, value-based bidding and ROAS |
| Starts checkout | InitiateCheckout | Begin checkout (secondary) | Shows checkout drop-off; retarget unfinished checkouts |
| Adds to cart | AddToCart | Add to cart (secondary) | Strong intent; cart retargeting |
| Views a product | ViewContent | View item (optional, secondary) | Product interest; retargeting audiences |
| Enters payment details | AddPaymentInfo | Add payment info (optional, secondary) | Checkout progress |
| Signs up or leaves an email | Lead or CompleteRegistration | Sign-up or lead (secondary for most stores) | Email capture and lead campaigns |
| Buys for the first time | Purchase, with existing customers defined | Purchase with new-customer data | See and favor new customers |
| Views a page or searches | PageView, Search | Usually not a conversion | Audiences and diagnostics |
In Google Ads, primary conversion actions count in the Conversions column and drive bidding, while secondary ones are reported for observation only. In Meta, you choose one optimization event per ad set, usually Purchase, and the other events build audiences and appear in your reports. When an ad set gets too few purchases to learn from, optimizing for an earlier event such as AddToCart is a common fallback.
Every purchase should carry the order’s value and currency, a unique ID so repeats can be dropped (the transaction ID in Google Ads, the event_id in Meta) and, for better matching, customer details such as email and phone, hashed before they’re sent.
Sign-ups and leads
Shopify’s standard customer events don’t include a sign-up event. Newsletter and account sign-ups reach the ad platforms through the form or email app that collects them (some send a Lead or CompleteRegistration event to Meta themselves) or through a custom event a developer publishes from your theme. PixlBridge’s events cover shopping and checkout, not sign-ups. In Google Ads, keep a sign-up conversion action secondary unless lead generation is the campaign’s goal: a store that optimizes for sign-ups gets sign-ups, not necessarily sales.
First purchases and new customers
There’s no standard first-purchase event on either platform. The usual approach is to send every order as Purchase and tell each platform who your existing customers are:
- Google Ads has a new customer acquisition goal that can bid only for new customers, or bid higher for them. Google spots existing customers from its own purchase data, customer lists you upload and a
new_customervalue (true or false) sent with each purchase. According to Google, the Google & YouTube app sets that value for you, based on whether it’s the shopper’s first order in your store. - Meta lets you define existing customers, and an engaged audience, for your ad account with custom audiences such as a customer list or past purchasers. Sales campaigns then break results down into new, engaged and existing audiences.
How Shopify sends events: customer events, web pixels and apps
Shopify gives apps two ways to see what happens on your store, and a solid setup usually uses both. Each platform also has an official Shopify app: Facebook & Instagram, made by Meta, and Google & YouTube, made by Google, which covers Google Ads, Google Analytics and Merchant Center.
In the browser: customer events and web pixels
Shopify’s customer events are a stream of standard events from your storefront and checkout, such as page_viewed, product_viewed, product_added_to_cart, checkout_started, payment_info_submitted and checkout_completed. Web pixels subscribe to that stream, and you manage them in your Shopify admin under Settings → Customer events. There are two kinds:
- App pixels, added by apps you install, such as Facebook & Instagram, Google & YouTube or PixlBridge.
- Custom pixels, code that you or a developer add on the same page.
Pixels run in a sandbox, so they only see the data Shopify passes them, and they follow your customer privacy settings: in regions where you ask visitors for consent, a pixel runs only for visitors who give it. Shopify has also moved checkout tracking to this system, replacing older methods such as scripts pasted into the order status page, so tracking that still depends on code like that may no longer fire.
On the server: order webhooks and APIs
Shopify also notifies an app’s server about orders through webhooks, for example when an order is created or paid. The app can then send the order to an ad platform’s server API. That’s how server-side tracking works on Shopify: the event doesn’t depend on the shopper’s browser, and it comes with the full order, including the customer’s email and phone, which are hashed before they’re sent.
How to send Shopify events to Meta
Meta takes website events from two places: the Meta Pixel in the shopper’s browser and the Conversions API (CAPI) from a server. Meta recommends using both, with a shared event ID on each browser and server pair so it can keep one copy. You can set this up with Shopify’s own Meta app, with a Conversions API app, or with both, as long as you decide which one sends purchases.
Option 1: Shopify’s Facebook & Instagram app
- From your Shopify admin, add the Facebook & Instagram app from the Shopify App Store.
- Connect your Facebook account and choose your business portfolio, Facebook Page, ad account, Instagram account and Meta Pixel (Events Manager may list it as a dataset). Pick the pixel your ads already use rather than creating a new one.
- Open the app’s settings, go to its data-sharing settings, turn on customer data sharing and choose a level.
Shopify describes the three levels like this:
- Standard: the Meta Pixel only, from the shopper’s browser.
- Enhanced: the Meta Pixel plus the Conversions API, which sends the purchase event from Shopify’s servers to Meta’s, along with customer details for matching.
- Maximum: the same, plus Meta’s latest advertising technology.
So at Enhanced or Maximum, the app already sends purchases server-side, which is a complete setup on its own.
Option 2: a Conversions API app such as PixlBridge
A dedicated Conversions API app focuses on the server side: which events are sent, how they’re deduplicated and what reached Meta. With PixlBridge, setup takes four steps, with no code and no theme edits:
- Install PixlBridge from the Shopify App Store. Your account is created automatically.
- Connect Facebook & Instagram with Facebook Login for Business.
- Choose your ad account and the Meta Pixel your store already uses.
- Send a test event and check that it arrives in Meta.
The step-by-step guide to setting up the Conversions API on Shopify walks through each screen and the checks to run afterward.
Decide who sends purchases. At Enhanced or Maximum, Shopify’s Facebook & Instagram app also sends each order from the server, with its own event IDs, so Meta would count it twice. Either lower the app’s data sharing so it stops sending purchases server-side, or switch off Purchase in PixlBridge for that store; PixlBridge shows this reminder next to its Purchase switch and in the store health notes. Then compare the Purchase events Meta receives with your Shopify orders for a few days. The app’s browser pixel uses its own event IDs too, so if purchases still look doubled, switch off Purchase in PixlBridge.
Test your Meta events
In Meta Events Manager, open your pixel’s Test events tab, then browse your store: view a product, add it to the cart and start checkout. If you can, place a test order and check the Purchase event. For each event, look at the connection method (browser, server or both), the value and currency, and whether browser and server copies were deduplicated.
In PixlBridge, Send a test event (My store → More) sends a custom test event with no value, never a purchase, so it checks the connection without adding a sale. To see it in Meta’s Test events tab too, first copy the test code shown there into My store → Advanced settings → Test & tools, and clear the code when you’re done testing.
How to send Shopify purchase events to Google Ads
Google Ads measures results with conversion actions: each one defines something you count, such as a purchase, with settings for its value, how often it counts and whether bidding uses it. The standard route from Shopify is the Google & YouTube app. PixlBridge doesn’t send events to Google Ads, so use these steps, or another Google tracking tool, for this half.
Step 1: Install Google & YouTube and link your accounts
Install the Google & YouTube app from the Shopify App Store and sign in with the Google account that manages your Google Ads account. Link Google Ads and, if you use them, Merchant Center (for your product feed) and Google Analytics 4. The app loads the Google tag for each service you link, so there’s no code to paste. If you added Google tags by hand before, in theme code or a custom pixel, remove them once the app is tracking, so each sale is measured once.
Step 2: Review the conversion actions
When you link Google Ads, the app sets up conversion actions for purchases, add to carts and checkouts started. In Google Ads, open Goals → Conversions → Summary and check each action’s settings:
- Primary or secondary: for most stores, Purchase should be the only primary action. If add to cart or begin checkout are primary too, bidding counts carts alongside sales.
- Value: purchases should carry each order’s value and currency, so conversion value and ROAS reflect real revenue.
- Count: “Every” for purchases, since each order counts; “One” for leads.
- Transaction ID: each purchase should carry the order’s ID, so Google Ads can drop repeats.
- Attribution: the conversion window and the model (data-driven by default) decide how many sales Google Ads credits to its ads.
Step 3: Turn on enhanced conversions
Enhanced conversions add hashed first-party data from the order, such as the customer’s email, to the conversions your Google tag sends, so Google can match more sales to ad clicks. In the Google & YouTube app, open Settings, find Enhanced conversions under Google Ads settings, turn it on and accept Google’s customer data terms.
Step 4: Test it
Use Google Tag Assistant to check your tag setup, then place a test order and confirm the purchase carries the right value, currency and transaction ID. Each conversion action in Google Ads shows a status, such as Recording conversions or No recent conversions. New actions can take a few hours to update, so check again the next day.
Developers have other routes too: adding the Google tag themselves through a custom pixel, server-side tagging, or uploading conversions from order data. They give more control but need more upkeep. Whichever you choose, keep one source per conversion action.
Shopify conversion tracking for Meta and Google Ads together
Running both platforms on one store is normal and causes no conflict by itself, because each platform only reads its own events. Meta never sees your Google tag, and Google Ads never sees your Conversions API events. A typical setup looks like this:
| Meta | Google Ads | |
|---|---|---|
| Browser | Meta Pixel (Facebook & Instagram app) | Google tag (Google & YouTube app) |
| Server | Conversions API: the app at Enhanced or Maximum, or a CAPI app such as PixlBridge | Optional: server-side tagging or conversion uploads |
| Customer matching | Hashed customer details on events | Enhanced conversions |
| Duplicates dropped by | Same event name and event_id within 48 hours | Same transaction ID within one conversion action |
| Main conversion | Purchase | Purchase, set as primary |
Why the two platforms report different sales
Send the same purchase to both platforms and both may claim it. A shopper who clicks a Google ad, sees an Instagram ad two days later and then buys can count as a conversion in both reports, because each platform credits sales to its own ads under its own attribution window and model. Meta’s default setting also counts some people who saw an ad without clicking it. Add the two platforms’ conversions together and you’ll often get more sales than Shopify recorded.
Neither report is wrong by its own rules. Shopify’s orders are the record of what actually sold, so judge overall efficiency with blended ROAS: all store sales divided by all ad spend, Meta and Google together.
Where server-side tracking fits
Server-side tracking sends events from a server to the ad platform’s API instead of from the shopper’s browser. Browsers lose events to ad blockers, tracking protection, slow connections and tabs closed too early; a server-side event doesn’t depend on any of them. It also starts from the full order, so it can carry hashed customer details that help the platform match the sale to a person.
| Browser (client-side) | Server-side | |
|---|---|---|
| Sent from | The shopper’s browser | A server, run by an app or by you |
| Examples | Meta Pixel, Google tag | Meta Conversions API; Google server-side tagging or conversion uploads |
| Ad blockers and browser limits | Can stop the event | Don’t decide whether it arrives |
| Order and customer data | What the page exposes | The full order, with hashed customer details |
| Strongest at | Browsing signals, cookies and click IDs | Purchases and checkout events |
Server-side tracking doesn’t remove your privacy obligations, and it doesn’t fix a wrong setup: a server that sends duplicate purchases or wrong values makes your reports worse, not better.
For Meta, the Conversions API is the standard server-side route, and it works best next to the pixel. For Google Ads, the Google & YouTube app’s tag with enhanced conversions covers most stores. Turning on the Conversions API sends nothing to Google. For a fuller comparison of the two approaches, see client-side vs server-side tracking.
How to prevent duplicate conversions
Most duplicates have the same cure: one source per event per platform. Two tools sending purchases to Meta, or two primary purchase actions in Google Ads, count each sale twice.
On Meta: matching event IDs
Meta merges a browser event and a server event when they have the same event name and the same event_id and arrive within 48 hours of each other. So the pixel and the Conversions API can both send a purchase, as long as they share the ID. A browser pixel that sets its own IDs can’t be merged with server events that use different ones, and two server-side senders with their own IDs will double count. For examples of what breaks deduplication, see how deduplication works in practice.
On Google Ads: one primary purchase action
Google Ads drops a purchase when the same transaction ID arrives twice for the same conversion action. It doesn’t compare across actions, so if two purchase actions record one order, for example the Google & YouTube app’s and one from an old hand-added tag, both count when both are primary. The same happens if you import a purchase key event from Google Analytics 4 and also keep the app’s purchase action as primary. Keep one primary purchase action and set the others to secondary, or remove the old tags.
Keep a tracking map
Write down, in a few lines, which tool sends which event to which platform. Check it whenever you install or remove an app, change your theme or change checkout: duplicates often appear after a new app adds its own tracking.
How PixlBridge helps on the Meta side
PixlBridge covers the Meta half of this setup. Here’s how PixlBridge’s Meta Conversions API for Shopify works.
What it sends
Shopify’s Web Pixel captures storefront and checkout activity, and order webhooks add the order and customer details. Each event type can be switched off per store.
| Shopify customer event | Sent to Meta as |
|---|---|
| page_viewed | PageView |
| product_viewed, collection_viewed | ViewContent |
| search_submitted | Search |
| product_added_to_cart | AddToCart |
| checkout_started | InitiateCheckout |
| payment_info_submitted | AddPaymentInfo |
| checkout_completed + the paid order | One Purchase with full match keys |
- Email, phone, name, city, state, zip and country are normalized and SHA-256 hashed before sending, and raw values aren’t stored. Click IDs (fbc and fbp), IP address and user agent are sent as Meta expects.
- Each event gets a deterministic
event_idbuilt from Shopify’s own identifiers, so a browser pixel that uses Shopify’s event IDs isn’t counted twice. - Events reach Meta within seconds, and purchases within about a minute. If sending fails for a temporary reason, retries start at one minute and double each time; after five attempts the event is marked failed with Meta’s message.
- The web pixel respects Shopify’s customer privacy settings. Purchases built from order webhooks are sent from the server, so make sure your privacy policy covers that sharing.
Beyond the test event, the Meta Pixel + Conversions API status panel and Recent activity show events as “Sent to Meta (CAPI)”, and store health shows event counts and the share of purchases carrying each match key, such as email or phone.
ROAS reporting next to your Shopify sales
Once events flow, PixlBridge’s Ads overview shows ad spend, purchases, purchase value and ROAS by campaign, ad set and ad, with each ad’s creative. Home puts your Shopify sales next to your Meta ad spend as blended ROAS, “Why no sale?” lists products that get traffic but no sales, and alerts and reports arrive by email.
If you also run Google Ads, keep one thing in mind: PixlBridge connects Meta only, so its blended ROAS divides all your store sales, including those Google Ads drove, by your Meta spend. Treat it as a quick check, and add your Google spend when you want the all-channel figure.
PixlBridge doesn’t send events to Google Ads or any other ad platform, so keep Shopify’s Google & YouTube app for Google Ads; the two don’t interfere. PixlBridge for Shopify shows the whole app.
Common problems and how to fix them
Purchases are missing on one platform
Usually an app pixel is disconnected, a conversion action isn’t active, or visitors in a consent region declined tracking. Fix: check Settings → Customer events in Shopify, the event overview in Meta Events Manager and the conversion action’s status in Google Ads. In PixlBridge, failed events are listed with Meta’s reason.
Purchases look doubled
Meta receives about twice as many Purchase events as you had orders, or Google Ads records two conversions for one order: two tools are sending the same sale. Fix: list every tool that sends purchases to that platform and keep one. If Meta and Google Ads together simply claim more sales than you made, that’s attribution overlap, not duplication.
Purchase values don’t match Shopify
Check the currency (a multi-currency store can send either the shopper’s currency or the store’s), whether tax and shipping are included, and how discounts are handled. Ad platforms also record a purchase’s value when it happens, so later refunds usually aren’t subtracted. Fix: compare one event’s value with the same order in Shopify, and adjust the tool’s settings if they differ.
Browser events arrive but server events don’t
In Meta Events Manager, events that show only the browser connection method mean the Conversions API isn’t sending. Fix: check the app’s connection to Meta. With PixlBridge, if Meta refuses events because of the Facebook login, for example error #270 when the person who connected isn’t an admin of the ad account, PixlBridge holds the events, retries them daily and shows in the dashboard how to fix the login.
New and returning customers are mixed up
New-customer reporting is only as good as your definition of an existing customer. Fix: keep customer lists up to date on both platforms and, if you set new_customer yourself rather than through the Google & YouTube app, use one consistent rule, such as no order in the past 540 days, Google’s default.
Tracking broke after a theme or checkout change
Tags pasted into theme code or old checkout scripts can stop firing when the theme or checkout changes, or keep firing next to a new app pixel. Fix: move tracking to app or custom pixels, remove the old code and run a test order on both platforms.
Best practices for clean event data
- Cover privacy on both sides. Shopify’s customer privacy settings decide when web pixels run in the regions you sell to, but they don’t control events an app sends from your order data on the server, so make sure your privacy policy covers that sharing too.
- Test after every change. A new app, a theme change or a checkout change is a reason to place a test order and check both platforms.
- Watch match quality. In Meta, check Event Match Quality (EMQ), Meta’s score for how well your events’ customer details match its users. In Google Ads, check the enhanced conversions diagnostics on your purchase action.
- Compare with Shopify every week. Check each platform’s purchases against your orders, and your blended ROAS across all ad spend.
Summary
To send Shopify events to Meta and Google Ads, set up each platform on its own terms: the Meta Pixel plus the Conversions API for Meta, and the Google tag, enhanced conversions and well-configured conversion actions for Google Ads. Make Purchase the main conversion on both, keep one sender per event per platform, and check both against your Shopify orders.
For the Meta half, PixlBridge sends your store’s events through the Conversions API and shows Meta ad results and ROAS next to your Shopify sales, with no code. For Google Ads, keep Shopify’s Google & YouTube app. PixlBridge starts at $29 a month, with a 14-day free trial and no card needed.
Frequently asked questions
What are acquisition events in Shopify?
They are the actions shoppers take on the way to buying, such as viewing a product, adding it to the cart, starting checkout, signing up and purchasing. Apps share them with ad platforms like Meta and Google Ads for measurement and optimization.
Can I send Shopify events to Meta and Google Ads at the same time?
Yes. Each platform needs its own integration, such as Shopify’s Facebook & Instagram app or a Conversions API app for Meta and the Google & YouTube app for Google Ads. They don’t interfere; duplicates only happen when two tools send the same event to the same platform.
Which Shopify events should I send to Google Ads?
Make Purchase the primary conversion, with each order’s value, currency and transaction ID. Add to cart and begin checkout work well as secondary conversions, which show in reports without steering bidding.
Does Shopify’s Facebook & Instagram app use the Conversions API?
Yes, at its Enhanced and Maximum data-sharing levels, according to Shopify’s help center; Standard uses the Meta Pixel only. If you also use a Conversions API app such as PixlBridge, let only one of them send purchases.
What is the difference between Meta’s Conversions API and Google’s enhanced conversions?
The Conversions API sends events to Meta from a server, alongside the browser pixel. Enhanced conversions add hashed customer data, such as email, to the conversions your Google tag already sends, so Google can match more of them to ad clicks.
How do I stop Shopify purchases from being counted twice?
Use one sender per event per platform. For Meta, browser and server copies must share the same event name and event_id; for Google Ads, keep one primary purchase action and send each order’s ID as the transaction ID.
Why do Meta and Google Ads report different numbers of sales?
Each platform credits sales to its own ads under its own attribution window and model, so both can claim the same order. Use Shopify’s orders as the reference.
Can PixlBridge send Shopify events to Google Ads?
No. PixlBridge sends Shopify events to Meta through the Conversions API and reports Meta ad results and ROAS next to your Shopify sales. For Google Ads, use Shopify’s Google & YouTube app alongside it.






