Workspace boundaries
Keep each client's connections and reporting credentials in its own workspace and assign only the required members.
Agency workflow
Separate client data. Standardize the reporting process.
Monstera workspaces keep source connections, warehouse metrics, API keys, and sync activity scoped to the intended client boundary.
Normalized warehouse
Use consistent campaign dimensions for supported provider data while retaining source and account context.
Visible verification
Check sync outcome, date coverage, and row-level plausibility before a client report is refreshed or shared.
Recommended operating sequence
One repeatable handoff for every client.
- 01
Create the client boundary
Use a distinct workspace for each client or brand and confirm the correct members before connecting a source.
- 02
Connect and verify
Authorize one certified provider workflow, run a bounded import, and validate its rows in Data Explorer.
- 03
Deliver the report
Use the Sheets add-on identity flow or a workspace API key for Looker Studio, then reconcile the first report.
Pilot access, provider coverage, workspace capacity, and support expectations are confirmed before rollout.
Validate one client workflow first.
Use the first-run guide to connect, import, verify, and reconcile before expanding the pilot.
Read the verification guide