Product Tagging
Part of Social commerce measurement
Product tag clicks versus completed orders
Learn what product tag actions and store orders each count, when a rate is valid and how to report a gap without calling clicks sales.
A product tag click records an action in a social shopping experience. A completed order records a purchase under the retailer's chosen order definition. Show both. Do not call tag clicks sales or divide unrelated totals into a conversion rate.
Establish what was counted
Start with the platform's exact metric name. Does it count taps, product-detail opens, outbound clicks or distinct accounts? Record the post, product and period. One shopper may interact with several tags or tap the same tag more than once.
For the store figure, decide whether you mean orders placed, paid orders or orders retained after cancellations and refunds. Also distinguish orders from purchased items and units. Check the metric documentation to understand what each reported measure counts.
Check the order report's documentation for how it treats cancelled, pending and unpaid orders; do not assume its total means completed, paid or retained orders.
| Figure | What it establishes | What it does not establish alone |
|---|---|---|
| Tag actions | The defined platform action occurred | The shopper reached the store or bought the item |
| Measured store visits | A website visit was recorded | It came from a particular native tag unless the route is identifiable |
| Purchase events | Analytics received the configured event | The order’s later payment or refund status |
| Store orders | An order met the chosen store definition | Which social action caused it |
Product Tag Clicks vs Completed Orders: What Each Metric Actually Counts
- Product Tag ClickA tap, product-detail open, or outbound click on a social media product tag. May include multiple interactions by the same user.
- Completed OrderAn order that meets the store’s definition of 'completed'—typically paid and not cancelled or refunded.
Use a valid denominator
A tag-click total and an attributed-order total for the same week may cover different people, visits and attribution rules. A tag may open an in-app product view, while an order may follow a later visit.
Their quotient is a ratio of reported totals, not a tag-click conversion rate, unless the retailer can identify the eligible click population and link its outcomes under a stated rule.
For the website, the share of eligible social-entry sessions containing a recorded purchase event is a more clearly defined session measure when entry and purchase data are collected consistently. Check those events against store orders before calling them completed sales. If the native tag cannot be connected to store visits, leave its count in a separate column.
Key Metrics to Track in Social Commerce Reporting (Australia)
- Tag ActionsTaps or product views from Instagram or Facebook via Meta's native tagging
- Measured Store VisitsWebsite sessions originating from social tags (if tracked via UTM or analytics)
- Store Orders (Completed)Paid orders retained after cancellations and refunds – as defined in Shopify or ATO-compliant reporting
Investigate a gap without guessing its cause
When tag actions rise but measured visits do not, check what the tag opens and whether the store visit is captured. When visits rise but orders do not, inspect the product and buying route. A paid boost, stockout, tracking change or different audience could also explain the pattern; the counts alone cannot decide.
A tag interaction and a store order are distinct reported events. The available figures alone do not show whether or how a shopper moved between them.
Report the platform metric, measured visits if available, the selected store-order status, period and attribution rule. If the systems cannot be joined, say so plainly.
How to Report Product Tag Performance Without Misleading Claims
- Confirm the platform metric definitionCheck whether 'tag click' includes taps, opens, or outbound links (e.g., Meta’s documentation)
- Define 'completed order' clearlySpecify if it includes only paid, non-refunded, non-cancelled orders per your business logic
- Verify attribution rulesEnsure session data matches tag actions; don’t assume all clicks lead to purchases
- Report gaps transparentlyIf tag clicks and orders aren’t linked, state this clearly—do not infer conversion rates
