Why the Pixel alone is no longer enough
The Pixel is a piece of JavaScript in the browser. It is blocked by ad blockers, limited by iOS privacy settings and by Safari and Firefox cookie rules, and it disappears when a page fails to load fully on a slow connection, which in Nepal is common. Meta’s delivery system optimizes toward the events it can see, so an account that loses a third of its purchase or lead events is optimizing on a third less information and reporting a third less than it earned. The Conversions API sends the same events from your server, where none of that applies. Running both, correctly deduplicated, is the baseline for every account I manage.
What gets set up
Pixel in the browser
Installed through Google Tag Manager or the platform’s native integration, with standard events (Lead, Contact, Purchase, AddToCart, InitiateCheckout, Schedule, CompleteRegistration) fired on real completions, not page loads or button clicks. Custom events are added where your funnel has a step Meta has no name for. Advanced matching passes hashed email and phone from forms so more events match a Meta profile.
Conversions API from the server
Depending on your platform: the native Shopify or WooCommerce integration, a server-side Tag Manager container, or a partner gateway. Each event carries the same event name and a shared event ID as its Pixel twin, plus the user parameters Meta uses to match: email, phone, name, city, IP address, browser agent, and the fbp and fbc cookies.
Deduplication
When browser and server both send a Purchase for the same order, Meta must count one. Deduplication works on matching event name plus event ID (or external ID). I test it by firing an event and confirming in Events Manager that it is received twice and counted once. Setups that skip this double-count conversions and make the account look better than it is.
Event match quality
Events Manager scores each event out of ten by how many identifying parameters arrive with it. Low scores mean fewer events attributed and worse optimization. I raise the score by passing hashed email and phone, keeping the fbp and fbc cookies alive across the funnel, and sending IP and user agent from the server. The target is a high score on the events you bid on, not a perfect score on page views.
Domain verification and aggregated event configuration
Your domain is verified in Business Manager so events from it are trusted and can be configured and prioritized. Events used for optimization are set up and ordered so the ones that matter most are the ones Meta reports when browser signals are limited.
Test events and monitoring
Every event is fired through the Test Events tool with a test code, checked for parameters and deduplication, then monitored in Events Manager’s diagnostics for the first weeks. The setup document lists each event, where it fires, and what a correct test looks like.
What breaks in Nepal, and how I handle it
- Server-side hosting needs a card. A server-side Tag Manager container runs on a cloud service billed to an international card, which many Nepali businesses do not have. Options are a card the business does have, a hosting partner that invoices locally, or the platform’s native integration where one exists.
- Business verification. Meta asks for business verification for certain features, categories and spend levels. Nepali businesses usually verify with a company registration certificate, PAN or VAT document and a utility bill or bank statement showing the business name and address, and the process can take several attempts if the documents do not match exactly. Business Manager shows the document list it currently accepts when you start verification.
- Leads arrive on WhatsApp, not through forms. The click to WhatsApp is tracked as a Contact or Lead event, and conversation outcomes are logged so the campaign can be judged on conversations that became customers.
- Payment gateways that redirect off-site. Purchase events are fired from the return page with the order ID and deduplicated on it, or sent from the server when the gateway confirms payment.
- Several old Pixels in the theme. Everything is consolidated into one Pixel and one container; the old code is removed, not just disabled.
Process and what you receive
- Map every lead and purchase path, including chat and phone.
- Audit existing Pixel, events and Events Manager diagnostics.
- Install or rebuild the Pixel through GTM or the native integration; add advanced matching.
- Implement the Conversions API with shared event IDs; verify deduplication.
- Verify the domain and configure event priorities; complete business verification if required.
- Test every event, document the setup, monitor for two weeks.
You receive a working, documented setup in your own Business Manager. Tracking is included in Facebook Ads management services and the Facebook Ads setup service, and available standalone after a Facebook Ads audit finds gaps. The Google side of the same measurement layer is Google Ads conversion tracking setup, and both feed the reporting described under analytics and tracking.
Pricing
Standalone Pixel and Conversions API setup is quoted from the platform, the number of events and whether server-side hosting is needed; see the Meta Ads packages and pricing page. The free Meta Ads audit includes a check of your current events and match quality. All Meta Ads services are on the hub.