# The Conversion Did Not End at WhatsApp

_Published 2026-09-09._

The pageview is the easy part.

A visitor arrives from an ad, reads the page in Arabic or English, taps a WhatsApp button, and the meaningful conversation happens somewhere else. If the click identifier disappears at that button, the dashboard can still show activity, but it cannot explain which visit produced the conversation.

That was the real platform problem behind ANGA. It was not “add three pixels.” It was making the visitor journey legible across systems that do not naturally share a record.

## Locale is part of the request

Arabic and English are not two color themes on the same page. They affect the URL, content, direction, and the meaning of what a visitor sees. An explicit locale should win over an automatic guess.

Laravel owns that first request. Attribution identifiers are captured there, carried through the page, and used again when the visitor moves toward a conversion.

## One event vocabulary

GA4, GTM, Meta, and the first-party conversion path do not need identical payloads, but they need to agree on the important nouns. If one system calls an action `lead_created`, another calls it `contact`, and a third only counts a button click, the reports will disagree before anyone opens a dashboard.

The [ANGA case study](/work/anga-website) treats WhatsApp as part of the funnel rather than a dead end. The handoff carries the same identifiers so an operator can connect the conversation to the visit that produced it.

The useful design is not “collect everything.” It is deciding which identifiers are necessary, when consent applies, and what the first-party record should still know when an advertising tag is blocked.