Measurement
Part of Podcast media reporting
Reporting promo-code sales without claiming complete attribution
Report accepted promo-code orders, sales adjustments and code coverage while making the limits of podcast attribution clear.
The defensible headline is orders recorded with the campaign code under the advertiser's sales rules. It is neither a count of everyone influenced by the podcast nor proof that every coded buyer heard it. Put the code's coverage, sales basis and adjustments beside the figure.
Present a traceable sales total
State the code or code group, eligible products and customers, campaign dates, redemption window and source system. Label the unit: accepted-code orders, distinct customers, gross order value or net sales. State how refunds, cancellations and tax are handled.
If codes differ by show, show each code's offer and dates; differences in sales may reflect different terms as well as different media.
Build the published total from orders where the checkout or order system accepted the code. Exclude test transactions and document manual adjustments. A rejected code is an issue to investigate, not an accepted-code sale. Keep order identifiers available for reconciliation without putting customer details in the media report.
Field in the report / What to show
- Code and offer
- Which code, eligibility and benefit produced the count
- Sales result
- Accepted orders and the stated sales measure
- Adjustments
- Refunds, cancellations and other documented changes
- Window
- When orders were accepted and when the data was extracted
- Distribution
- Any known use of the code outside the podcast campaign
Key Metrics for Reporting Promo-Code Sales
- Accepted Code Orders
- Total orders where the code was successfully applied at checkout
- Redemption Window
- Campaign start and end dates, plus when data was extracted
- Sales Measure
- Gross order value or net sales (with tax handling stated)
- Adjustments
- Refunds, cancellations, manual corrections documented
Explain differences from analytics
Google Analytics 4 has an Order coupons report. Its figures may help investigate the online journey, but should be labelled as analytics data.
Purchase-event duplication or omissions can also affect the comparison. Explain material differences from the accepted orders in the sales system rather than silently choosing the larger total.
Sales System vs Analytics Data: Key Differences
- Source System
- Sales system (checkout accepted codes)
- Analytics Source
- Google Analytics 4 Order coupons report
- Data Reliability
- Sales system: higher accuracy; Analytics: may have event duplication or omissions
- Recommended Use
- Use sales system total as primary; use analytics for journey insights only
Write the finding within the code's reach
A listener can buy without the code. Someone else can receive a shared code without hearing the podcast. A buyer may have encountered several promotions.
If the code also appeared in email or social activity, disclose that use. If its wider distribution is unknown, do not call the figure podcast-exclusive.
A ratio of accepted-code orders to reported ad deliveries can be shown as descriptive arithmetic when its units and windows are clear. It is not a causal conversion rate: the numerator may include shared-code orders, and the publisher's delivery event does not necessarily mean a person listened.
Close with what the sales system recorded, which offer and period the code covered, and the limit on attributing those sales to the podcast. Wider sales effect requires evidence beyond code use.
