A promo code shows which code was used in an order, but it does not always show where the buyer first learned about the offer. The code may be forwarded to a friend or posted on another site; attributing all such sales to a single post is too bold.
What different labels address
A UTM in a verified external link describes a tagged visit within the capabilities of analytics. A promo code describes the application of an offer at checkout. A buyer's answer of "saw it from an acquaintance" adds separate evidence, but it does not turn into precise technical attribution.
Yandex Metrica documents its own processing of labels and sources. This is not a rule that any store automatically links a promo code to the same source. If the system does not store such a link, its absence should be left visible.
Breaking down a conditional ten orders
Let us imagine ten confirmed orders with the code WORKSHOP. Six have a comparable visit via a partner link, two have another known source, and two have an unknown source. The report contains ten code applications and, separately, the distribution of available sources. All ten cannot be recorded as proven new partner sales.
Also check whether the code was used by a returning buyer. Applying a promotion and acquiring a new customer are different results. A refund or cancellation should be accounted for according to the accepted financial reporting rule, rather than disappearing from one table and remaining as revenue in another.
How to start observation
Before placement, choose a clear code, the terms of the offer, and the evaluation period. Make sure the store actually stores the code application on the order. Then check the correct external link and record which data is available given the user's consent. Do not add new UTMs on every internal visit.
In the report, keep three metrics side by side: used the code, source confirmed by available data, source unknown. This is a measurement methodology for a store where promo codes are already supported; it does not promise the presence of such a field in any Boosted order and does not require changing monetary settings.
Diagram: 1 — code usage, 2 — separate source verification, 3 — known and unknown sources without forced distribution.
Sources
Metrica: label processing. Verified on 20 September 2026. The examples, workflow, and diagram were prepared by the editorial team; the conditional numbers are not customer data.
If you are preparing a separate public post or video, check the view terms. This service does not perform the editorial work described and does not guarantee organic interest or sales.