Connecting Meta to Churney

By Churney
-
Updated November 2026
Meta and Churney

Churney sends each new customer's predicted long-term value to Meta through the Conversions API, so Meta's bidding goes after the customers who pay back. Setup is seven steps in Meta Business Suite, guided in the Churney app.

At a glance: 7 steps · Admin access in Meta Business Suite · Guided in the Churney app

Before you start

  • Admin access to the ad account and your Meta business portfolio.
  • A system user in Business Settings. An existing one works, or create one for Churney.
  • Access to the Churney app. You get it when you onboard.

Step 1. Add Churney as a partner

The Churney app shows our Business ID. You need it here and in step 2.

  1. In Meta Business Suite, go to Settings > Accounts > Ad accounts.
  2. Select the ad account and click Assign partner.
  3. Paste the Churney Business ID and turn on View performance and Manage campaigns.
  4. Copy your Ad Account ID into the Churney app.

Watch: assigning Churney as a partner

Step 2. Share your events dataset

Churney sends predicted value events to your dataset, the asset behind the Conversions API.

  1. Go to Settings > Data sources > Datasets.
  2. Select the dataset and click Assign partner.
  3. Paste the Churney Business ID and turn on Manage events dataset.
  4. Copy your Dataset ID into the Churney app.

Step 3. Let the system user manage campaigns

  1. Go to Settings > Accounts > Ad accounts.
  2. Select the ad account and click Assign people.
  3. Select the system user and turn on Manage campaigns.

Step 4. Connect a developer app

Churney needs a Meta developer app assigned to the system user. If you have an app whitelisted for bid multipliers, use that one.

If you already have an app

  1. Go to Settings > Accounts > Apps.
  2. Select the app and click Assign people.
  3. Select the system user and turn on Develop app.

If you need to create one

  1. Go to developers.facebook.com/apps/create and choose Business as the app type.
  2. Name it, for example churney_access_app, add your contact email and business portfolio, and click Create app.
  3. Under App Review > Permissions and Features, check that ads_management and business_management have Standard access.
  4. In Business Settings, open Users > System users, select the system user, choose Assign assets > Apps, pick the app and grant Manage app.

Step 5. Allow ads for your Pages

Only needed if Churney sets up the campaigns for you.

  1. Go to Settings > Accounts > Pages.
  2. Select the Page and click Assign people.
  3. Select the system user and turn on Ads.
  4. Repeat for every Page you advertise for.

Step 6. Generate an access token

  1. Go to Settings > Users > System users.
  2. Select the system user and click Generate token.
  3. Set the expiration to Never.
  4. Grant ads_management and business_management.
  5. Paste the token in the Churney app.

Churney checks the token by creating a test custom audience, so permission problems show up before anything goes live.

Why these permissions: ads_management lets Churney send predicted value as the optimization signal and read performance to measure results. business_management is needed because the dataset is a Business Manager asset.

Step 7. Choose campaigns

With the connection in place, the app lists your active Meta campaigns with status, objective, daily budget and start date, plus a sample of active ad sets and their countries. Pick the campaign you want to replicate for the Churney experiment. You don't need to make a final decision yet.

What Churney sends to Meta

  • Predicted value events through the Conversions API into your dataset, set up as custom conversions for value optimization.
  • Match keys: fbc and fbp, plus hashed email, phone and address, and external IDs. With full identifiers, Event Match Quality typically lands at 8 to 9.

App campaigns usually run through your MMP. See AppsFlyer, Singular or Adjust.

See whether your data predicts long-term value.

Book a 30-minute call. We look at your setup and tell you plainly whether pLTV is worth testing.