Meta ads

Connect the Meta Pixel and the Conversions API (CAPI) so Facebook and Instagram ads optimize on real bookings and revenue, and bring Meta Lead Ads submissions into Arketa as new leads.

When you run Facebook or Instagram ads, Meta needs reliable conversion data to find buyers — not just clickers. Arketa connects Meta Pixel (browser) and the Conversions API (CAPI) (server) together so your campaigns see bookings, purchases, trials, and subscriptions even when the browser Pixel is blocked.

Set up both. Pixel alone misses a meaningful share of events. CAPI is what makes your reporting and optimization trustworthy.

Why CAPI is worth setting up

The Meta Pixel runs in your client's browser. That worked well for years — but today a lot of conversion signals never reach Meta:

  • Ad blockers and privacy extensions stop fbq from firing
  • iOS and browser privacy limit what client-side tracking can see
  • Paid subscriptions often convert on a server invoice after checkout, when the browser session is already gone

Conversions API (CAPI) sends the same conversion events from Arketa's servers directly to Meta. You get a second, independent path for every important action on your booking page.

What you gain

  • More complete data — recover conversions the browser Pixel never recorded
  • Smarter ad delivery — Meta's algorithm optimizes on real revenue, not incomplete signals
  • Accurate ROI — see which ads drive bookings and memberships, not just landing-page visits
  • Automatic deduplication — Arketa sends matching event IDs from browser and server; Meta counts each conversion once
  • Reliable subscription tracking — Subscribe fires when the first invoice is actually paid, server-side, so failed cards don't inflate your numbers

CAPI is not a replacement for Pixel — it's the pairing Meta recommends. Arketa handles both and keeps them in sync.

