Power BI integration
Power BI is on the map, not in the product yet.
A daily SEO KPI feed pushed into your Power BI workspace, sized honestly to what push datasets allow.
How it works
Power BI connects through Microsoft Entra OAuth, and the integration pushes a small SEO performance dataset into the workspace you choose using the Power BI REST API's push datasets. Clicks, indexed pages, and rankings per day arrive as rows your analysts can build reports on alongside everything else the workspace holds.
In the loop, this is the measure step delivered into the BI tool your company already reports from. The design is deliberately a daily KPI feed rather than a data warehouse: push datasets carry hard limits on tables, rows, and request rates, and a compact daily feed fits inside them with room to spare while covering what executive reporting actually needs.
Best forCompanies whose reporting lives in Power BI and who want SEO KPIs present in the same workspaces as everything else.
Setup, step by step
- Click Connect on the Power BI card and sign in through Microsoft Entra OAuth.
- Approve the connection with an account that can create datasets in the target workspace.
- Pick the workspace the SEO dataset should live in.
- The connector creates the push dataset and sends the first day of KPIs.
- Build reports on the dataset, or start from the report layout suggestions in our guide.
Best practices
Treat it as a KPI feed, not a warehouse
The dataset carries daily clicks, indexed pages, and rankings, which is what push datasets are good at. For raw event-level analysis, the BigQuery integration is the right tool, not this one.
Put the dataset in a shared workspace
A dataset in a personal workspace helps one person. Landing it in the workspace your reporting team shares makes the SEO feed a first-class citizen of company dashboards.
Expect a rolling window of history
Push datasets retain a bounded number of rows, oldest dropped first. The feed comfortably holds a long daily history, and SearchHandled itself remains the archive for anything older.
Keep the daily grain
The feed pushes one row per KPI per day, which sits far inside Microsoft's request-rate limits and gives reports a clean, consistent grain. Finer-grained pushes would buy noise, not insight.
Known issues
What practitioners actually report, from official docs, issue trackers, and community forums.
Push datasets carry hard limits
The push dataset API caps a dataset at 75 tables and 75 columns per table, 10,000 rows per POST, 120 POSTs per minute, and retains 200,000 rows FIFO, so it cannot host bulk data.
How we handle itThe integration is positioned as a daily KPI feed sized well inside every one of those limits. The design is honest about what push datasets are for, and the limits never touch normal use.
learn.microsoft.com
Real-time streaming is flagged for deprecation
Microsoft has flagged Power BI real-time streaming for deprecation, so integrations built on streaming datasets face a forced migration.
How we handle itWe build on standard push datasets only, not the streaming variant, so the deprecation does not touch this integration.
learn.microsoft.com
Questions teams ask
- Can we get raw event-level data through this connection?
No, and by design. Push datasets are built for compact KPI feeds, not bulk data. For raw, unsampled event-level analysis, connect the BigQuery integration, which reads the GA4 export.
- How much history does the dataset keep?
Push datasets retain rows on a first-in, first-out basis up to Microsoft's row cap, which holds a long window of daily KPIs. Full history always remains available in SearchHandled itself.
- What if we do not use Power BI?
The Sheets export carries the same KPIs into spreadsheets, and the Looker Studio connector serves teams reporting in Google's stack.
Not connectable yet
Start with the plan, not the connector.
Build a Growth Map from your site to see the work itself. Approved pages can leave through the export or the webhook today, and telling us Power BI matters moves it up the rollout.