# Measuring showcases: from the ad to the paid purchase

> You connect the pixel once for your whole workspace; after that every published showcase reports to the ad platforms what happens on it, without starting any tool before the visitor agrees. The one thing to remember: “Purchase” is only sent once the money has really arrived. Our example: Yacine, a digital-marketing trainer, runs a Facebook ad and wants the platform to learn from his real sales.

- Time: about 10 minutes
- Who can do it: People with the workspace’s tracking settings. The “Measurement question” card needs the “Analytics” permission.
- Updated: 2026-10-06
- URL: https://www.dirassaplus.com/en/guide/showcase-tracking

## In short
1. Paste the “Pixel ID” and “Conversions API token” in “Settings” → “Tracking”: once for all your showcases.
2. Add a “Test code”, then tap “Send a test event” to see the server reach the platform.
3. Read “Server tracking health”: each platform’s state, its last accepted and last refused event.
4. On the showcase the consent bar asks the visitor; no pixel loads before “I agree”.
5. Events: PageView from the browser only, the others from the browser plus a server copy, Purchase from the server once money arrives.
6. In the editor, “Ask for tracking consent” turns the tools on or off for that showcase.
7. The “Measurement question” card in “Results” says how many visitors agreed.
8. If nothing arrives: published showcase, consent, id, the platform’s own message.

## Before you start
- A Meta or TikTok pixel id, and a Conversions API token so confirmed sales get through: the “Pixels” and “Conversions API” lessons show where to find them.
- A published showcase: the tools do not run in the preview or the draft.
- A payment method ready, so an order can become a paid purchase that gets reported.

## The steps

### 1. Connect once for all your showcases
Open “Settings” → “Tracking” (“Ad pixels & tracking”). Under “Facebook / Instagram (Meta)” and under “TikTok” there are two fields: “Pixel ID” and “Conversions API token”. Each field saves itself when you leave it, and the token then shows as hidden dots. Next to each platform a chip says how far along you are: id and token together mean ready; an id without a token means incomplete. All your showcases use these settings, and in the editor “Page” → “Ad tracking” says “Set up” or “Not set up”, with the “Tracking settings” link. The token is what lets the server report a confirmed sale, so don’t stop at the id.
On screen: «Settings»، «Tracking»، «Ad pixels & tracking»، «Facebook / Instagram (Meta)»، «TikTok»، «Pixel ID»، «Conversions API token»، «Ad tracking»، «Set up»، «Not set up»، «Tracking settings»
Heads-up: A Meta pixel ID is digits only, not the complete pixel script. Paste anything else and a red message appears under the field.

### 2. Try it before you rely on it: the test event
Open “Test codes” on the same page and copy the test code from Meta’s or TikTok’s Events Manager into “Test code (optional)”. Then tap “Send a test event”: the server sends a test “Purchase” of 100 DZD to each platform that has the id, the token and the code, without touching your real numbers. One line per platform: “Received. Open “Test events” to see it, then empty the code field.”, or refused by the platform in its own words, or “Not sent: add the test code first.”, or “Not sent: the server token is missing.”, or “No pixel set.”.
On screen: «Test codes»، «Test code (optional)»، «Send a test event»، «Received. Open “Test events” to see it, then empty the code field.»، «Not sent: add the test code first.»، «Not sent: the server token is missing.»
Tip: Empty the code field after the test: it is for checking once, not for sending with forever.

### 3. “Server tracking health”
Under the two platforms, this section says what Meta and TikTok answered to the server’s latest sends, not what you typed in the fields. Each platform has a state: “Working”, “Refused” (with the platform’s refusal text as it wrote it), “Nothing sent yet”, “No event for a week” or “Not set up”. Below, “Last accepted” and “Last refused” with their time, and a line on order conversions over 7 days: how many accepted, how many refused. Tap “Refresh” to read the latest. The section does not show at all while no pixel is set and nothing has been sent.
On screen: «Server tracking health»، «Working»، «Refused»، «Nothing sent yet»، «No event for a week»، «Not set up»، «Last accepted»، «Last refused»، «Refresh»
Tip: “Refused” with an expired token or a wrong id is the most common reason sales are missing from your ads: the platform’s message says which.

### 4. The consent bar: no tool before “I agree”
As soon as the workspace has a pixel, the visitor sees on the published showcase one line at the bottom of the screen: “We measure our ads with advertising partners. Do you agree?” with “I agree”, “No thanks” and a “Privacy policy” link. Neither the Meta nor the TikTok pixel loads before “I agree”. The answer is kept for 180 days. If the visitor closes the bar with “Close” (or the Escape key), that is not an answer: the tools stay off, and they are asked again on their next visit. Anyone with “Global Privacy Control” on in their browser is treated as a “no” without being asked. At the bottom of the showcase, “Privacy choices” asks again for anyone who changes their mind.
On screen: «I agree»، «No thanks»، «Privacy policy»، «Close»، «Privacy choices»
Heads-up: “Privacy choices” shows in the “Footer” when the bar exists, so don’t remove the footer altogether if you want visitors to be able to change their answer.

