Orders and advertising: what an online store can measure

Orders in the admin panel and purchases attributed by an ad platform measure different things. The panel records orders and statuses; advertising platforms attribute some purchases to interactions under their own windows and rules. A difference is not automatically a technical error.

We begin with the event that has business value. Clicking a phone link does not establish a completed call, and pressing an order button is not always a successful order. Purchase measurement should follow a saved order with accurate currency, value and a unique identifier to prevent duplicate counting.

Both quick-order flows and any standard checkout are tested separately. Client- and server-side measurement requires deduplication where both are used. Cancelled, returned and uncollected orders differ from realised profit and should be distinguished in reporting.

Google Analytics, Google Ads and Meta setup follows account permissions and visitor consent. Names, phones and emails do not belong in URLs, analytics labels or public events. Server-side sending is not used to bypass refused consent. Any platform-specific customer-data matching requires a separately justified and agreed implementation.

Before launch, agreed flows are tested and the measured events documented. Afterwards, events are compared with orders rather than promising attribution for every purchase. Browser settings, blockers and cross-device use can limit visibility.

Measurement setup is a separate technical task; media spend and ongoing campaign management are agreed separately. This gives clients a basis for decisions while distinguishing reported revenue, advertising costs and actual profit.