You will be able to install at least one platform's tracking and show that it records a real test conversion.
Priya's website runs on WordPress and has a booking form for trial classes (she is an invented example). Before running any Meta ads, she installed tracking, set up her main conversion and tested it with a real booking. The test found a problem she would otherwise have paid for.
Advertisers often find out a month into a campaign that the conversion tag was on the wrong page, fired twice or didn't fire at all. When that happens, every number in the report is wrong, and the platform has spent the month learning from bad data. About ten minutes of checking before launch would have caught almost all of these cases. The full exercise below takes about forty minutes the first time.
Work on the platform you chose in your account plan in Lesson 2.4, Plan your account structure. There are three common ways to put a pixel or tag on a site. For most small businesses, this is the order of preference:
The website platform's own integration. Shop builders and website platforms often have an app, plugin or settings page for Meta, Google and TikTok. You log in to the ad platform from inside it and choose your pixel or tag. The website platform places the code for you, and it often sets up standard events and server-side sending too, as described in Lesson 3.2, Server-side events and first-party matching. Google Tag Manager, a free tool that holds all your tags in one container. You add the container to the site once. After that, you add and manage tags in Tag Manager and don't need to edit the site's code again. It takes more learning than an integration. It gives you control when there is no integration, or when the integration doesn't do what you need. Pasting code into the site's template by hand. This works, but it is the route most likely to break later when someone edits the site. Use it only when neither of the other two is available.
Priya used a WordPress plugin that connects her Meta pixel and sends server events.
Your main conversion is the event in the ad platform for the key action you chose in Lesson 3.1, What a pixel does and why the auction needs it. Create it or confirm it in the ad platform.
Where it fires matters as much as what it is called. A purchase event must fire on the order confirmation page. If it fires on the checkout page, every abandoned checkout counts as a sale. A lead event must fire when the form is successfully submitted. If it fires when the form page loads, every visitor who opens the form counts as a lead. If you can pass a value, such as the order total, set that up now as well.
In Meta's Events Manager, Priya set Lead as her main conversion and made it fire on the form's thank-you message.
Each platform has a tool for checking that your events arrive. In Meta's Events Manager there is a Test Events feature. Meta says you can use it to verify that your server events are received, and it does not promise they appear instantly: events can take some minutes to show up, so check Meta's developer documentation for the current wait and for exactly what the tool displays. Google's Tag Assistant opens your site in a debugging session and shows which Google tags fire on each page and what they send. TikTok's Events Manager has its own testing area. These tools get renamed from time to time, so if a screen looks different, search the platform's help for testing events.
Test in these tools first because they show events sooner than the reports do. Some reports, such as the conversion columns in Google Ads, can take hours to update.
With the testing tool open, go through your site as a customer would. Land on the home page, visit a product or service page, then complete the main conversion.
The test conversion has to be real. In a shop, buy the cheapest item and refund it afterwards. For a form, submit it with your own details and write that it is a test in the message field so you can find and delete the enquiry later. Then check three things in the testing tool: that the conversion event appeared; that it appeared only once, or, if it was sent from both browser and server, that it arrived from both and was deduplicated into one; and that any value sent is correct. If an event is missing or doubled, fix it and test again. Don't move on with a known problem.
Deduplication is when the platform merges one event sent from both browser and server into a single count. It works by matching event IDs.
Priya's first test showed Lead arriving twice from the browser. The plugin fired it, and so did an old code snippet a freelancer had pasted into her theme. She removed the snippet and tested again. On the second test, Lead arrived once from the browser and once from the server, with matching event IDs, and Events Manager showed them as deduplicated. She took a screenshot of that screen.
She then wrote a short note in a shared document: event name Lead; fires on the booking form success message; sent by the plugin from browser and server; tested on the date she ran the test. Six months later, when she changes the form, the note tells her exactly what to test again.
You should end up with the same record. That means one platform's tracking installed, a main conversion that fires on the right page, and a screenshot of one real test conversion arriving once in the platform's event tool. You also need a written note giving each event's name, where it fires, how it is sent and the date you tested it. If you start advertising on a second platform later, repeat the same steps for it.
Set aside forty minutes with your site and the ad platform open side by side. The activity below asks you to do exactly this and keep the screenshot.
Install one platform's tag, set up your main conversion, make a test conversion and take a screenshot of it arriving in the platform's event tool.
Junxiong-WFG Organisation is an authorised representative of AIA Financial Advisers Private Limited (Reg. No. 201715016G).