Configure Power BI-ready destinations, site metadata, source mappings, page groups, and snapshot rules from AKM settings.
Power BI Destinations is the settings workflow for sending governed marketing snapshots into Power BI-ready reporting environments. It lets a team define the destination profile, business context, source mappings, snapshot rules, page grouping, and approved conversion logic in AKM.
The feature is intentionally not tied to one source type. A destination can be configured around the connected sources and reporting requirements that matter for the Power BI model, rather than being limited to one analytics or search platform.
Prepare governed BI exports without exposing report-specific infrastructure details.
Map site, market, timezone, connected sources, and approved conversion events in one place.
Support Power BI reporting workflows with repeatable snapshot configuration.
Add the Power BI destination name, tenant key, display name, market, timezone, and history start month.
Select the connected sources that should feed the BI view, then define page groups, conversion events, and optional query patterns.
Save the destination configuration so future reporting snapshots follow the same governed delivery rules.
Users define the destination name, tenant key, display name, domain, market, timezone, history start month, and finalization timing so snapshots follow a predictable reporting cadence.
Power BI reporting often needs several data inputs. AKM keeps source mapping in settings so the destination can draw from the connected accounts selected for that reporting model.
Snapshot output becomes more useful when page groups, conversion events, query patterns, and finalization rules are defined centrally. This keeps the Power BI layer focused on analysis instead of setup logic.
The destination copy and setup are broad enough for connected sources beyond one analytics or search provider.
Business metadata, source mappings, and snapshot rules live in AKM rather than scattered through report files.
The goal is to give Power BI a stable reporting feed while AKM controls source setup and measurement rules.
Continue through related AKM features, connector pages, or setup guidance.
No. The feature is designed around connected source mapping, so it can support the sources required by the reporting model.
Page groups keep report categories consistent across snapshots and reduce manual grouping work inside Power BI.
It controls when a reporting period should be treated as stable, which helps Power BI reports avoid shifting numbers after stakeholder review.