Meta Ads Management for Facebook and Instagram, Built on a Clean Conversions API
On Meta, the algorithm decides who sees your ads, so you win on two inputs: the conversion signal you send and
the creative you give it. John Williams manages Facebook and Instagram ads with a Conversions API setup that
Meta can actually match, and a creative pipeline that keeps up with it.
Signal comes first: Meta Pixel plus the Conversions API, deduplicated on matching event_id and event_name,
with Event Match Quality monitored for each event.
Advantage+ sales campaigns (Meta's new name for Advantage+ shopping) are the default for ecommerce,
configured on purpose rather than accepted as-is.
Creative is the main lever. We build a testing system around concepts, not around one-off ads.
Lead-gen campaigns optimize toward qualified leads sent back from your CRM through the Conversions API, not
raw form submissions.
Flat fee, quoted after an audit. Nothing is billed as a percentage of spend.
Who this is for
Ecommerce brands where Meta drives a meaningful share of new customers but reported purchases
don't match the store.
Lead-gen businesses getting plenty of cheap Meta leads that sales can't close.
Brands running Google well that want Meta handled with the same measurement discipline.
Teams with creative fatigue: the same five ads running for months and costs climbing.
Signal: Pixel plus Conversions API, done the way Meta documents it
Meta's
Conversions API
connects your server, website platform, app, or CRM to Meta's systems. If you already have a Pixel, you can set
it up in one click from Events Manager, or build a direct integration for more control. Meta recommends running
Pixel and CAPI together, which it calls a "redundant setup." That setup needs deduplication:
Matching IDs and names. The Pixel's eventID must equal the server's
event_id, and the event names must match. Meta discards later duplicates received within 48 hours
(Meta deduplication docs).
Required parameters. Website events sent through CAPI need action_source,
event_source_url, and client_user_agent (CAPI best practices).
Match quality. Event Match Quality is a 0–10 score, calculated from the last 48 hours of
events, that shows how well your customer information matches events to Meta accounts (About event match quality). Matched events are what let Meta attribute conversions to your ads and find people likely to convert. Meta
rates email and click ID as the highest-priority parameters, with phone, external ID, and browser ID next, so
hashed email, the fbc click value, and fbp are what move the score most.
Normalization before hashing. Emails trimmed and lowercased, phone numbers converted to the
international E.164 format (ITU-T E.164), then hashed with SHA-256 as specified in
NIST FIPS 180-4.
A stray capital letter or missing country code produces a different hash that matches nobody.
The full server-side build (hosting, consent propagation, CRM events) is covered on our
server-side tracking page.
What's included
Signal audit and rebuild: Pixel events, CAPI coverage, deduplication test, Event Match
Quality by event, and the parameter fixes that raise it.
Account structure: an Advantage+ sales campaign for ecommerce prospecting where it fits,
separate campaigns only where budgets or offers really differ, and exclusions set at the ad account level
where Meta allows.
Creative system: a concept matrix (problem, proof, offer, format) with a steady cadence of
new concepts, copy variants from our Social Media Ad Builder, and
assets checked against placement specs with the
Creative Asset Validator.
Lead quality loop for lead gen: CRM stages sent back through CAPI so campaigns can optimize
toward qualified leads.
Reporting: Meta-reported results next to backend orders or CRM outcomes, so you can see how
much the platform reports versus what actually landed.
How John runs Meta ads
Fix the signal before the spend
Test purchases and leads in Events Manager, confirm deduplication, raise Event Match Quality, and make sure
the event that campaigns optimize toward is the one the business actually values.
Let Advantage+ do what it's good at
Meta describes Advantage+ sales campaigns as its most efficient option for online sales when Advantage+
audience, placements, and budget are all on (About Advantage+ sales campaigns). Advantage+ campaign budget is on by default for sales, leads, and app promotion campaigns (Advantage+ campaign budget). We use that automation for distribution and keep control over what Meta can't decide well: the offer,
the creative, and the conversion event. The same unification shows up on the developer side: Meta's
Marketing API documentation says that from v25.0 the separate Advantage+ shopping campaign API is replaced
by regular campaigns that use Advantage+ audience, budget, and placements, with the campaign's Advantage+
status reported in an advantage_state field (Meta for Developers). Any reporting or automation scripts built on the old API need updating.
Know which settings turn Advantage+ off
In the Advantage+ campaign experience, some audience and placement choices switch Advantage+ off for that
campaign (Meta Business Help). Multiple ad sets without campaign budget, excluded placements, or opting out of mobile or desktop all
switch it off, while ad account-level controls don't. Excluded placements can be given limited spend of up
to 5% of budget each, and the old existing-customer budget cap is gone. We make those trade-offs on purpose,
for example a hard age or location limit required by regulation, rather than by accident.
Test concepts, not tweaks
Each new round tests a different idea (a new angle, new proof, a new format), not a new button color.
Winners get more variants. Losers get written up so the same idea doesn't come back three months later.
Report against the backend
Weekly: spend, Meta-reported results, backend results, and the gap between them. Monthly: blended
customer-acquisition cost across Meta and Google, so budget goes where it earns the most.
Common Meta ads mistakes John fixes
Pixel and CAPI double-counting purchases because event IDs are missing or generated
differently on each side.
Low Event Match Quality from sending only an IP address and user agent server-side, with no
hashed email, phone, or fbc.
Optimizing lead campaigns to raw form submissions, which teaches Meta to find people who fill
in forms, not people who buy.
Too many small ad sets splitting budget so none of them gets out of learning.
Creative fatigue treated as an audience problem. Frequency climbs, CTR falls, and the fix is
new concepts, not new targeting.
Unhashed contact data. Meta's systems are designed not to accept unhashed contact information
except where noted, and the Meta Business SDK hashes automatically (customer information parameters).
How the creative system works
On Meta, the targeting is mostly automated, so creative is where you still have real control. John's system
treats creative as a pipeline with a backlog, not a monthly scramble.
Concept backlog. Each concept is one sentence: the problem it speaks to, the proof it uses
(review, demo, number, founder), the offer, and the format (Reel, static, carousel). The backlog is ranked by
what we expect to learn, not by what's easiest to produce.
Variants per concept. Each concept ships with a few hooks (first line or first three seconds)
and placement-ready versions for Feed, Stories, and Reels, so a promising idea gets a fair test.
A fixed testing cadence. New concepts go out on a schedule, so fatigue never catches the
account with nothing ready.
A written log of winners and losers. What won, against what, on which metric, and our best
guess why. It's the institutional memory most accounts lack.
Pre-flight checks. Copy variants come out of the
Social Media Ad Builder, which writes to each platform's character
limits, and visuals go through the Creative Asset Validator before
they reach Ads Manager.
Lead generation on Meta: forms vs. website
Meta's instant forms make submitting easy, and that's the problem. Low friction attracts low intent. John's
approach depends on what happens after the lead:
Sales calls every lead fast: instant forms with a qualifying question or two, and qualified
outcomes sent back from the CRM through the Conversions API.
Sales is capacity-constrained: send traffic to a website form with stronger qualification,
tracked by Pixel and CAPI with deduplication.
Either way: the optimization event should eventually be a qualified lead, not a submission.
That needs enough qualified volume to optimize, so lead quality and lead volume have to be planned together.
Meta and Google, managed with one standard
Most of our Meta clients also run Google. The value of one operator across both is consistency: the same
definition of a conversion, the same backend reconciliation, and budget decisions based on blended
customer-acquisition cost rather than each platform's self-reported numbers. Google search captures demand that
already exists. Meta creates demand. Judging both on last-click ROAS undervalues Meta and overvalues brand
search. We report both views.
Measuring Meta honestly: lift beats attribution
Meta's reported results tell you what its attribution model credits, not what the ads caused. The best public
evidence on the gap comes from Meta's own experiments. A study of large randomized lift tests at Facebook found
that common observational methods often misstate the true effect, sometimes badly (Gordon et al., Marketing Science). A follow-up across 663 Facebook experiments concluded that, even with rich user-level data, the researchers
were "unable to reliably estimate an ad campaign's causal effect" without an experiment (Gordon, Moakler & Zettelmeyer).
What that means in practice:
Reconcile weekly. Meta-reported purchases or leads next to backend orders or CRM records,
with the gap tracked over time. A widening gap is a measurement problem to investigate, not a win.
Run lift tests on big decisions. Before doubling Meta spend or cutting it, test it. Where
user-level lift tests aren't available, Meta's open-source
GeoLift measures
incremental lift across matched regions.
Model the mix once you have history. Meta's open-source
Robyn marketing mix
model estimates Meta's contribution alongside Google and offline channels, and its results can be calibrated
with lift tests.
Feed the system variety. Meta built its Andromeda retrieval engine to scale ad selection to a
much larger volume of ad creatives (Engineering at Meta), which is one more reason the creative backlog above matters more than audience tweaks.
Pricing and engagement
Meta ads management is a flat monthly fee quoted after we've audited the ad account and the signal setup. The
number depends on creative volume and how many offers or markets are involved. Per the
pricing page, nothing at Ahmeego is billed as a percentage of spend and there are no
long contracts. CAPI and signal fixes can also be scoped as a one-time project.
Platforms we work in
Meta campaigns depend on Meta's own tools plus the server and commerce stack behind them. Official product pages
below.
Do I need the Conversions API if I already have the Meta Pixel?
Meta recommends running both. The Conversions API sends events from your server, website platform, or CRM, so
it can include events the browser misses, such as offline and CRM outcomes. If you send the same event both
ways, it must be deduplicated.
How does Meta deduplicate Pixel and CAPI events?
The recommended method is matching event_id (sent as eventID from the Pixel) and matching event names. Meta
discards later duplicates received within 48 hours of the first event with that ID.
What is a good Event Match Quality score?
Meta scores Event Match Quality from 0 to 10 based on the customer information you send and the share of
events matched to Meta accounts, using the last 48 hours of data. Higher is better. Meta ranks email and click
ID as the highest-priority parameters, so send those first, normalized and hashed correctly, then add phone,
external ID, and browser ID where you legitimately have them.
Should I use Advantage+ sales campaigns?
For most ecommerce prospecting, yes. Meta describes them as its most efficient option for online sales when
Advantage+ audience, placements, and budget are on. They depend on a clean purchase signal and a steady supply
of new creative.
Why are my Meta leads low quality?
Usually because the campaign optimizes toward form submissions. Sending qualified-lead events from your CRM
back through the Conversions API lets you optimize toward the leads sales actually wants.
Do you manage Instagram ads separately from Facebook?
They run from the same Meta Ads Manager account. Placement choices and creative formats differ (Reels,
Stories, Feed), so creative is built for each placement even when campaigns are shared.
Talk to John about Meta ads
Tell John what you sell, your monthly Meta spend, and whether CAPI is set up. He'll reply with a written read on
signal and creative.
John, Kristy, or Sandeep will reply.One of the three of us will respond personally within 1 business day. No SDR queue.
Message received.
One of us will reply directly within one business day. While you wait, run a free
Buddy audit on your account.
Top 25 references
The primary sources, standards, research, and tools we rely on for this work. Every link was checked on
2026-10-11. We aren't affiliated with these publishers unless noted.
Official documentation
Meta Business SDK for Python— Meta (GitHub) Meta's official SDK for the Marketing API and Conversions API, which hashes customer data
automatically.
Meta Business SDK for Node.js— Meta (GitHub) Meta's official JavaScript SDK, the usual choice for server-side CAPI from a web stack.
FIPS 180-4: Secure Hash Standard— NIST The specification for SHA-256, the hash Google, Meta, and Microsoft all require for emails and phone
numbers sent with conversions.
Guidelines 05/2020 on consent under Regulation 2016/679— European Data Protection Board The EU regulators' definition of valid consent under GDPR: freely given, specific, informed,
unambiguous, and as easy to withdraw as to give.
Cookies and similar technologies— UK Information Commissioner's Office The UK regulator's PECR guidance on when analytics and advertising cookies need consent.
Global Privacy Control— Global Privacy Control The browser opt-out signal several US state privacy laws require advertisers to honor.
Facebook Ads Benchmarks— WordStream by LocaliQ CTR, CPC, conversion rate, and cost-per-lead benchmarks for Meta lead and traffic campaigns by
industry.
The Long and the Short of It— IPA (Binet & Field) The effectiveness study on balancing brand building and activation, useful when judging Meta on last-click
ROAS alone.
Leading tools
Conversions API Tag for Google Tag Manager— Meta (facebookincubator on GitHub) Meta's official server-side GTM template for sending Conversions API events, maintained by Meta.
Robyn— Meta Open Source (GitHub) Meta's open-source marketing mix modeling package for measuring Meta against other channels.
GeoLift— Meta Open Source Meta's open-source geo-experiment toolkit for measuring incremental lift without user-level
tracking.
Pixels and customer events— Shopify Help Center How Shopify's customer events and web pixels work, which decides where Meta Pixel events fire on
Shopify.
Tag Manager Template Gallery— Google Where community and vendor server-side templates, including Conversions API tags, are published.
Server-Side Tagging In Google Tag Manager— Simo Ahava The canonical deep dive on how server containers, clients, and tags work, from the best-known GTM
practitioner.
Communities & courses
Meta Blueprint— Meta Meta's free training and certification catalog for Ads Manager, measurement, and creative.
r/FacebookAds— Reddit The largest Meta advertiser forum, where delivery bugs and policy changes surface quickly.
#measure Slack community— Measure Chat A long-running Slack community of analytics and tag management practitioners, good for GA4 and sGTM edge
cases.
AI disclosure: This page was drafted with AI assistance and edited by a human. Platform rules and
limits are cited to official documentation as checked on 2026-10-11; Google, Microsoft, and Meta change these
often, so confirm against the linked source before acting. Brand names mentioned in John's background are past
engagements listed on the about page; no current endorsement is implied.
Check your Pixel and consent setup for free.
The Marketing Analytics Auditor detects Meta Pixel, consent mode, and data layer issues in your browser.
Meta Ads Manager
Facebook
Instagram
Google Tag Manager
Stape
Shopify
HubSpot
Looker Studio