Meta Ads

Meta Pixel and Conversions API: to make events happen in full

The Meta Pixel and Conversions API settings are two halves of the same measurement: the browser sends the event from the buyer's phone, the server sends the event from your end, and both must share the same event ID. Without it, the purchase is counted twice, and the cabinet shows more orders than your accounting department can see. A detail that often causes the server channel to perform worse than expected: an event from a server without _fbp and _fbc cookies captured in the browser comes with almost no data to match - there is nothing for the system to glue it to a person.

See how it works

Price: after a free audit
Guarantee: 30 days after project sign-off
Two channels of one event: browser pixel and server Conversions API; their common event identifier brings them together

Price: after a free audit
Guarantee: 30; days after project sign-off
Two channels of one event: browser pixel and server Conversions API; their common event identifier brings them together
Term of works: 3-12; working days - depends on the method of transmission of server events
Before the estimate: Free Check What's Transferring Now: 2-3 business days
A typical find: in the self-defense store, the Meta pixel was the only counter on the site - measurement 07/31/2026
What we measure after implementation: the share of events from the server channel, the assessment of the quality of the mapping, the discrepancy with the accounting system
What we do not promise: the growth of numbers in the office: after deduplication, they often fall, because they stop counting purchases twice

Process steps

Transparent stages with approval at every step

Total duration:3–12 days

Free event transmission test
2-3 working days, to estimate
We see how many pixels are on the page, what events are received, whether there is a server channel and whether the purchase is not counted twice. The output is a map of events and the recommended transfer method for your platform.
Browser Events: Revision and Full Chain
1-3 working days
We remove duplicates and redundant sources, select missing events, add product parameters, amount and currency. Here we record how the event identifier is generated.
Server channel and deduplication
1-5 working days
We raise the transfer through the Conversions API in the chosen way, transfer _fbp and _fbc from the browser, combine both channels by a common identifier. First, we enable one event — a purchase.
Test events, reconciliation and document
1-4 working days
We run the real order from the cart to confirmation, compare purchases in the office with orders in the accounting system, describe the scheme of events and transfer access.
A week of observing the quality of the mapping
7 calendar days, does not take working days
The evaluation of the quality of the mapping in the event manager is not immediately typed. We watch it on live traffic and adjust the parameters if the server events are worse than the browser events.

Technologies & integrations

What we build on and what it connects to

Stack

Meta Pixel is a browser channel. It is installed quickly, but some of the events will never be seen: blockers and browser restrictions on cookies
Conversions API is a server channel. Closes the browser loopholes, but without _fbp and _fbc removed in the browser, the mapping quality drops
The event manager and test events are the only place where you can see what actually arrived. The assessment of the quality of the mapping there is approximate, it is not a metric of accuracy
Google Tag Manager — collects browser events without site release. I am very reluctant to buy from him: the thank you page is not proof of payment
The tag server container is one channel for several systems at once. This is separate hosting that someone has to pay for and update
The backend handler is the most accurate source: the event fires when the order is actually created. Code access and developer queue required

Integrations

Meta Ads Manager
the Meta event manager
Google Tag Manager
server tag container
CRM or accounting system
consent banner

What's included

Complete list of work and what you get as a result

Revision of the pixel: one identifier per site instead of two or three left over from different contractors — otherwise events are shared between offices
A complete chain of standard events — viewing the product, shopping cart, starting checkout, purchase: it is clear at which step the buyer gets lost
Product parameters, amount and currency in the purchase event - without them, the report remains the quantity, but not the return on advertising
Server transmission through the Conversions API on your part: the event occurs even when the browser did not send it
Common event ID for both channels and push _fbp and _fbc to the server - the purchase counts once and has something to match
Consent banner event matching: Human opt-out stops transmission, not just cookie recording
Test events and running a real order from cart to confirmation — we check what comes, not what should come
Reconciliation of purchases in the office with orders in your accounting system for the same period
Checking the Mapping Quality Score in the Event Manager after a week of work, when the statistics are collected
Schema of events in one document: names, parameters, where each value comes from - to be maintained without us
Guarantee of 30 calendar days for completed works

When this service isn't right

What's not included — so there are no surprises at delivery

Conducting advertising campaigns
Transfer of personal data without your written consent and legal basis
Bypassing the user's opt-out of tracking
Setting up Google analytics is a related service
Legalization of the privacy policy

