Connecting Ad Platform Accounts

​

Overview

Some storefronts run through direct ad platform adapters instead of a publisher sales agent. Before Scope3 can discover products, create media buys, sync creatives, or read delivery from those adapters, the customer must connect the relevant advertiser account to Scope3 through the platform’s own account-sharing or OAuth flow. This guide is written for legal, procurement, and platform admins who need to approve the access request. For what a connection actually is — organization vs advertiser accounts, manager-account (MCC / Business Manager) expansion, account types, and how discovered accounts map to your advertisers — see Ad Platform Accounts.

​

What Write Access Means

When Scope3 asks for platform write access, it is asking for permission to operate campaigns and related advertising objects for the advertiser accounts that the customer explicitly grants. It does not mean Scope3 needs broad business administration rights. Write access may be used to:

• Create, update, pause, or resume campaign objects, ad groups or ad sets, ads, budgets, targeting, and flight dates.
• Upload or sync creative assets and create platform-native creative records.
• Create or update first-party audience segments when the customer enables audience sync.
• Create or update product catalogs or feeds when the media-buy workflow uses catalog products.
• Read delivery, spend, approval status, pacing, and performance reporting.
• Send conversion or event data when measurement is configured for the advertiser.
• List connected advertiser accounts so the customer can choose the right one.

Scope3 does not need permission to:

• Add, edit, or delete users.
• Take ownership of the customer’s business account or advertiser account.
• Manage unrelated advertiser accounts that were not shared with Scope3.
• Change security settings, login settings, business verification, or platform account ownership.
• Manage billing users or finance roles unless a customer has a separate, explicitly approved billing workflow.

​

Recommended Access Pattern

Use the platform’s partner or manager-account sharing flow where available. The customer remains the owner of the business and advertiser accounts, and can remove or reduce Scope3’s access from the platform console at any time. For activation workflows, choose the least broad role that can both manage ads and read reporting. Use read-only access only for reporting-only pilots.

​

Agencies: Link the Manager Account

When an agency runs media for several clients, the pattern is the same on every platform:

1. Each client grants access on the platform side — to the agency’s container (Business Manager, manager account / MCC, Business Center) or, on platforms without an organization container, to the agency’s user.
2. The agency connects its own login in Interchange, once.
3. Every client account the grant reaches is discovered under that one connection, grouped under the manager account where the platform has one.
4. The agency maps each client account to the matching advertiser on the Advertiser mapping tab (Settings → Connections).

Organization-level linking is the agency-correct move because one grant surfaces the whole client portfolio. Linking a single client-shared ad account also works, but each additional client then needs its own connect. The per-platform sections below include an Agency setup subsection with the client-side steps.

​

Platform Summary

​

Meta

Ask the customer to add Scope3 as a partner in Meta Business Suite or Meta Business Manager, then grant access only to the advertiser assets required for the workflow. Default grant for activation:

• The relevant ad account.
• Campaign management access.
• Performance reporting access.

Additional assets may be needed depending on the campaign:

• Facebook Page or Instagram account access when ads use those identities.
• Pixel or dataset access when conversion events or conversion optimization are configured.
• Catalog access when catalog products are used.

Meta’s OAuth consent can include ads_management, ads_read, and business_management. The customer-side asset grant should still stay scoped to the specific business assets needed for the advertiser workflow. Scope3 does not need full control of the customer’s business portfolio, broad account-settings control, billing administration, or permission to add, edit, or delete users.

​

Agency setup

The client adds the agency’s Business Manager as a Partner on the ad account — in Business settings, under Partners, using the agency’s Business Manager ID — and assigns the same scoped access described above (campaign management plus performance reporting, plus Page, pixel, or catalog assets as needed). The agency then connects its own Business Manager login in Interchange; every client ad account the partner grants reach arrives under the agency’s Business Manager on the Advertiser mapping tab, ready to map to the right advertiser.

​

Meta app-install readiness

For Meta app-install campaigns, plan the campaign around mobile-first creative and privacy-safe app-event measurement before scaling spend:

• Use Advantage+ App Campaigns as the default starting structure unless the advertiser has a specific manual-buying reason.
• Start with lowest-cost bidding while the campaign is learning; move to cost controls only after the account has stable cost and conversion history.
• Keep placements open across Feed, Stories, and Reels so Meta can allocate delivery, and design Reels-ready vertical creative rather than treating Reels as an afterthought.
• Launch with at least 5-10 distinct creative variants. Prefer short vertical video that shows the app experience quickly, then keep refreshing variants as the campaign learns.
• For iOS, confirm SKAdNetwork or MMP postbacks and Conversions API event forwarding before scaling. Evaluate D7/D30 cohort ROAS instead of day-1 last-click results.
• Once trial, purchase, subscription, or other downstream app events are flowing reliably, optimize toward those events rather than raw installs.

​

TikTok

Ask the customer to share the advertiser account from TikTok Business Center to Scope3’s Business Center as a partner. Default grant for activation:

• Advertiser account role: Operator.

Use Analyst only for reporting-only access. Analyst can view ads, performance, and reports, but it cannot create or edit ads or manage audiences. Use Admin only when there is an explicitly approved reason to manage ad account settings. Admin is not the default activation role. Additional assets may be needed depending on the campaign:

• TikTok account delivery access for Spark Ads.
• Use “Only show as ads” when Scope3 should be able to run Spark Ads without publishing posts to the TikTok profile.
• Use “Show on TikTok profile and as ads” only when organic profile publishing is explicitly intended.

