Before you connect Meta: permissions, the pixel and the Custom Audience terms
With Block, Tapper creates a custom audience called Tapper - Invalid Traffic Audience in each ad account and excludes it from the ad sets you protect. That needs four things. You do not need to own a Facebook Page. On a Lift-only workspace Tapper creates no audience, so the pixel and the terms do not apply.
What to check
- Advertiser or Admin access. In Meta Business settings, open Accounts > Ad accounts > People and check your profile has Manage campaigns or Manage ad account. View-only (Analyst) access is refused. If you lack it, ask an admin of the ad account, or let someone who has it connect.
- Permission to manage your ads. When Meta asks what Tapper may do, allow everything, in particular managing your ads.
- A Meta pixel on the ad account. Without one, the account does not connect.
- Meta's Custom Audience terms, accepted once per ad account. Ticking an account on Tapper's list shows Accept the terms on Meta, which opens them. Or in Meta Ads Manager, open Audiences, then Create audience > Custom audience > Website, and accept.
What Facebook asks for at sign-in
| Permission | What it covers |
|---|---|
email | Your email address |
ads_read | Reading your ad accounts and their spend |
ads_management | Managing your ads, which Tapper needs to create its audience and attach it to ad sets |
business_management | The business portfolios and the ad accounts they own |
pages_show_list | The list of Pages you manage |
pages_read_engagement | Your Pages' content and engagement |
For every platform, see What access Tapper asks for on each platform and what it does with it.
If something fails
Each failure message and its fix is in Meta Ads account could not be connected.
Related
Was this helpful?
Still need help?
Chat with our team and mention this article.