Connect Meta Ads

Meta credentials let VEOtool read your ad account and pixel health during diagnosis (especially conversion tracking and attribution modules).

This is a manual connection today: you paste an ad account ID and a long-lived access token in Client Setup. A full Meta OAuth Ads Manager view is planned separately.

A Meta ad account you can access in Ads Manager.

An access token with at least ads_read permission (and ideally read access to the pixels linked to that account).

A saved client setup with a Google Ads account ID (Identity tab) so the Meta tab is available under Integrations → edit client.

Open Meta Ads Manager → Settings (gear) → Ad account settings. The account ID is shown at the top — use the act_1234567890 format (VEOtool also accepts plain digits and normalizes them).

If you manage multiple accounts, pick the one that matches the campaigns you diagnose for this client.

Recommended for agencies: create a System User in Meta Business Settings, assign the ad account, generate a token with ads_read, and store it securely.

For a quick test: Meta Graph API Explorer can mint a short-lived user token with ads_read — extend or replace it before production use.

The token must be able to read the ad account and, where possible, pixel/event metadata used in tracking checks.

Go to Integrations → open the client → Meta tab.

Enter Meta ad account ID and access token, then click Verify Meta.

When verification succeeds, save the client setup. Re-run diagnosis to include Meta signal in module findings.

VEOtool normalizes the account ID, confirms the account is readable via the Graph API, and reports pixel count and recent pixel activity when available.

If verification fails, check token expiry, missing ads_read scope, or wrong ad account ID. You can still save credentials, but diagnosis modules may skip Meta-specific checks until verification passes.