Pageview counts alone don't tell you whether a traffic source is valuable — revenue per session does. Tying UTM campaign data to ad earnings closes that gap.
The core challenge
Ad Manager doesn't natively read UTM parameters the way analytics platforms do. To connect the two, you generally need to pass traffic-source information into a custom key-value at ad request time, then report against that key-value.
A practical setup
- Capture the relevant UTM parameter (source or campaign, typically) on page load.
- Map it to a simplified custom key-value — a small, consistent set of values rather than every raw UTM string.
- Pass that key-value into the ad request alongside your existing targeting.
- Report on revenue by that key-value inside Ad Manager's reporting tool.
Why this is worth the setup effort
Once it's running, you can directly compare RPM across organic search, social, newsletter, and paid traffic — which often reshapes where content and promotion budget actually gets spent.
How AdPulse helps
This kind of custom tracking is exactly the type of technical setup our ad operations consulting covers — built once, then folded into your regular reporting.
Want hands-on help applying this to your account?
Book a free consultation