What you'll need

  • A Meta Business Manager account
  • A Meta Pixel (create one in Events Manager if you don't have one yet)
  • A Conversions API access token for that Pixel
  • Your website domain verified in Meta Business Manager

Set up Meta tracking in Arketa

Copy your Pixel ID

  1. Go to business.facebook.com and log in
  2. Open Business Settings (gear icon, top right)
  3. Go to Data Sources → Pixels
  4. Select your Pixel (or click Add to create one) and copy the Pixel ID

You can also find the Pixel ID in Meta Events Manager under your dataset's Settings.

Generate your Conversions API token

CAPI requires a server access token tied to your Pixel — this is separate from your Pixel ID.

  1. In Meta Events Manager, open your Pixel / dataset
  2. Go to Settings
  3. Scroll to Conversions API
  4. Click Generate access token (or Set up manually → generate token)
  5. Copy the token and store it somewhere secure — Meta may only show the full value once

Use the token from Conversions API in Events Manager, not a preview or test token from elsewhere.

Verify your domain (recommended)

Domain verification helps Meta attribute events to your site and improves delivery quality.

  1. In Business Settings, go to Brand Safety → Domains
  2. Add your domain if it is not listed and follow Meta's verification steps
  3. Open the domain and copy the Meta Tag Verification code from Domain Details

Connect in Arketa

  1. Go to Settings → Integrations → Meta
  2. Enter:
    • Meta Pixel ID
    • Conversions API access token
    • Domain Verification Meta Tag (if you use domain verification)
  3. Save

Once your Pixel ID and CAPI token are saved, server-side tracking is on. Optional: enable Track subscription renewals (LTV) if you want a custom SubscriptionRenewed event sent on each renewal (see FAQ below).

Meta integration fields in Arketa Settings

Confirm events in Meta

  1. In Events Manager, open Test Events
  2. Complete a test booking or purchase on your client-facing booking page
  3. You should see the event with Browser and Server sources and a Deduplicated badge

If you only see one source, check that the Pixel ID and CAPI token are saved in Arketa and try again without an ad blocker.

What Arketa sends to Meta

Arketa fires standard Meta events from your booking page (browser Pixel + CAPI):

EventWhen it fires
ScheduleClient books a class
PurchaseClient buys a pricing option, on-demand video, or pack
StartTrialClient starts a subscription on a free trial
SubscribeFirst paid invoice succeeds for a subscription
SubscriptionRenewed (custom)Each renewal invoice, if Track subscription renewals (LTV) is enabled

That data powers:

  • Ad optimization — Meta finds more people like your actual buyers
  • Retargeting — build audiences from people who visited but did not convert
  • Revenue reporting — tie ad spend to bookings and memberships, not just clicks

Meta Lead Ads

Bring your Facebook and Instagram lead ad submissions straight into Arketa. Every time someone fills out one of your Instant Forms, Arketa creates a client with their name, email and phone, marks the source as Facebook, and runs the automations you already have for new leads. No Zapier and no spreadsheets.

What you'll need

  • Full control of the Facebook page your ads run from. Partial access isn't enough to connect it
  • At least one Instant Form on that page. You don't need a running ad to connect or to test it
  • An email question on the form. Arketa adds each lead as a client by their email, so a lead without one isn't added

Connect your page

Open the Meta integration

Go to Settings → Integrations → Meta and click Connect next to Meta Lead Ads. You can also get there from Marketing → Lead Management → Setup → Meta Lead Ads.

The Setup menu in Lead Management with the Meta Lead Ads option

Log in with Facebook and pick your page

A Facebook window opens. Log in and choose the page your lead ads run from. If you manage more than one page, Arketa asks which one to connect.

The Choose a Facebook page dialog with one page selected

Choose a lifecycle stage

Pick the stage new leads from Meta start in. Until you pick one, they start on your studio's default stage, or on your first stage if you don't have a default, so every lead lands on a stage. Leads placed on a stage also trigger your Client transitioned to lifecycle stage automations.

If your studio has no lifecycle stages yet, the card shows a red banner instead. Leads still come in, without a stage, until you add one in Lifecycle Settings.

The Meta Lead Ads card showing Connected, the page, Disconnect and the lifecycle stage

Once the card says Connected, every new Instant Form submission shows up in Marketing → Lead Management within seconds, with Facebook as the lead source.

Lead Management with leads whose Lead Source is Facebook

Each lead's profile shows where it came from, along with the name, email and phone from the form.

New leads also show up for a week in the New leads tab of the Notification Center on your Home page, so you can see them come in without opening Lead Management.

A client profile with Lead source facebook and Created source Facebook lead ad

Check Leads Access

Meta lets a business choose which apps receive the leads from its pages. This setting is called Lead Access Manager, and it lives in Meta Business Suite under Settings → Integrations → Leads Access.

  • If it's off (the default), every app connected to your page receives its leads. You don't need to do anything.
  • If it's on, Meta only sends leads to the apps on its list. Select your page, click Assign CRMs and add Arketa Marketing Suite. Until you do, the card in Arketa says Connected but no leads arrive.

Only someone with full control of your business in Meta can change this. Arketa Marketing Suite appears in the list once your page is connected in Arketa.

Not sure if it's on? Open the Lead Ads Testing Tool and choose your page. If Page Diagnostics shows a warning on Arketa Marketing Suite that says App does not have leads permission, add it in Leads Access.

Follow up with an automation

To follow up with every lead from Meta automatically, go to Marketing → Automations, create an automation and pick New lead added as the trigger with Lead source Facebook. Then add what should happen next, like a welcome email, a text, a tag or a task for your front desk.

An automation trigger set to New lead added with Lead source Facebook

An automation that adds a tag to every new Facebook lead

Test it

  1. Open Meta's Lead Ads Testing Tool
  2. Choose your page and your form
  3. Click Preview form to fill in the form yourself, for example with your own email to see your automations reach you. Or click Create lead to send one with Meta's sample data (like test@meta.com), which won't reach a real person
  4. The test lead shows up in Arketa with source Facebook

The Lead Ads Testing Tool with a page and form selected, and the Create lead, Delete lead and Preview form buttons

An Instant Form opened with Preview form and filled in with a sample lead

Use an email that isn't already one of your clients, or Arketa updates that client instead of adding a new lead. Each form takes one test lead at a time, so click Delete lead in the tool before sending another. If Preview form opens on Thanks, you're all set, the form already has a test lead: click Delete lead, reload the tool and open it again.

If it stops working

If Meta removes our access to your page, the card shows Connection lost. Click Reconnect and log in with Facebook again.

The Meta Lead Ads card showing Connection lost with a Reconnect button

Frequently asked questions

Was this helpful?