🌐 Also available in: Français
Original source: Adobe Marketo Engage User Groups
This article is an editorial summary and interpretation of that content. The ideas belong to the original authors; the selection and writing are by Marketo Ops Radar.
This video from Adobe Marketo Engage User Groups covered a lot of ground. 2 segments stood out as worth your time. Everything below links directly to the timestamp in the original video.
If your MPI dashboards are empty, the fix is likely a single setting change per channel — not a data overhaul. Understanding the 'inclusive' vs. 'normal' distinction can unblock attribution reporting for your team the same day.
Why Your MPI Dashboards Are Empty — and the Channel Setting That Fixes It Immediately
A recurring pattern across Marketo instances is Performance Insights dashboards that appear blank or near-empty. A presenter demonstrated that the root cause is almost always the default channel analytics behavior setting — 'normal' — which requires period costs to be logged before any data surfaces. Switching each channel to 'inclusive' causes MPI to immediately begin reporting on available data regardless of whether costs have been entered, giving teams a working attribution view within 24 hours without any structural changes to their instance.
Beyond the channel behavior fix, the session demonstrated a UTM-based smart campaign pattern for capturing social and paid ad touches that originate outside Marketo. When a known or trackable person clicks a UTM-tagged link into a Munchkin-tracked page, a smart campaign can fire, add the person to a social or ad channel program, and set a success status — effectively pulling external channel activity into the attribution model. This pattern closes a common gap where paid media spend goes untracked because it doesn't originate from a Marketo asset.
Two additional configuration practices received emphasis: logging period costs at the program level to enable ROI calculations, and using required custom tags (such as region or business unit) enforced at program creation to ensure consistent filtering downstream. The session also covered the 20-report limit on saved quick reports and the ability to export MPI data directly to Excel or PowerPoint — a practical detail for teams that need to present attribution data to stakeholders without rebuilding charts manually.
"every single Channel by default utilizes the normal behavior and it's self-explanatory actually it says requires period costs and because nobody is actually adding in the cost of the different campaigns they're running they're not seeing any reports coming out of MPI based on this"
MPI Attribution Edge Cases: Contact Roles, Pipeline Columns, and the 24-Hour Refresh Lag
A Q&A session surfaced several practical blockers that prevent teams from getting full value out of Marketo's built-in attribution reporting. A common point of confusion — the absence of the Revenue Cycle Analytics attribution setting in Admin — turns out to require the Revenue Explorer add-on, not just the Revenue Cycle Modeler. Teams that have built lifecycle models but still can't find the attribution configuration setting should verify their subscription tier before troubleshooting further.
On the question of how contact-to-opportunity association affects attribution, a practitioner clarified that opportunity creation date — not expected close date — is the timestamp MPI uses to evaluate whether a touch should be attributed. This matters for teams trying to understand which programs influenced an opportunity: only activity prior to opportunity creation is counted by default, though the setting can be adjusted. For teams with inconsistent CRM hygiene, the hybrid attribution setting offers a fallback — if no contact roles are logged on the opportunity, Marketo falls back to account-level contact association. The cleaner path is getting sales to log contact roles consistently, but the hybrid mode provides a practical stopgap.
For teams seeing empty pipeline value columns despite having opportunity data flowing in, the answer is that MPI requires the standard CRM revenue field — not a custom opportunity value field — to populate pipeline and expected revenue metrics. This is a common misconfiguration in orgs that have customized their CRM opportunity object. The session also confirmed that adding period costs retroactively will cause MPI to reflect updated data within approximately 24 hours, since the reporting engine runs on a scheduled background process rather than in real time.
"if you want to be 100 sure in reality the best approach would be to make sure that sales is locking the correct contact roles on your CRM opportunities and then that then limit the the information that you're looking at to those contacts instead of the accounts so if you want great beautiful data that you can trust a hundred percent that puts a little demand or I would say a lot of Demand on sales"
Also mentioned in this video
Summarised from Adobe Marketo Engage User Groups · 58:01. All credit belongs to the original creators. Marketo Ops Radar summarises publicly available video content.
