Per-Supplier Meta Pixel Wiring
Wire each Lead Distro AI supplier to its own Meta pixel for isolated CAPI conversion attribution. Multi-tenant agency pattern, setup steps, and FAQs.
Last updated:
What This Does
Wire each supplier in Lead Distro AI to a specific Meta pixel. Conversion events for that supplier's leads fire on that pixel — and only that pixel. Lets multi-account agencies isolate ad-optimization signals so Client A's pixel learns from Client A's traffic only.
Why Isolate Pixels?
- Multi-tenant agencies — each client has their own Meta ad account and pixel. CAPI events should fire on the client's pixel, not yours.
- Vertical separation — running personal injury + home services on the same Lead Distro AI instance? Pixel separation prevents Meta from cross-contaminating audience signals between unrelated verticals.
- A/B test isolation — test campaign vs control campaign with different pixels lets you measure which campaign's CAPI signal improves Meta's optimization more.
- Compliance — some clients require their CAPI data stays on their pixel, never your agency-level pixel. Per-supplier wiring satisfies this contractually.
Setup
- Connect the relevant Meta ad accounts to Lead Distro AI (Settings → Integrations → Meta Ads).
- On the supplier's detail page, open the Meta Integration tab.
- Select the Meta pixel from the dropdown (populated with all pixels accessible from the connected accounts).
- Enter the CAPI access token for that pixel (generated in Meta Events Manager).
- Map lead outcomes (accepted, sold, returned, paid) to Meta conversion events (Lead, Purchase, etc.).
- Save. Conversion events for this supplier's leads now fire on the selected pixel.
Each pixel has its own access token — don't reuse tokens across pixels. Generate a new token per pixel in Meta Events Manager: **Settings → Conversions API → Generate access token**.
Multi-Tenant Pattern (Agency)
Run one Lead Distro AI supplier per client. Wire each supplier to its client's pixel + token. Lead distribution to buyers still uses standard distribution methods — only the CAPI side is isolated. Reporting shows blended performance in your dashboard, while each client sees their own attribution in their own Meta Ads Manager.
Frequently Asked Questions
Why use per-supplier Meta pixel wiring instead of one shared pixel?
Three reasons: (1) Multi-tenant agencies need each client's CAPI events to fire on the client's pixel, not the agency's. (2) Meta's algorithm learns per-pixel — cross-contaminating audiences from unrelated verticals (legal + home services) hurts both. (3) Some clients contractually require their conversion data stay on their pixel.
How many pixels can I wire to a single Lead Distro AI account?
Unlimited. Each supplier wires to one pixel; you can have hundreds of suppliers each on a different pixel. The connection is to the supplier, not the account — agencies running 50+ clients on one Lead Distro AI instance commonly have 50+ pixel wirings.
Can one supplier fire events to multiple pixels?
Not directly — each supplier has one pixel assignment. For multi-pixel attribution (e.g., events fire on both your agency pixel AND the client's pixel), create two suppliers, one per pixel, and split the supplier's traffic across them (e.g., duplicate the supplier and route 50/50).
What happens to CAPI events if I change a supplier's pixel mid-campaign?
Events for new leads (after the change) fire on the new pixel. Events for already-ingested leads (before the change) stay attributed to the original pixel — Lead Distro AI doesn't retroactively re-fire CAPI events on a different pixel. The cutover is clean: switch pixels at the moment your client wants it; events split at that moment.
Do per-supplier pixels affect lead distribution to buyers?
No. Pixel wiring is a CAPI-only setting — it affects how conversion events are sent to Meta, not how leads are distributed to buyers. Buyer-side delivery (webhooks, automations, returns) is independent of pixel configuration.
Can I see which pixel fired the conversion event for a specific lead?
Yes — open the lead detail page in the dashboard. The Meta CAPI tab shows every event attempted for that lead, including the pixel ID, the event name, the Meta API response, and any retry attempts. Useful for diagnosing 'Why didn't this conversion show in my client's Meta Ads Manager?' questions.
Related Articles
Supplier Basics
Configure lead suppliers in Lead Distro AI: API key generation, cost-per-lead tracking, source attribution, ingestion endpoints, and supplier-level reporting for every traffic source.
Meta Ads Integration
Connect Lead Distro AI with Meta Ads: sync ad spend to campaigns, track conversions via the Conversions API, connect Facebook and Instagram lead forms, and attribute revenue to traffic sources.
Supplier Cost Modes
Lead Distro AI supplier cost modes: Fixed, Variable (Meta Ads), and Revenue Share. How each calculates per-lead cost, when to use which, and FAQs for accurate profit tracking.
If you have any questions, send us an email at support@leaddistro.ai