### 5. What is sent, and when
Only after “I agree”: PageView when the page opens, from the browser alone. ViewContent once per visit, InitiateCheckout on every buy-button tap (not a secondary button), Lead when a visitor sends a form or an order: those three go from the browser, and with a Conversions API token the server sends a copy with the same id, counted once even if the browser blocks the pixel. Purchase goes from the server alone and only once the money has arrived: a receipt you approve, a card the provider confirms, or cash on delivery recorded as collected (not merely when the order is approved). On TikTok the names change: Lead becomes SubmitForm, Purchase becomes CompletePayment, the others keep their name. And in “Tracking”, the “Events sent automatically” list covers the whole platform, including CompleteRegistration and Contact.
On screen: «PageView»، «ViewContent»، «InitiateCheckout»، «Lead»، «Purchase»، «SubmitForm»، «CompletePayment»، «Events sent automatically»
Tip: In Events Manager, PageView has no server copy: its count won’t match “Results”.

### 6. The “Ask for tracking consent” switch
In the editor open “Page” → “Header and footer”. If the workspace has a pixel you see the “Ask for tracking consent” switch, on by default for every showcase, even those made before the pixel existed: under it, “One line asks the visitor first; the Facebook and TikTok tools run once they agree.”. Switch it off to stop the ad tools on that showcase alone, and you read: “Measurement tools are off on this page: no consent line, no Facebook or TikTok pixels, and no orders sent to them from the server. The visit counter in “Results” keeps working.”. With no pixel in the workspace, you read instead of the switch: “No tracking tools are set up, so no consent is needed.”. While it stays off, the readiness list shows a yellow warning: “Measurement tools are off on this page, so its visits and orders will not count in your ads.” with a “Turn measurement on” button. Republish after a change so it reaches the published showcase.
On screen: «Page»، «Header and footer»، «Ask for tracking consent»، «Measurement tools are off on this page, so its visits and orders will not count in your ads.»، «Turn measurement on»، «No tracking tools are set up, so no consent is needed.»
Heads-up: Only switch it off with a reason: without the tools the ad platform learns nothing from this showcase’s sales.

### 7. “Measurement question”: how many agreed?
On the showcase’s page open “Results”: the “Measurement question” card says “N% of visitors agreed” among those who answered, with how many answered and how many did not. The share shows from 20 answers; before that the card says so instead of a meaningless number. Anyone who says no gets no pixel, so Facebook and TikTok count fewer visits than “Results”; orders and money collected are not affected. With no pixel, the card says visitors are not asked.
On screen: «Results»، «Measurement question»، «N% of visitors agreed»

### 8. I don’t see the events: what to check
Go through the list in order. First: test the published showcase, not the preview, which starts no tool. Second: tap “I agree” on the bar, no event goes before it. Third: in the editor, check that “Ask for tracking consent” is on. Fourth: go back to “Tracking” and tap “Send a test event”: if it says “Not sent: the server token is missing.”, paste the token. Fifth: read “Server tracking health”: on “Refused”, the platform’s text gives the cause (wrong id, expired token…). And on “No event for a week”, perhaps nobody visited after agreeing. Remember that some browsers and ad blockers cut the pixel, and that anyone with Global Privacy Control on is not measured.
On screen: «Send a test event»، «Not sent: the server token is missing.»، «Refused»، «No event for a week»، «Ask for tracking consent»
Tip: Open the published showcase in a private window, tap “I agree” and watch Events Manager: you see what your visitor sees.

## After measuring
- Set up the pixel step by step: Where to find the id and how to check it works.
- Add Conversions API: So confirmed sales arrive even when the pixel is blocked.
- Share a link per channel: And the ad parameters, to learn which channel sold.
- Follow up on leads: The follow-up desk shows where each person came from.

## Questions

**Why does Meta count fewer events than my visits?**
Because the pixel only runs after “I agree”, some browsers block it, and PageView has no server copy. Visits in “Results” are counted without any partner, so they are higher. Conversions API narrows the gap for ViewContent, InitiateCheckout and Lead among people who agree.

**Do I need a pixel per showcase?**
No. The id and token belong to the whole workspace and serve every showcase.

**When is Purchase sent for cash on delivery?**
When the cash is recorded as collected, not when the order is approved: the platform is never told about a sale that wasn’t paid.

**What if the visitor closes the bar without answering?**
The tools stay off for that visit, and they are asked again on the next. An “I agree” or “No thanks” answer is kept for 180 days.

**Are drafts and preview links measured?**
No. The tools only run on the published showcase, so your tests never mix with your numbers.

**The test event arrived: is the link sound?**
It proves the server reaches the platform with the id and token. After the test, empty the code and watch “Server tracking health” with the first real order.