Connection status
Reporting and proposals for review. This workflow does not publish ads or change bids, budgets or campaigns. Confirm the actual data delivered for your accounts.
Data to confirm
Check the required fields, reporting period and successful delivery before using these inputs.
Keep account totals separate from creative detail
The configured connection separates daily account-level reporting from a shorter ad-level analysis window. Campaign, ad-set and ad identifiers help retain context. The ad-level report is configured for a 95-day lookback; this is not a promise that every historical creative or period is available. Check the actual rows and reporting dates after the first successful sync.
Compare like-for-like evidence
Choose an account, currency, date range and outcome before comparing ads. Distinguish all clicks from outbound clicks and platform-attributed purchases from store orders. Do not add overlapping purchase action types or sum reach across days as if every person were unique. A creative with weaker engagement may need investigation, but audience mix, stock and landing-page changes can also explain the result.
Turn the review into a specific creative brief
Illustration: clicks on a dress ad increase while purchase progression weakens. The team checks the landing destination and size availability before proposing a different message. A useful brief names the ad, source window, product facts, observed issue, alternative explanation and reviewer. This is a proposed investigation, not evidence that a new creative will generate incremental sales.
Prepare the next task
Illustrative workflow. Record the source, open questions, owner and review date with the proposal.
- Select the account, period, currency and conversion definition.
- Verify account totals and inspect relevant ad-level records.
- Prepare a source-backed brief for human review; apply any approved campaign change in Meta.
First setup check
Reconcile a small sample with the source. Confirm history, refresh timing and missing fields for the question you want to answer.
Permissions and scope
Connection setup uses a Meta access token and ad-account identifiers. The configured access includes ads_read and read_insights. Daily ingestion is scheduled; current delivery depends on account access, quota and successful runs. Media access can differ from reporting access. Faccelerate does not automatically upload ads or change Meta budgets through this workflow.
Platform documentationThis reference explains the source platform, not the data delivered to your Faccelerate account.