Who it's for

Situations where this service delivers results

Scenario 1 of 5

You advertise in Meta and have never reconciled your account with the accounting system

The cheapest check takes five minutes: purchases in the office for a week against orders in your system for the same week. If the cabinet shows twice as much, this is not successful management, but one event that comes through two channels without a common identifier. Campaigns learn from an inflated signal.

We'll review your situation in a free audit

Only browser pixel vs pixel with server feed

How this option differs from the alternative

	Browser pixel only	Our approach
What about the blocker event	there is no event at all, there is no order for the cabinet	the browser one did not go, the server one went — the purchase is counted once
How do you know that the order is genuine?	the event is sent by a thank you page and can be reloaded five times	the event is sent by the backend when the order is created
Risk of double accounting	no: one channel, instead, there is a lack of data	is — that's why a shared event identifier is required, not preferred
What is required of you	access to the site or to the tag manager	backend or server container access and options decisions
How much does it cost to support	nothing more than the site itself	server container — separate hosting; handler — developer time on checkout changes

Free audit

Free test of event transmission in Meta

Half of the problem with Meta ads isn't the campaigns, it's that the system doesn't see what happened after the click. The check shows which events arrive, which are lost, and which are counted twice.

What we measure

Is the pixel standing and is it aloneTwo pixels per page is not uncommon after a contractor change. In the sample we measured, there were sites where the Meta Pixel was the only counter at all, without any other analytics.
Complete chain of eventsViewing the product, adding it to the cart, starting the checkout, purchasing. Most often, it is the middle that is missing, and the funnel becomes unusable for analysis.
Transfer of the cost of the orderWithout the amount and currency in the purchase event, it is impossible to calculate the return on advertising - only the quantity remains.
Availability of a server channelAre events being sent from your end, not just from the browser. Browser events are partially blocked due to blockers and privacy settings.
DeduplicationIf the same purchase is sent by both the browser and the server without a common event ID, it will be counted twice. This is the quietest of all defects: the numbers keep getting better.
Data collection consent statusIf the site has a consent banner, the events must obey the user's choice. We are checking if this is the case now.

What you get

Map of events: what is being transmitted now, from where and with what parameters.
List of lost and duplicated events.
The recommended way to pass server events is specific to your platform.
Conversation for 30 minutes on the document.

Timeline: 2-3 working days

Why is it free

Because double accounting makes reports more beautiful, and it is almost never looked for by themselves. It's cheaper to show it for free than to explain later why the figures in the office are twice the real orders.

What's next

We provide an estimate for the implementation of the selected transmission method, deduplication and data quality control.

Short form: your contact and site URL

Did not find your case?

Describe how it works on your side — we will tell you whether “Meta Pixel and Conversions API” fits and what it means in your situation. No brief and no call: one question, one answer.

Contract and paperwork

We work officially

Contract, act and invoice — for every project, not just large ones.

Trusted by6 brands

Terms fixed in writing8 points

Contract, act and 30-day warranty
Every project gets a written contract: scope, deadlines, amount, acceptance procedure. After delivery — act and invoice, then 30 calendar days of warranty.
Sole proprietor & bank transfer
The contractor is a registered sole proprietor. Payment by invoice with closing documents.
Rights & access — yours
Code, design and materials transfer to you after full payment. Domain, hosting, repository and analytics are registered to you.
Client portal instead of email chains
During the project you get access to a portal: contracts, invoices, acts and project status in one place.
Sites in nine countries
Our sites run in nine countries: besides Ukraine — Poland, Germany, Austria, England, Norway, Bulgaria, Moldova and Spain.
Verifiable numbers
Every case in the portfolio comes with a link to a live site and a technical measurement.
Audit first, then pricing
There is no price list on the site intentionally: the scope of the same work differs multiples between clients.
We say "no" when unsure
If the task isn't ours or the deadline is unrealistic — we tell you upfront.

