
“Revenue Per Element” would measure how much revenue is generated per individual component, unit, or touchpoint (an “element”) in a marketing, product, or sales context. The “element” might be an ad unit, an email, feature, campaign, or product SKU. It’s a way to break down total revenue into smaller attributable parts.
Breaking down revenue by element helps marketers and product teams see which parts of their mix are most effective. It supports optimization by identifying high-performing assets and underperforming ones. If you can tie revenue to elements (e.g., particular ad creatives, emails, landing pages, or SKUs), you gain granularity in decision-making.
An ecommerce brand runs three banner ads (A, B, C). Ad A drives $20,000 in sales through tracked clicks, with 100,000 impressions. The “Revenue Per Ad Impression” for Ad A = $0.20. By comparing that to Ads B and C, the brand can shift budget to the most effective ads.
If instead the “element” is SKU, then “Revenue Per SKU” for a given product variant would be total revenue from that SKU divided by number of units or transactions of that SKU.
Because “Revenue Per Element” is custom and context-dependent, standardized benchmarks are rare. However:
If you like, I can adapt this into your specific domain (e.g. ads, email, SKUs) and give you benchmarks tailored to your industry (e.g. Philippines, DTC). Do you want me to do that?
Might as well give us a shot, right? It'll change the way you approach CRO. We promise. In fact, our friend Nate over at Original Grain used element-level revenue data from heatmap to identify high-impact areas of his website to test, resulting in a 17% lift in Revenue per Session while scaling site traffic by 43%. Be like Nate. Try heatmap today.
