Order gap report
Meta's purchases compared with your Shopify orders, so you see how much the pixel alone misses.
Meta Conversions API setup for Shopify: server-side purchases, shared event IDs, and hashed matching, tested in Events Manager. From $550.
2X
Signal paths per purchase
100%
Events deduplicated by ID
How your project runs
Teams we have built for:








The Problem
It gets worse as more shoppers use ad blockers and privacy browsers. The pixel doesn't fire for some of them, so Meta can't see those sales.
01 · Missing sales
Ads Manager shows fewer purchases while Shopify orders rise.
Meta's purchases get lined up against your Shopify orders day by day.
02 · Blocked pixels
Some shoppers block the pixel entirely.
A server feed sends each purchase even when a browser blocks the pixel.
03 · Device switching
Shoppers tap an ad on one device and buy on another.
Hashed email, phone, and click IDs help Meta match buyers to ads.
04 · Unloaded pages
Some Thank you pages don't load, so no purchase fires.
Server events share the pixel's event ID, so Meta keeps one copy.
Your Shopify orders are up this week, but Ads Manager shows fewer purchases than last week. Some shoppers block the pixel. Others tap your ad in an in-app browser, then buy later on a laptop. A few Thank you pages don't finish loading, so no purchase event fires at all. Meta's delivery system optimizes on the sales it can see, so your best campaigns start to look like your worst.
We start by lining up Meta's reported purchases against your Shopify orders, day by day. Then we add a server feed that sends each purchase with the same event ID your pixel uses, so Meta counts it once. Hashed email and phone help Meta match buyers to ad clicks. Once purchases flow through the Conversions API, Facebook and Instagram campaigns learn from the sales you made, not just the ones a browser reported.
Purchases sent from the server
Each order can reach Meta from the server, even when a browser blocks the pixel.
Counted once, not twice
Browser and server copies share one event ID, so Meta keeps one and drops the other.
Better buyer matching
Hashed email, phone, and click IDs help Meta connect purchases to the ads that drove them.
Our CAPI Setup Process
You see Meta's numbers next to your Shopify orders before we touch anything. You pick the route, and we test in Events Manager before launch.
We line up Meta's reported purchases against your Shopify orders and check your pixel and data-sharing setup. On a quick call, we walk you through the gap and the cheapest route that closes it. If Meta's app at Maximum covers you, we'll say so.
What's Included
Every plan closes the gap between Meta and your orders. Larger plans move from the free app or Gateway to a server container or a direct Shopify integration.
Compare Options
Meta's free app sends purchases server-side at Enhanced or Maximum, and paid CAPI apps add more events for a monthly fee. Here's where each option stops.
| Feature | DeveloperLookBest fit | Meta's free app | Paid CAPI app |
|---|---|---|---|
| Upfront cost | From $550, fixed scope | Free | Low setup cost |
| Ongoing cost | Cloud fees only, if any | None | Monthly subscription |
| Server-side events | Every event you choose | Purchase, per Shopify | Varies by app |
| Offline and recurring orders | Sent with action source | Not supported | Some apps |
| Deduplication | Tested with test orders | Handled by the app | Handled by the app |
| Match data | Email, phone, IDs, click IDs | Set by data sharing level | Varies by app |
| Where it runs | Your cloud or Shopify app | Meta and Shopify | Vendor's servers |
| Code ownership | Yours, documented | Run by Meta | Stays with the vendor |
Projects We've Built
A selection of ecommerce stores and apps we've built. Server event work draws on the same skills: clean order data, careful API work, and testing with real orders.
What Our Clients Say
Feedback from ecommerce teams we have built stores, apps, and server integrations for.
We had a different kind of problem. People were visiting the store, adding products to their carts, and then disappearing before they finished the order. We had tried a few apps and made changes here and there, but nothing really seemed to solve the bigger issue. The team went through the shopping experience with us and pointed out things we hadn't really noticed ourselves. They cleaned up the cart and checkout flow, made the mobile experience much smoother, and helped us make the store feel easier to shop. I’m not going to pretend we fixed everything overnight, but it finally feels like the store is helping the sale instead of getting in the way of it.
The mobile experience is probably my favourite part of the new site. We had spent a lot of time making sure the desktop version looked right, and the team kept pushing us to think about how everything would actually feel on a phone too. They were right. The navigation is clean, the interactions feel natural, and everything we’ve tested so far works exactly as it should. They also went through the links, forms, integrations, and other details more than once before launch, which I really appreciated. And even after going live, we could still reach out when something came up. The whole process felt friendly, organised, and surprisingly straightforward.
We had a pretty specific idea of what we wanted our website to become, but I wasn’t sure how easily we could explain all of it to a development team. There were quite a few moving parts, and we were working toward a deadline, so I expected a few things to get lost along the way. That never really happened. They understood what we were trying to achieve, kept us updated throughout the process, and got everything ready within the agreed timeline. The final site feels much easier to navigate, works beautifully on mobile, and is noticeably smoother for our customers. It was a huge relief seeing the original idea actually turn into the website we had in mind.
1,000+
Projects shipped
10+
Years of experience
Top 3%
Upwork Top Rated Plus
5 stars
Average review score

