From connected source to verified report.
This guide is for operators and agencies connecting Meta Ads, Google Ads, TikTok Ads, or Shopee to a Monstera workspace, then reading the imported data in Data Explorer, Google Sheets, or Looker Studio.
Before you begin
You need a Monstera workspace and permission to authorize the source account you intend to report on.
Pilot behavior
Manual refresh is available subject to your plan limits. Scheduled cadence is shown on the pricing page and in the product.
Step 1
Connect one source
Start with one certified workflow. Confirm current source coverage and limitations in the integration catalog.
- 1
Open Sources
Sign in, choose the intended workspace, and open Sources. - 2
Authorize the provider
Choose a supported source and complete its provider authorization. Select only accounts you are allowed to report on. - 3
Confirm workspace ownership
After the callback, verify that the connection appears under Your sources in the same workspace.
Expected result: The source shows as connected in the intended workspace. This confirms authorization; it does not yet prove that metric rows were imported.
Step 2
Run the first warehouse import
- 1
Choose a practical window
Use a recent date range that contains known activity and stays within the workspace plan limit. - 2
Select the exact account
If the connection has multiple ad accounts or shops, select the one with known recent data. - 3
Start one refresh
Run a single manual refresh and wait for its final status. Avoid starting overlapping refreshes for the same connection.
Expected result: Sync activity records a completed run and reports its outcome. A successful authorization with zero rows can still mean the chosen account or window had no supported activity.
Step 3
Verify before building a report
Open Data Explorer, select the same workspace, provider, account, and date window, then check:
- At least one row appears
- The earliest and latest dates match the import window
- Spend and delivery metrics are plausible
- The platform and account labels match your source
Expected result: The warehouse view matches a known provider report closely enough to proceed. Investigate material discrepancies before sharing a dashboard.
Google Sheets add-on
The Sheets add-on signs in with a Google identity token generated by Apps Script. It does not require you to paste a workspace API key into the sidebar.
- Open the add-on in the active spreadsheet and complete Google authorization if prompted.
- Use the Google account associated with the Monstera user or permitted pilot workflow.
- Select the workspace and report filters, preview the query, then write the requested rows.
Never copy or share the identity token. If the sidebar reports an expired or invalid token, close and reopen it, then reauthorize the add-on. Persistent audience errors require an operator to verify the backend's exact allowed Google token audience.
Looker Studio connector
Looker Studio uses a workspace API key. Create or rotate the key under Settings → API, then enter it only in the Monstera connector credential prompt.
- Verify warehouse data first.
- Create a workspace API key and store it securely.
- Add the Monstera community connector, authenticate, and choose a date range.
- Confirm the first chart totals against Data Explorer.
Partial or empty sync
- Confirm the selected workspace, connection, account, and date window.
- Check provider-side activity in the same window.
- Review the integration limitation notes; not every provider object or metric is supported.
- Read the final sync activity status before retrying. Do not treat “connected” as proof of imported metrics.
Expired or revoked connection
If the provider revoked access or refresh credentials can no longer be renewed, reconnect that source from its setup page. Confirm the returned connection stays in the intended workspace, then run one bounded verification import.
Limits and support
Connection, seat, pipeline, query, and date-range limits vary by workspace plan. Review the configured plan limits. During the private pilot, connector access and paid entitlements are confirmed with an operator.