Marketing Attribution Data in Power BI
Power BI is where many teams want to see which channels, campaigns and ads actually produce leads, customers and revenue.
This page explains the path that makes that possible: capture attribution in hidden form fields, pass it into your CRM, and model it in Power BI. It also gives you a checklist for confirming each link in that chain works before you trust a dashboard.
How the data moves from a form to a report
The workflow has four stages. First, hidden fields are added to your lead forms so attribution values have somewhere to live. Second, a script monitors the visitor's marketing channel and writes the values into those hidden fields. Third, when the form is submitted, the attribution details — channel, campaign name, ad name and similar values — are passed into your connected CRM. Fourth, Power BI reads from that CRM so you can build reports on which channels, campaigns and ads drive leads, customers and revenue.
A useful way to think about it: the form is the intake point, the CRM is the system of record, and Power BI is the presentation layer. If a report looks wrong, the problem is usually in one of those three places, not in the report itself.
What attribution information is captured
Two broad categories of data are captured.
Channel data: the channel a lead came from (for example Paid Search, Paid Social or Organic Search), plus detail within that channel. For Paid Search, that includes the campaign, ad group and keyword.
Landing page data: the first page the lead saw on your site (for example a blog article URL) and the category of that page (for example Blog).
The exact field names and control definitions are supplied in the protected form-controls contract module and should be treated as fixed. The list above describes the information categories, not a replacement schema.
A checklist before you build the dashboard
Use this list to confirm each link in the chain before you invest time in report design.
- Hidden fields exist on every lead form you care about, and their names match what the attribution script expects.
- A test submission produces non-empty attribution values in the form payload.
- Those values appear on the resulting CRM record, not just in the form tool.
- The CRM object you plan to report on has the attribution fields available to Power BI.
- Your Power BI model joins the CRM object to the right related tables (for example, contacts to opportunities) before you aggregate revenue.
- A single known test lead can be traced from landing page through channel and campaign to the report row.
If step 2 fails, the issue is on the site. If step 3 fails, the issue is the form-to-CRM connection. If step 5 fails, the issue is the data model, not the attribution data.
Worked example: one lead, one report row
Imagine a visitor arrives from a paid search ad and lands on a blog article. The attribution script records the channel as Paid Search, along with the campaign, ad group and keyword, and records the landing page as that blog URL with a page category of Blog. When the visitor submits a form, those values travel into the CRM record.
In Power BI, that single record can then be sliced by channel, by campaign, by ad group, by keyword, by landing page URL or by page category. Aggregated across many records, the same fields answer questions such as which campaigns produce the most customers or which landing page categories are associated with revenue. The value comes from the join between attribution fields and downstream outcomes — not from the attribution fields alone.
Telling apart the three common failures
Missing attribution in Power BI usually has one of three causes, and they are easy to confuse.
Form-level failure: the hidden fields are absent or misnamed, so nothing is captured at submission. Symptom: the form payload has blank attribution values.
Sync-level failure: the form captures values but the CRM record does not show them. Symptom: the form tool has the data, the CRM does not.
Model-level failure: the CRM has the data but the Power BI report shows blanks or inflated totals. Symptom: the raw CRM record is correct while the report is not, often because of a missing or duplicated relationship.
Checking these in order saves time, because each stage depends on the one before it.
Frequently asked questions
What attribution data can appear in Power BI?
Channel (such as Paid Search, Paid Social or Organic Search), channel detail such as campaign, ad group and keyword, the first landing page URL the lead saw, and the landing page category (such as Blog). These values are captured in form fields and passed into the CRM that Power BI reads from.
Does Power BI connect directly to the form tool?
In this workflow, no. The attribution values are passed into your CRM, and Power BI reports are built from the CRM data. The CRM is the system of record between the form and the report.
Why are attribution fields blank in my Power BI report?
Work backwards through the chain: confirm the hidden fields exist and are named correctly, confirm a test submission produces values, confirm those values reach the CRM record, and confirm the Power BI model relates the CRM tables correctly. The first stage that shows blanks is where the problem is.
Can I report on revenue, not just lead counts?
Yes, provided your CRM holds revenue or deal values on records that also carry the attribution fields, and your Power BI model joins them correctly. The attribution data itself describes the source; revenue comes from your CRM records.