Fewer conversions than real leads
Your CRM shows 30 leads from Meta this month, Ads Manager reports 18. The algorithm optimizes on the 18.
Ads and visibility: customers who are looking for your service now or don’t know about it yet.
01 Google AdsInquiries from people searching for your service right nowfrom $1,000/mo 02 Social media adsMeta, TikTok, LinkedIn: customers who are not searching yetfrom $600/mo 03 SEOHigher in Google and Maps without paying per clickfrom $750/mo 04 Visibility in ChatGPT and AIYour business in AI assistant answerspart of SEO 05 Amazon and marketplacesSell where customers already buywith a partnerThe place where a visit turns into an inquiry, and a system that doesn’t lose that inquiry.
01 Web designA website that turns visits into inquirieslanding from $1,000 02 Online storesCart, payments and shipping, ready for adsfrom $3,900 03 CRMNo inquiry gets lost in a phonesetup $3,000 04 Chatbots and AIThey answer customers, at night too$1,900 05 Email and SMSCustomers come back instead of forgetting youquoted individuallyPlan and tracking first, budget second. You know what works before you spend more.
01 Strategy and auditKnow where to spend the budget before you spend it$1,900 02 AnalyticsSee which ad brings in money$550 03 ConsultationsA call about your specific problem$65/h 04 Free auditA quick review and 3–5 priorities to start$0How your business looks and sounds before anyone calls you.
01 Social media managementProfiles that look like a real businesswith a partner 02 Creative and videoGraphics and videos that stop the thumbquoted individually 03 BrandingA logo and style that sets you apartwith a partner
Edmonton, Canada
200 keywords on page one of Google
Boreal Kitchens
Winnipeg, Canada
up to 5 inquiries/mo from Google without ads
Adela Realtor
Żywiec, Poland
from 3 to 9 locations in two years
Gładko Tnący Barber
Żywiec, Poland
PLN 15 000 +/mo in delivery orders
Da Diego
The Meta Pixel and Conversions API together tell Facebook and Instagram which ad clicks turned into leads and sales. The pixel works in the browser and misses a share of events because of ad blockers and privacy settings; the Conversions API sends the same events from a server. I set up both, remove duplicates and check match quality in Events Manager.
Free: a 30-minute call, an action plan and a price range in writing.

Your CRM shows 30 leads from Meta this month, Ads Manager reports 18. The algorithm optimizes on the 18.
Pixel and server events without a shared event ID inflate results and make cost per lead look better than it is.
Without good signals the system finds people who fill in forms, not people who buy.
Created in a former agency's Business Manager, so you can't share it, fix it or see its history.
I set up events so that calls, forms and messages are counted, not just visits.
Prices in US dollars.
Meta Pixel as part of the GA4, Tag Manager and Google Ads setup.
Server-side events with deduplication. Depends on your website, store platform and CRM.
Campaigns run on clean data, with reports every two weeks.
The Meta Pixel is a piece of code in the visitor's browser. When someone views a page, submits a form or completes a purchase, it reports the event to Meta. The problem is that browsers increasingly limit what such code can do. Ad blockers stop it, Safari restricts cookies, iPhone users opt out of tracking in apps, and some visitors decline cookies on your banner.
The Conversions API sends the same events from a server instead. Your website, store platform or CRM tells Meta directly that a lead or purchase happened, with hashed customer details like email or phone that help Meta match the event to a person. Because it doesn't depend on the browser, it fills many of the gaps.
Running both with deduplication gives Meta the most complete picture. That matters because Facebook and Instagram ads optimize based on conversions: the better the signal, the better the targeting.
After setup I check four things in Meta's Events Manager:
If any of these is off, results in Ads Manager can be misleading for weeks before anyone notices.
There are several ways to send server events, and the right one depends on your setup:
I'll recommend the simplest route that gives reliable data for your budget. There's no point in a complex server setup for a few hundred dollars a month in ads.
Meta's delivery system needs a stream of conversion events to learn from. After the Conversions API goes live, reported conversions usually rise within days, because events the pixel used to miss now arrive. Changes in cost per lead take longer, typically a few weeks, as campaigns adjust to the better signal. I compare reported leads with your CRM or inbox before and after, so you can see the difference in real numbers rather than in a platform dashboard alone.
The pixel and its dataset should live in your own Business Manager, with your domain verified there. If a former agency created them in theirs, you may be able to request a share, but often the cleanest path is a new pixel under your ownership, installed in parallel for a short period. I handle that transition so campaigns don't lose their footing.
If you advertise housing, employment, credit or financial products, or social issues and politics, Meta puts your ads in a special ad category with restricted targeting. Tracking still works, but some optimization options and audiences are limited. Meta special ad categories explains the rules.
Healthcare deserves extra caution. Events from pages where patients book or describe symptoms can carry protected health information. I keep those events generic or remove them, and I suggest a review with your compliance advisor.
The real gain comes when Meta learns which leads turned into customers. If you use a CRM, qualified leads and closed deals can be sent back as events, so campaigns optimize toward people who buy rather than people who fill in forms for free advice. That is part of end-to-end analytics. Combined with campaigns from my Meta ads management, it closes the loop between ad spend and revenue.
If you spend modest amounts on Meta ads and most conversions are tracked, the pixel may be enough for now. As the budget grows, the share of events the pixel misses starts to matter, and Meta itself recommends running both. I'll look at your numbers before suggesting it.
When both the pixel and the server report the same lead, Meta needs a shared event ID to know it's one lead, not two. Without it, results look better than they are and the algorithm learns from inflated data. Setting this up correctly is a large part of the work.
With great care, if at all on patient-facing pages. Meta restricts sharing certain health information, and HIPAA-covered practices face real risk if pixels send protected data. I limit events and parameters on those pages and recommend a review by your compliance advisor.
Not always. Many platforms offer a built-in integration, and Meta offers a gateway option. Server-side Tag Manager is another route, with modest hosting costs paid by you directly to the cloud provider. I recommend the simplest option that gives reliable data.
Yes, for example when a lead becomes a qualified lead or a paying customer. This lets Meta optimize for leads that close, not just for form fills. It's part of end-to-end analytics and depends on your CRM.
Tell me your website platform, your monthly Meta budget and what counts as a lead. I'll reply within one business day, or we can talk on a free 30-minute call.