Meta MPP Data Portal
Dashboard direction and data spec for Meta Managed Partner Program account operations, spend tracking, and reporting workflows.
Context
How can we make this workflow easier to search, track, understand, and act on?
The Problem
- Which accounts belong to which batch?
- Who manages each account?
- Which accounts are prepaid or postpaid?
- How does current spend compare to the previous window?
- Which accounts are growing or declining?
- How do campaign, ad set, and ad-level insights fit together?
Research & Direction
- Research
Workflow Research
Understood how MPP ad accounts, batches, account managers, spend windows, and reporting needs were being handled.
- Proposal
Wireframe Proposal
Created the initial dashboard concept covering account selection, spend tracking, insights, and admin workflows.
- Stakeholders
Stakeholder Discussions
The marketing team was directly involved in the MPP workflow and connected with Meta stakeholders through recurring weekly meetings.
- Data Spec
API fields & windows
Studied the Facebook Marketing API documentation to pin down the endpoints and parameters that could return the data we needed — accounts, batches, spend windows, insights — and defined the fields and formulas the reporting would run on.
- Decision
Direction Shift
The team chose a lighter API-to-Excel reporting workflow instead of building the full dashboard UI immediately.
- Recreation
Dashboard Concept
Refined the original direction into a high-fidelity interface that made the proposed workflow tangible for stakeholder review.
Product Scope
Four connected capabilities formed the dashboard. Together they covered account selection, spend tracking, drill-down insights, and admin maintenance in one workspace.
Account Selection
- Search account name or ID
- Batch-wise filtering
- Account manager selection
- Multi-select account controls
Spend Tracking
- Last 7 Days Spend
- Pre 90 and Post 90 windows
- Spends Till Date
- Growth / Decline status
Insight Exploration
- Campaign insights
- Ad set insights
- Ad insights
- Parent-child context
Admin Management
- Assign account manager
- Assign batch number
- Set prepaid or postpaid
- Bulk import accounts
User Flow
Context is established first, then analysis. The admin branch runs in parallel to keep account assignments up to date.
The flow prioritizes context before analysis, so users always know which account set they are reviewing before interpreting spend or insight data.
Data Model & Reporting Logic
Design Direction
- Light backgrounds with white cards
- Soft borders and compact filters
- Blue accent states for primary actions
- KPI cards, status badges, and date range controls
- Formula helper panels that made logic visible
- Sortable, exportable tables
Interface Highlights
The recreated interface as one connected system, with callouts mapping each product moment to its supporting surface.
Product identity and access
Login introduces the tool while keeping authentication focused.
Account context
Search, filters, batch selection, and multi-select establish what data is being analyzed.
Spend analysis
KPI cards, formulas, and tables separate summary from detail.
Reporting support
Date range selection, sorting, and CSV export support operational reporting.
Feasibility Decision
From Product Direction to Delivery Path
With the workflow mapped and the data spec validated, the team chose the fastest path to production: an API-to-Excel workflow built on that structure. The dashboard direction stays as the reference for the full product build.
Full Dashboard UI
- Centralized account and spend visibility
- Better long-term product experience
- Easier filtering and drill-down insights
- More scalable interface
- Higher engineering effort
- Longer implementation timeline
API-to-Excel Reporting
- Faster to implement
- Lower engineering effort
- Solved the immediate data-access problem
- API extraction built by the tech team on the data spec I defined; report format designed by me
- Reports were shared in Excel format over email
- The workflow ran on this structure through the team's weekly Meta reporting until the MPP program wound down.
What shipped
The team moved forward with the API-to-Excel workflow. It ran on the structure that came out of my sprint.
Mapped the workflow
Account selection, spend tracking, insights, and admin assignment designed as one system.
Defined the data spec
The exact API fields, spend windows, and formulas the reporting needed.
Reporting shipped
The Excel workflow built on that spec ran weekly until the MPP program wound down.
Dashboard direction delivered
A hi-fi reference the team can build from when the time comes.
The fastest path to production was the right call for that moment. The dashboard direction is ready when the product is.
