Meta Pixel and Conversions API setup – measure your ad results properly

Why a Meta Pixel alone is no longer enough

The Meta Pixel is a tag on your site that sends events such as "viewed a product", "added to cart" or "purchased" from the visitor's browser to Meta. For years that covered almost everything. Then iOS 14.5 introduced App Tracking Transparency (ATT) in 2021, and browser-side tracking started losing data.

The main reasons events go missing today:

• iOS opt-outs: many people decline tracking inside the Facebook and Instagram apps
• Browser limits: Safari's ITP and similar features shorten how long cookies last
• Ad blockers: extensions stop the pixel tag from loading at all
• Early exits: if the order confirmation page never loads, the purchase event is never sent

Missing events make your ads look less profitable than they are and give Meta's algorithm less to learn from. A quick first check: compare the number of orders in your shop admin with the purchases shown in Events Manager for the same period.

What the Conversions API does and how it pairs with the Pixel

The Conversions API sends events to Meta directly from your server or e-commerce platform. Because it skips the browser, ad blockers and cookie limits affect it far less. Meta itself recommends running the Pixel and the Conversions API together.

• Pixel: fast, detailed browser-side signals such as page views and product views
• Conversions API: the events you cannot afford to lose – purchases, leads – sent server-side
• Deduplication: both send the same event name and event ID, so one purchase is counted once
• Customer matching: email or phone, hashed with SHA-256, helps Meta link the event to the person who saw the ad

Matching quality appears as the Event Match Quality score in Events Manager. Sending more customer parameters usually raises it, but your privacy policy should explain this use of data. In Japan, the external transmission rules under the Telecommunications Business Act may also apply, so check the current guidance and update your notices.

Step-by-step Meta Pixel and Conversions API setup

Following this order keeps gaps to a minimum:

• Check your business portfolio: the ad account, pixel (dataset) and domain should belong to your company
• Verify your domain: confirm ownership in business settings so you control the events for it
• Choose events: pick the standard events you need – PageView, ViewContent, AddToCart, InitiateCheckout, Purchase, Lead
• Install the Pixel: through your platform's integration or Google Tag Manager, on every page
• Connect the Conversions API: an official integration such as Shopify's, a WordPress plugin, server-side GTM or Meta's Conversions API Gateway – whichever fits your setup
• Test: use Test Events in Events Manager to confirm events arrive from both browser and server and are deduplicated

Always include value and currency (JPY) in purchase events, or you cannot compare return on ad spend. During testing, place a real order or send a real form once and check that what Meta receives matches your admin panel.

Setup notes by platform

How much work the Conversions API takes depends heavily on what your site runs on.

• Shopify: the official Facebook & Instagram app connects the Pixel and Conversions API in one go, with a choice of data-sharing level, and syncs your product catalog
• WordPress and WooCommerce: Meta's official plugin connects both, but some themes and plugins fire purchases twice, so testing is essential
• BASE and similar services: you work within the built-in integrations; server-side fine-tuning may be limited, so confirm early what can be tracked
• Custom-built sites: server-side GTM or a direct integration gives full control – just decide who will maintain it

For the wider picture on Shopify, including Instagram Shopping and catalogs, see Shopify and Instagram integration.

Common Meta Pixel setup mistakes

Tracking problems often go unnoticed until the ad numbers stop making sense. Check these right after setup:

• The same pixel is installed through the theme code, an app and a tag manager, so purchases count double
• Pixel and Conversions API events use different event IDs, so deduplication fails
• The purchase event fires on pages other than order confirmation and inflates results
• The pixel sits in a former agency's or employee's personal account and cannot be handed over
• A cookie consent banner blocks the tags even after visitors accept

Keep the pixel and ad account in your company's own business portfolio and give outside partners access as needed. That way your tracking data stays with you whoever manages it.

How UNANOBO handles tracking: planned together with your site

We prefer to design the site's conversion paths and its events together, so tracking fits the site from the start. Before you commit, UNANOBO builds a free demo of a site or landing page around your brand, along with a plan showing which buttons and screens trigger which events. After you have seen the demo, you get the scope, the steps and an estimate.

The process is free demo, feedback, launch, growth. The founder handles every project personally, so one contact covers everything from installing the pixel to running ads and improving results after launch. Everything runs by message, in Japanese or English. Once tracking is in place, Meta Ads management explains how campaigns are run and improved.