Scope
This guide covers setup & configuration for Google & Meta Ads Intelligence. Availability depends on your tenant package, role and configured providers.
Purpose
Bring paid performance into planning without unsafe autonomous spend.
Connect approved ad accounts and map them to projects.
Before you start
Correct tenant and project selected
Required source or provider is available
An accountable owner is identified
Test data can be separated from live activity
Procedure
- Open the correct tenant and confirm the project or workspace that owns this capability.
- Connect approved ad accounts and map them to projects.
- Connect or select the required source records and owners.
- Create a safe test configuration before using live customer or campaign data.
- Compare spend, delivery, leads and attributed outcomes.
- Keep platform changes and spending decisions human-controlled.
Verify the result
Compare spend, delivery, leads and attributed outcomes. Confirm that the intended record, state, run or report is visible to another authorised operator and that its next owner is clear.
Completion checkpoint
The capability is in the intended state, evidence is current, exceptions are owned and the next action can be understood without a separate status message.
Controls and limitations
Keep platform changes and spending decisions human-controlled. Predictive, attribution and recommendation outputs support operator judgement; provider and data limitations remain relevant.