Meta Pixel and Conversions API for small shops

In the first lesson you saw that Meta shows your ad to more people like the ones who already acted. For a sales campaign, "acted" means "bought". If Meta cannot see your sales, it cannot learn who your buyers are. It also cannot tell you what each sale cost.

Two tools let Meta see your sales. This lesson explains both, then shows the setup for the way you sell.

What the Pixel and the Conversions API are

The Meta Pixel is a small piece of code on your website. When a visitor views a product, adds to cart or pays, it tells Meta. These are called events. The Pixel now sits inside a dataset in Meta's Events Manager, with the same ID number it always had.

The Conversions API sends the same events from your shop's server instead of the visitor's browser. Browsers lose events. On iPhones, many people decline tracking in apps: AppsFlyer found only about half of users worldwide allow it. A server-side feed fills the gap.

Run both. Each event carries the same event ID from both sides, and Meta keeps one copy. Meta reports that advertisers with a Conversions API setup for web events saw on average 17.8% lower cost per result. Treat that as a guide, not a promise: it is Meta's own figure.

Why sales campaigns need them

1. Meta optimises for what it can see. A campaign set to find purchases needs purchase events to learn from. Lessons 1 and 2 showed that the learning phase wants about 50 of them in 7 days.
2. Your cost per sale is only as true as your tracking. Missed events make good ads look bad, and you may stop the wrong ad.
3. Retargeting needs events. "People who added to cart but did not buy" only exists if the Pixel recorded the add to cart.

Set it up for the way you sell

Shopify

1. In Shopify, install the Facebook & Instagram app by Meta.
2. Connect the business portfolio, ad account and Page from the last lesson, then pick or create your pixel.
3. Under data sharing, choose Maximum. Shopify then sends events through both the Pixel and the Conversions API.

WooCommerce

1. In Meta Events Manager, open Partner Integrations and pick WooCommerce.
2. Follow the steps to connect your shop. The connector adds the Pixel and the standard shop events, and it can also send events through the Conversions API. Turn that on.
3. Check that the dataset ID it shows matches the one in Events Manager.
4. Run the test at the end of this lesson to check that purchases arrive from both the browser and the server.

A custom website

Your developer adds the Pixel, then sends the Conversions API events from the server with the same event ID. The Conversions API setup guide has the details to hand them.

WhatsApp only, no website

You do not need a Pixel to start. Run ads that open a WhatsApp chat. Ads Manager then reports the cost per messaging conversation started.

The catch: the sale happens inside the chat, where Meta cannot see it. So you count it yourself.

1. In the WhatsApp Business app, set up two labels: From ad and Paid. Add any that are missing.
2. Give every chat that came from an ad the From ad label. When the customer pays, add Paid.
3. Once a week, count the chats that have both labels. Divide what the ads spent by that number. That is your real cost per sale.

Meta says click-to-WhatsApp ads can also be measured with the Pixel, the Conversions API or offline conversions. That usually needs the WhatsApp Business API through a provider, which is worth it once chat volume grows.

Shopee or Lazada only

You cannot add the Pixel to a marketplace listing. Ads to a listing usually run on the Traffic objective, and you check sales in your seller centre. The guide for Shopee sellers covers this route.

Check that it works

1. In Events Manager, open Test Events for your dataset.
2. Open your shop in another tab and place a real test order.
3. Look for one Purchase with a value and currency. You should see it arrive from both the browser and the server, counted once.

If a purchase shows twice, the event IDs do not match. Fix that before any campaign optimises for it. The guide on Pixel and Conversions API deduplication walks through it.

Ask for consent

Under Malaysia's Personal Data Protection Act 2010, a site that sends visitor data to Meta is processing personal data. Consent is the default rule, and your notice must be in Malay and English. Read PDPA and the Meta Pixel before you go live.

A worked example: the Ipoh bakery grows

Say the Ipoh brownie bakery still takes local orders on WhatsApp. For Deepavali, it opens a small Shopify shop to send gift boxes across Malaysia.

• Local orders: the WhatsApp labels method. Each Monday the owner counts chats labelled From ad and Paid, and works out the cost per sale.
• Gift boxes: the Facebook & Instagram app on Shopify, with data sharing on Maximum. One RM 45 test order shows up in Test Events, counted once, with the value in MYR.

Now the gift box campaign can optimise for purchases, and the reported cost per sale can be trusted.

Where this shows up in AdPlay.ai

When you connect Meta in AdPlay.ai and pick Purchases as your goal, the sales it counts are the purchases Meta records. No events, no sales to show. And when you build a sales ad set in Launch by hand, setting Optimization Goal to Conversions asks for a Facebook Pixel and a Conversion Event, such as Purchase. You cannot launch it without both. The launch guide covers the rest.

Checklist

• My website has the Pixel and the Conversions API on, through my shop platform.
• A test order shows one Purchase in Test Events, with value and currency.
• My site asks for consent, with a notice in Malay and English.
• If I sell on WhatsApp, every ad chat gets a label, and I count paid ad chats weekly.

Your homework

Set up the Pixel and the Conversions API through your shop platform. Place one test order and check it in Test Events. If you sell only on WhatsApp, set up the From ad and Paid labels today and start counting the ad chats that pay.