Contract, act and 30-day warranty
Every project gets a written contract: scope, deadlines, amount, acceptance procedure. After delivery — act and invoice, then 30 calendar days of warranty.
Sole proprietor & bank transfer
The contractor is a registered sole proprietor. Payment by invoice with closing documents.
Rights & access — yours
Code, design and materials transfer to you after full payment. Domain, hosting, repository and analytics are registered to you.
Client portal instead of email chains
During the project you get access to a portal: contracts, invoices, acts and project status in one place.
Sites in nine countries
Our sites run in nine countries: besides Ukraine — Poland, Germany, Austria, England, Norway, Bulgaria, Moldova and Spain.
Verifiable numbers
Every case in the portfolio comes with a link to a live site and a technical measurement.
Audit first, then pricing
There is no price list on the site intentionally: the scope of the same work differs multiples between clients.
We say "no" when unsure
If the task isn't ours or the deadline is unrealistic — we tell you upfront.

We sign NDAs on request. After completing the work, we delete our access to your services ourselves.

What affects the price

Why two seemingly identical tasks are priced differently

Method of transmitting server eventsReady integration of the platform — a few days. The tag server container is also separate hosting that someone has to pay for and update. Own processor on the backend gives the most accurate data and takes the most time. This is where the difference between the lower and upper limits lies.
How many events are we recording?One purchase is one ID and one reconciliation. The complete chain from viewing to checkout is four events, each with its own product parameters, and each should be checked separately in both channels.
What is already on the siteIt is faster to set up a clean site than to disassemble the legacy. Two pixels, events from the topic and from the tag manager at the same time, a module that sends its own — analysis of someone else's setting is a separate line of the estimate.
There is a consent banner or notIf not, the events just go on. If there is, both channels must be submitted to the person's choice and two states, consent and refusal, must be checked. Testing on this is doubled.
Whose turn is it on the backend?We make edits in the tag manager ourselves. The site-side processor is contributed by whoever has access to the code: if it's your developer, the deadline starts to depend on his queue, not ours.

Cases

Tasks and results in numbers — all metrics measured by us

online retail underwear store, over 110,000 product items

Task: Check if the events behind Meta remarketing can be trusted.
Solution: Analysis of counters in the markup and selection of 150 random product addresses of the site map.
Result: The counters are all there: the tag manager, GA4, Google Ads, and the remarketing module gives the product ID to several systems at once, including Facebook. The defect was not found in the counters: out of 150 random product addresses, 50 (33%) return 301, and all lead to a different position — a different size or color. In the catalog of 115,456 items, this is about 37,000 addresses where the browsing event indicates the wrong product that the person opened. Measurement 01.08.2026.

Elektroshokery

a specialized online store of self-defense equipment

Task: To understand how to measure advertising, if there are numbers in the office, but there is nothing to compare them with.
Solution: Analysis of all counters on the pages and checking of the site map.
Result: The Meta Pixel is in place and loading, and there's nothing else on the site: no mention of a tag manager or Google Analytics. The catalog is small - 68 addresses in the site map, 48 of them are commercial, so it was possible to check each one. The accounting system remains the only independent source for reconciliation. Measured on 07/31/2026.

online store of natural cosmetics on beekeeping products

Task: Check whether the counters that count advertising are working.
Solution: Parsing counter identifiers in HTML and comparing their types.
Result: Meta Pixel, Google Ads and Tag Manager are up and running. Analytics - no: the Universal Analytics counter lives on the site, which Google disabled on July 1, 2023, and the GA4 identifier is not in the markup at all. Data was not collected for three years, and from the outside it looked like customized analytics. The first response is 126.3 ms. Measured on 07/31/2026.

plastic surgery clinic, site on JS-framework

Task: Find out why configured events are not appearing in reports.
Solution: Reading the markup separately for the browser and for the bot, parsing the inline snippet of tags and consent mode.
Result: The tag container didn't load at all: in the inline snippet, the exit condition compared the id with itself, so the return always worked - and the id field contained the GA4 code, not the container. The default consent mode is disabled. The site gives the browser a shell of 3.0 KB, the search bot — 126 KB of pre-rendered HTML. From the outside, everything looked set. Measured on 07/31/2026.

What we need from you

We can't start without this — best to prepare in advance

Access to the business account and event manager - without it you can't see what's coming now.
Access to the site or to the tag manager to implement the browser part.
What parameters you are willing to share and the legal basis for doing so is your decision, not ours.
Access to the server part if we choose direct transmission from the backend.
A description of what is considered a successful order in your system: payment, manager confirmation, or shipment.
The existing consent banner and the rules of its operation, if it is already there.