Scope3 does not need Business Center Admin, finance roles, or permission to add, edit, or delete users.

​

Agency setup

The client shares each advertiser account from their TikTok Business Center to the agency’s Business Center as a partner, using the agency’s Business Center ID, and assigns the Operator role (the same role guidance as above). The agency connects its own Business Center login in Interchange; the shared advertiser accounts appear grouped under the agency’s Business Center on the Advertiser mapping tab — map each to the right advertiser.

​

Google Ads

Ask the customer to grant Scope3 manager-account or account-level access to the Google Ads account that will run the campaign. Default grant for activation:

• Campaign management access.
• Reporting access.

Additional access may be needed depending on the workflow:

• Customer data or data-manager permissions when first-party audiences, enhanced conversions, or similar measurement workflows are enabled.
• Conversion action access when Scope3 is expected to configure or send conversion events.

Scope3 does not need Google Ads account ownership, billing administration, or permission to add, edit, or delete users.

​

Agency setup

Google’s flow runs in the other direction: the agency sends a link request from its manager account (MCC) using the client’s ten-digit customer ID, and the client accepts it from their account’s access settings. The agency then connects the manager account login in Interchange; client accounts under the MCC are discovered through the manager grant and appear under it on the Advertiser mapping tab — the MCC itself is context only and can never run buys.

​

Snap

Ask the customer to connect the relevant Snap advertiser account through OAuth or the approved Snap account-sharing flow. Default grant for activation:

• Ads management access.
• Reporting access.

Additional access may be needed for profile-backed creative workflows or measurement. Scope3’s Snap adapter requests Snap Marketing API access and may also request profile API access when the connected workflow needs it. Scope3 does not need organization administration, billing administration, or permission to add, edit, or delete users.

​

Agency setup

Snap access is member-based: each client invites the agency’s user into their Snap Organization as a member with an ad-account role that can manage campaigns and read reporting. The Snap grant is tied to the authorizing user, so the agency connects that user’s own Snap login in Interchange — the connection discovers every ad account the login can reach across all client Organizations, grouped by Organization on the Advertiser mapping tab.

​

LinkedIn

Ask the customer to connect the LinkedIn ad account that will run the campaign. Default grant for activation:

• Ads read access.
• Ads write access.
• Ads reporting access.

Additional access may be needed when creatives or sponsored content require an organization identity. Scope3 does not need Company Page administration unless the agreed workflow includes organic or organization-social publishing. Scope3 does not need LinkedIn account ownership, billing administration, or permission to add, edit, or delete users.

​

Agency setup

Each client adds the agency’s user to their LinkedIn ad account with a role that can manage campaigns and read reporting (Account Manager, or Campaign Manager when scoped to campaign work); a Sponsored Content Poster grant on the client’s Page is only needed when ads run under the Page’s identity. The agency connects its own LinkedIn login in Interchange; every client ad account the login can reach is discovered on the Advertiser mapping tab — map each to the right advertiser.

​

Pinterest

Ask the customer to connect the Pinterest ad account that will run the campaign. Default grant for activation:

• Ads read access.
• Ads write access.

Additional pin read/write access may be requested when the campaign workflow uses Pinterest-native creative or pin objects. Scope3 does not need account ownership, billing administration, or permission to add, edit, or delete users.

​

Agency setup

The client shares the ad account with the agency’s business through Pinterest business access — adding the agency as a partner by its business ID and assigning an ad-account role that can manage campaigns and read reporting. The agency connects its own Pinterest business login in Interchange; shared client ad accounts are discovered on the Advertiser mapping tab — map each to the right advertiser.

​

Reddit

Ask the customer to connect the Reddit Ads account or profile that will run the campaign. Default grant for activation:

• Ads read access.
• Ads edit access.

Additional conversion permissions may be requested when the customer enables conversion tracking or event logging. Scope3 does not need Reddit account ownership, profile administration beyond the advertising workflow, or permission to add, edit, or delete users.

​

Agency setup

Each client invites the agency’s user into their Reddit Ads Business as a member with access to the relevant ad account and a role that can manage ads and read reporting. The agency connects its own Reddit login in Interchange; the client ad accounts the login can reach are discovered grouped under their Business on the Advertiser mapping tab — map each to the right advertiser.

​

Amazon Ads

Ask the customer to connect the Amazon Ads account that will run the campaign. Default grant for activation:

• Advertising campaign-management access.
• Reporting access.

Amazon retail, seller, or vendor account administration is separate from advertising campaign management. Scope3 does not need retail account ownership, billing administration, or permission to add, edit, or delete users.

​

Agency setup

Each client invites the agency’s user to their Amazon advertising account from the Amazon Ads console’s user management, with a role that can manage campaigns and read reporting (DSP entities manage their users separately). Amazon access follows the Login with Amazon user, so the agency connects its own Amazon login in Interchange; every Sponsored Ads profile and DSP advertiser the login can reach is discovered on the Advertiser mapping tab. Amazon has no manager container — accounts arrive as a flat list, typed sponsored_ads or dsp.

​

Revoking Access

Customers can revoke Scope3’s access from the platform’s business, partner, manager-account, or OAuth settings. Revoking access stops future discovery, campaign changes, creative sync, audience sync, catalog sync, reporting reads, and measurement writes for that connected platform account. After revocation, refresh the connection in Interchange before running new discovery or media-buy workflows so the account status reflects the provider’s current authorization state.