Lesson 4 — Tracking: Google Analytics, Search Console and the Meta Pixel for Your Store in Qatar, and Why Every Order Must Carry Its Source (2026)

ThreeU team22 أكتوبر 2026

trackingGoogle AnalyticsMeta pixelSearch ConsoleQataracademy

Lesson 4 — Tracking: How to Know Which Ad and Which Page Brought the Customer, Even When They Buy on WhatsApp

Straight answer: Before you pay the first riyal for ads, install three things: Google Analytics 4 to tell you what the visitor did, Search Console to tell you how they arrived from search, and the Meta pixel with the Conversions API so Instagram learns which ad produced a purchase rather than a click. Then the specifically Qatari problem: most purchases complete in WhatsApp, not on the checkout page, so if the WhatsApp conversation is not linked to the ad it came from, Instagram will optimise for the curious rather than the buyers. The fix is that every order and conversation carries its source.

What you will learn

The three tools and the question each one answers.
The four events to measure in a small store.
How to track a customer who came from an ad and bought on WhatsApp.
The five tracking mistakes that make the numbers lie.

The three tools

| Tool | The question it answers | Without it | |---|---|---| | Google Analytics 4 | Where the visitor came from, what they did, where they left | You improve pages by guessing | | Search Console | Which words you appeared for and which pages are indexed | You do not know half your store is invisible | | Meta pixel + Conversions API | Which ad produced a purchase or a conversation | Instagram optimises for cheap clicks |

The four events

1. Product page view — measures interest. 2. WhatsApp click or add to cart — buying intent. 3. Checkout started or conversation started — entering the funnel. 4. Purchase (from the checkout page or an order confirmed in WhatsApp) — the event your ads should optimise on once its weekly volume is enough.

The Qatari problem: the purchase completes in WhatsApp

In many Qatari stores the customer taps the ad, opens WhatsApp, asks, then pays by transfer or on delivery. The ad sees "conversation started" and never sees the purchase, so it learns to bring people who start conversations rather than people who buy. The fix has three steps: 1. An ad link that passes the click identifier into the conversation (official click-to-WhatsApp ads do this automatically with an API number). 2. Registering the order in the system linked to the conversation and the ad identifier. 3. Sending the purchase event to Meta through the Conversions API when the order is confirmed, so the campaign learns from real buyers. The full walkthrough is in lead tracking on WhatsApp in Qatar.

The five tracking mistakes

1. The pixel is installed but the purchase event is not defined, so the campaign optimises on visits. 2. The ad sends people to an employee's phone instead of an API number, so the trail breaks at the first message. 3. Ad links carry no source parameters, so everything shows as "direct" in Analytics. 4. Analytics measures only the thank-you page and forgets WhatsApp and POS orders. 5. Reports nobody reads weekly; tracking without a reading appointment is decoration.

How the ThreeU system does it

You connect Google Analytics and Search Console from the integrations page in one click and the numbers appear in your dashboard instead of across separate accounts. Meta ads are managed from the platform, the official WhatsApp number through Zajil receives ad conversations with the click identifier, and the order an employee registers from the conversation carries its source and is sent to Meta as a purchase event. The result is one report: how much you spent, how many conversations, how many orders, and from which ad. If your ads bring messages but no sales, the cause is usually in this lesson; see ad management in Qatar.

Lesson exercise

Open Analytics and answer: how many visitors last month, from which channels, and how many of them clicked WhatsApp or added to cart? If you cannot answer within ten minutes, this week's task is installing the three tools and defining the four events.

Checklist

[ ] Analytics 4 installed and showing channels
[ ] Search Console connected
[ ] Meta pixel and Conversions API sending the purchase event
[ ] WhatsApp ads go to an official API number
[ ] Every order in the system carries its source
[ ] A fixed weekly appointment to read the numbers

I want to connect tracking before I start ads

Previous lesson: Lesson 3 — Being found on Google · Next lesson: Lesson 5 — Ads from one dashboard · Academy index

FAQ

Do I need a developer to install the pixel and Analytics?

On ready platforms, no; you paste the identifiers or connect the accounts from settings. A developer is needed only for hand-built sites or complex custom events.

What is the difference between the pixel and the Conversions API?

The pixel sends from the visitor's browser and is affected by tracking blockers and mobile updates; the Conversions API sends from the server or the system directly and includes events the browser never sees, such as a WhatsApp order confirmation. Both together are more accurate.

When should I optimise the campaign on the purchase event?

When you have enough purchase events per week for the campaign to learn from; before that, optimise on a closer event that repeats more, such as conversation started, while tracking purchases in parallel.