Want results like these?
Tell us what you are building. You get a reply within 24 hours on business days, then a written estimate.
Work Culture
Server events are invisible to shoppers, so mistakes can hide for months. These habits keep your Meta data honest from launch.
We build each event ID from the Shopify checkout or order, so browser and server copies match. Meta then keeps one copy and drops the duplicate.
Email and phone are hashed with SHA-256 on the server before anything goes to Meta. Raw customer details stay inside your own systems.
Meta's free Shopify app at Maximum covers many stores. We recommend the Gateway or a custom build only when your events or margins call for it.
Meta accepts server events up to 7 days old, per its documentation. Our retry queue resends failed events well inside that window, so outages don't erase sales.
Every route gets test orders in Events Manager before it goes live. You watch the browser and server copies arrive and merge into one event.
The Gateway or server container runs in your own AWS or Google Cloud account, with an access token from your business portfolio. Nothing depends on a vendor account.
Overview
DeveloperLook sets up Meta Conversions API for Shopify stores, so purchases can reach Meta from a server even when a browser blocks the pixel. We match event IDs with your pixel, add hashed customer details, and test every event in Events Manager. Setups start at $550 and take 3 business days to 3 weeks, via the free app, the Gateway, or a custom build.
DEVELOPERLOOK
Project facts · Conversions API Setup Services
Reviewed 28 Sep 2026 by Saimul Islam
Good fit
Stores whose Meta sales look too low
Your Shopify orders keep growing, but Meta reports fewer purchases each month, and you can't tell which campaigns really work.
Stores already on the free app
You already run Shopify's Meta app at Maximum and now need server events for renewals, quizzes, or phone orders too.
Subscription brands with recurring orders
Your renewals charge automatically, so no browser fires a purchase, and Meta doesn't see your best repeat customers.
Teams comparing Gateway and custom builds
You're weighing Meta's Gateway against a custom build and want the cloud costs sized before you commit.
Agencies running Meta ads for clients
You manage Meta campaigns for several Shopify brands and need server events built and tested under your agency's name.
Not a fit
Pixel still misfiring
Your pixel still fires twice or sends purchases with no value. The Meta Pixel Setup for Shopify page fixes the browser side first.
GA4 and TikTok too
You want GA4, TikTok, and Google Ads fed from one server as well. See our Server-Side Tracking Setup service for that wider build.
GA4 numbers are wrong
Your purchase numbers in GA4 are the problem, not the ones in Meta. Start with our GA4 Setup and Audit Services instead.
Small Meta budget
Your Meta budget is small, and the free app at Maximum already shows purchases close to your orders. A $550 setup won't pay off yet.
Not sure we're the right fit?
Book a free call or message us. We'll tell you honestly whether we're the right team.
Pricing
These are starting points in USD. Your final price depends on the route, the events you send, and your order sources, and you get a fixed proposal after a free CAPI review.
For stores that need purchases sent server-side without custom code to maintain.
$550one-time, USD
For stores that want every shopping event sent server-side with full control of match data.
$1,250one-time, USD
For brands with renewals, phone orders, or custom funnels a browser cannot see.
$2,400one-time, USD
For Agencies
You own the client relationship and the ad account. We supply the server events behind it: the route choice, the build, deduplication testing, and handover notes written under your brand.
White label: your client only ever sees your brand
Share Events Manager access, the store URL, and the client's monthly order volume.
You get a route recommendation, a cloud cost estimate, and one fixed price.
We build, test with real orders, and hand over notes under your brand.
We stay behind your brand while you run the client and their ad spend.
One fixed price per route, agreed before any cloud setup.
Test Events screenshots show your client each merged event.
Bring us in for one store or a roster of ad accounts.
The Right Technology for Your Project
We send server events through Meta's own tools, Shopify webhooks, and Tag Manager server containers, hosted in your cloud account.
FAQ
Straight answers on setup costs, routes, deduplication, match quality, iOS, and who owns the setup.
Saimul IslamFounder & CEO, DeveloperLookStill have questions?
Send a message or book a call with the team.
Setup starts at $550 for the free Shopify app tuned to Maximum, or Meta's Gateway in your cloud account. A server container with every shopping event costs $1,250. Direct builds from Shopify webhooks, including subscription renewals, cost $2,400. Any cloud fees are billed to you by your provider.
Plan on 3 to 5 business days for Meta's app or the Gateway, test orders included. Server container and direct builds take 1 to 3 weeks, mostly for webhook work and match testing. A 2-week check against your orders follows launch, to catch anything the tests missed.
You need both, and Meta recommends running them together. The pixel captures browsing events such as product views, while the server feed, once called the Facebook Conversions API, covers purchases the browser misses. Shared event IDs let Meta merge the two copies, so running both doesn't double your numbers.
Use the simplest route that covers your events. Meta's Gateway needs no code and runs in your AWS or Google Cloud account, and Meta says cloud or partner fees are its only cost. Server-side GTM suits stores feeding several platforms. A direct build suits renewals and phone orders a browser can't see.
We give both copies of each event the same event name and an event ID built from the Shopify checkout or order. Meta keeps whichever copy reaches it first within 48 hours. Where an ID can't be shared, Meta can fall back on the browser ID, but only when the browser event arrives first.
Send more customer details with each server event, hashed first. Meta scores each event's match quality out of 10 in Events Manager. Email, phone, name, and an external ID matter most, along with the click and browser IDs from the pixel, the IP address, and the user agent.
It recovers part of the loss, not all of it. Server events don't depend on browser cookies or ad blockers, so more purchases reach Meta. Apple's App Tracking Transparency choices still limit how Meta uses data from people who opt out, whichever route the event takes.
Place a test order while the Test Events tab is open in Events Manager. You should see the purchase arrive from the browser and from the server, then count as one event. Over the next 2 weeks, Meta's purchases should track your Shopify orders closely, and each event's match quality should hold steady.
You do, because the Gateway or server container runs in your own cloud account. The access token also sits in your Meta business portfolio. Our team only uses the access you give us, and handover notes show your team how to replace the token and check event health.
Support runs 30 to 60 days after launch, depending on your plan. During that time, we watch match quality, fix failed events, and update the setup if Meta retires an API version. After that, alerts and handover notes help your own team catch problems early.
Saimul IslamFounder & CEO, DeveloperLookStill have questions?
Send a message or book a call with the team.
Free 30-min callGoogle Meet
Book a call
In 30 minutes on Google Meet we walk you through how we would build it, how long it takes and what it costs. Then you get a written estimate.
Calendar not showing? Book on cal.com or send a brief.