AdAce AdsConnect Meta ad accounts and verify Facebook and Instagram data access
Facebook and Instagram advertising uses Meta ad accounts, while pages, Instagram identities and pixels are separate assets. Begin by connecting the correct account, then verify the assets needed for your task. An AdAce Ads connection records authorization and selected resources; it does not establish that every Meta capability is available.
Accounts and assets have separate access
The implemented connection starts from Integrations and opens Meta's consent flow. Your Meta identity, its account access, selected assets and the configured application's permissions determine what can be discovered. Having a Facebook login or access to a page does not by itself prove access to an advertising account. AdAce Ads lists the accounts returned through the connection so you can select the advertiser and attach it to the correct client.
After selecting an account, import the campaigns you want to inspect. This import brings in campaign records; ad sets and ads require a separate structure collection and appear when that collection succeeds and access permits it. Reading pages, pixels or Instagram identities is a further capability check: a campaign may be visible while an asset needed for diagnostics or creative work is unavailable. Do not substitute another client's page or pixel for a missing asset. Investigate ownership and assignments in Meta before continuing.
For example, North Store and South Service can have similar campaign names while using different pages, Instagram identities and currencies. Connect North Store to the North Store client, compare the displayed account identifier and currency, then import one recognizable campaign. Verify the campaign first. After structure collection, inspect any available ad sets and ads in Campaigns. If the planned placement involves Instagram, confirm the relevant identity is accessible instead of assuming Facebook authorization covers it.
Connection health, imported structure and performance are separate evidence. Use Check now to inspect the current connection and verify the time and result of collection when reading reports. Recent attributed outcomes can be revised; align the account, period and reporting definitions before comparing with Ads Manager. A read failure is missing data, not zero results. The implementation tracks token validity and can require reauthorization, but local connector tests do not prove a live Login for Business configuration has passed acceptance.
Verify the advertiser before using its data
- Bring Meta campaign structure into the client context your team uses for other advertising channels, while preserving the account mapping.
- Identify missing permissions or assets before using reports or drafting creative changes that depend on a page, pixel or Instagram identity.
- Use observable connection and import results for handoffs instead of relying on a successful-looking consent popup.
Connect, import and check
- Ask an owner or administrator to open the intended client's Integrations and choose Connect Meta. If unavailable, resolve the deployment's provider configuration first.
- Allow the popup, review the Meta identity and selected business assets, and authorize only the intended access. Return to the application and inspect the connection result.
- Choose the advertising account from discovery. Compare its name, displayed identifier and currency with Ads Manager before attaching it to the client.
- Import a small campaign selection and verify the imported count and campaign names. After a successful structure collection, inspect available ad sets and ads. Check required assets separately for the task you plan.
- Run Check now and inspect Analytics when collection is available. Record the period and freshness of the evidence before asking a teammate or AI client to interpret it.
Missing assets, reauthorization and disconnect
- Account or asset missing: check the signed-in Meta identity and its current business assignments, review the consent selection, then refresh discovery. An expired selection requires a new list. Do not enter raw tokens into the interface to bypass this process.
- Needs_reauth, denied consent or callback failure: restart authorization from the intended client. A configuration, approved-permission or token-type problem needs the service operator; reconnecting repeatedly cannot establish app approval.
- Disconnect removes local connection access and may queue provider revocation. Inspect the revocation result; queued or failed is not confirmed removal at Meta. If removal is unconfirmed, review the application's permissions in Meta. This setup does not authorize advertising writes, guarantee delivery or promise automatic rollback.
Sources and further reading
Try it on your own accounts
Create a workspace, connect Google or Meta in a couple of clicks and see your accounts clearly. Changes follow your approvals or the policy you configure.
Create your workspace