If something is missing — let us know, we'll help you gather it or do it as a separate task.

FAQ

Most frequently asked questions — with concrete answers

Why server events if the pixel is still there?

The browser event goes from the buyer's phone and does not arrive in at least three cases: an ad blocker, browser restrictions on third-party cookies, a broken tab on a weak connection. The server drives from your side and does not depend on it. This is not a pixel swap: both channels send the same event, so a shared ID is required. There is a second reason, which is mentioned less often: the server knows that the order has really been created, and the thank you page only knows that the browser has opened it - and it can be opened five times in a row.

What is deduplication and why is it important?

Meta glues the browser event and the server event by the event name plus event ID pair. The ID must be generated once — per order — and go into both channels. The most frequent error looks different than expected: the identifier is formally there, but the browser and the server each generate their own, there is nothing to glue, and each purchase is counted twice. Our recommendation is simple: take the order number from your system as a basis. Then the identifier is the same by definition, and it is visible in both logs when you have to sort it out.

How to quickly understand that now the numbers are wrong?

Take purchases in the Meta cabinet for a week and orders in the accounting system for the same week. The difference in times towards the office is almost always double accounting. The difference towards the accounting system is undelivered events. There will never be an exact match: the attribution windows are shifted, some of the orders do not come from advertising. But the order of values must converge, and if they don't, it's not a question of campaigns.

Why does the event have to carry the correct product ID?

Dynamic remarketing is based on it: the view event must point to the same position as in the product feed. In the underwear store, we took 150 random product addresses from the sitemap — 50 of them (33%) returned a 301 to a different position, size, or color. There are about 37,000 addresses in the catalog of 115,456 items. Formally, events are sent there, in fact, some of them tell Meta about a product that a person has not looked at. That's why we look at redirects, not just code, before setting events.

Will the consent banner reduce data volume?

Yes, and this is the expected effect, not a breakdown. Some people will refuse, their events will not go - neither by the browser, nor by the server. We warn about the decline of indicators in the first weeks, because it is expensive to confuse it with a drop in sales. Separately, we check whether what is already working at all works: in the clinic from our sample, the consent mode was in the "disallowed" state by default, and the inline snippet of the tag manager was self-blocking - the exit condition compared the identifier with itself. The container was not loaded at all, and from the outside it looked set up.

We have a JS-framework store, events do not trigger on transitions

Recognizable story: The page doesn't reload, so the standard pixel insert registers only the first screen. Events should be posted for changing the route, and it is better to take the purchase to the server altogether - it is already known there. A visual example from our measurements: at the clinic, the browser receives a shell of 3.0 KB, and all the content is finished with a script. Anything that relies on loading a document in such an assembly will fire once per visit.

Which parameters are passable and which are not?

Technically, the system takes a number of parameters to match a person, and the more they are, the higher the match quality score. You can legally transfer them only if there is a legal basis and in a hashed form, and the decision is yours. We adjust exactly what is agreed upon in writing and record it in the document. There will be no "transfer everything to make it work better" advice from us: in the event of an inspection, you will be responsible for it.

How long does it last and what will be seen at the end?

3-12 business days after free inspection. Ready integration of the platform takes three to four days. A server-side tag container or a custom backend processor is up to two weeks: there you need test events, a reconciliation with the accounting system, and a week of monitoring the quality of the mapping. At the end, you have three things: a scheme of events in a document, a reconciliation of the cabinet with the accounting system for the same period, and an understandable reason for the discrepancy, if it remained.

Submit your site address and access to the event manager.

The response is a map of what is currently being streamed, a list of lost and duplicated events, and a recommended server transfer method specific to your platform. If you have already compiled everything correctly, you will hear it in the first email and without an estimate.

View cases

Reply within 2 hours
No commitment
We work under a contract

There is no price list on the site on purpose: the same work differs several times over between two clients, and a “from” figure explains nothing in that case. First a free audit — we count your pages, duplicates and speed — then we name the sum and the deadline and fix both in the contract.

Meta Pixel and Conversions API: to make events happen in full

Transparent stages with approval at every step

Free event transmission test

Browser Events: Revision and Full Chain

Server channel and deduplication

Test events, reconciliation and document

A week of observing the quality of the mapping