← Guides

Organise operations

Meta Ads client onboarding: OAuth, account access and a first-review checklist

Traffic AI by VT Group · Editorial review · 7 min read

Onboard a Meta Ads client by confirming asset ownership and the authorising person’s access, then connect through the official OAuth flow. Check that the required ad accounts are available and match their IDs, currency and business targets. A successful login is not proof that every required asset or permission was granted.

Prepare the account map with the client

List the client, business portfolio, ad account and assets involved in the campaign workflow. Confirm who owns them and who can authorise the integration. Similar account names are common; keep the account ID in the handover so a manager does not rely on a display name alone.

Record the purpose of each connection. Read-only review and campaign management involve different responsibilities. Ask for access appropriate to the task and explain which actions the product can propose or execute. Do not treat onboarding as permission to publish, change budgets or add unrelated assets.

Authorise through the official Meta flow

The authorised person signs in through Meta’s official flow and reviews the requested access. Traffic AI uses Facebook Login for Business through OAuth. The customer does not create a Meta API key or paste a token into a message as the normal connection process.

After the connection returns, inspect the available accounts. Match each ID to the account map. If an account is absent, check the person’s access and asset selection in Meta before reconnecting. Credentials, passwords and access tokens should never be placed in a client brief, screenshot, spreadsheet or support message.

Check the operating context before the first recommendation

Confirm account currency and timezone, campaign objective, conversion event and reporting period. Then record the commercial target for each offer. A lead target from one client is not interchangeable with a purchase target from another account, even if the currency is the same.

Inventory native rules and third-party tools that can mutate campaigns. Choose who owns each action scope during the pilot. For the first review, use manual approval and verify the proposed entity and before-and-after values. Access has been established; the live operating decision still needs its own review.

First-review checklist
CheckExpected output
AssetsOwner and correct account IDs
AccessRequired accounts are visible
MeasurementObjective, event, window and period recorded
Business targetOffer-level target approved by the client
ControlManual review and conflicting rules checked
HandoverResponsible person and reconnection path named

Handle missing access and revocation deliberately

A missing account can result from asset access, selection or an integration that needs reconnection. Collect the account ID and a description of the visible state without collecting secrets. Have the authorised person review the relevant access in Meta and reconnect through the product.

When a client leaves, agree which integrations should be revoked and which business records must be retained according to the applicable contract and policy. Revoking access prevents future use of that permission; it does not by itself delete historic data or cancel a commercial agreement. Use the relevant product deletion workflow separately.

A sample handover and the separate AI setup

An illustrative handover might read: “Client North, account ending 4821, GBP, purchase objective, offer target agreed, manual approval, first review assigned to Alex; no live change authorised yet.” This fictitious example demonstrates the level of specificity. It contains no real client information and should not include an access token.

In Traffic AI, Meta OAuth and AI setup are separate. BYOK applies to AI: the customer supplies their OpenAI key and pays the provider’s usage cost. Do not describe that AI step as a requirement to generate a Meta token. The regional product offer below explains how the campaign review workflow fits after the account is connected.

Common questions

Does connecting Meta approve campaign changes?

Connection grants the selected access. Campaign changes follow the product’s proposal, configured approval and execution validation process.

Should an agency ask for the client’s Facebook password?

Use the official authorisation process. Do not collect passwords or manual access tokens in onboarding documents or messages.

Sources and editorial limits

Reviewed 3 October 2026. Vendor documentation describes published features; it does not independently prove performance. Worked examples are illustrative.

Traffic AI by VT Group

Connect the right account, then review the first move.

Traffic AI uses official Meta OAuth and keeps campaign proposals in a controlled workflow. See the product and regional offer before setting up your first account review.

See the product and regional offer →

£127 one-time payment · lifetime access · AI-provider usage billed separately