Paid
Meta Ads integration for digital marketing agencies
Meta Ads is where iOS 14.5's Apple privacy changes hit hardest — pixel-only tracking lost most of its accuracy, and Conversions API (CAPI) became the only reliable conversion-feedback path. Agencies that don't track CAPI configuration explicitly per client ship campaigns optimising against degraded pixel data and quietly burn budget. Modeling Meta pixels and CAPI endpoints as typed objects is how mature agencies catch CAPI misconfigurations before they affect spend.
How Phloz models Meta Ads
Every Meta Ads concept that matters for digital marketing agency operations is a typed object in the tracking map. Health state per node, audit cadence, and graph relationships to every other tracking-system node it touches — so a broken tag or misconfigured property is findable in seconds across your full book of clients.
- Meta pixel as a typed node with pixel ID, data quality score, primary domain
- Conversions API endpoint as a separate node, linked to the pixel — agencies see "is CAPI live?" at a glance
- Custom audiences + lookalike audiences linked to the pixel they're built from
- Match rate + EMQ (Event Match Quality) score tracked per pixel, with verification cadence
Common Meta Ads configuration gotchas
The configuration mistakes agencies most often make with Meta Ads, surfaced here as a checklist agencies can run at every client onboarding. Honest, useful, not gated behind a sales pitch — these are real and you should audit for them regardless of whether you use Phloz.
- CAPI deduplication: agencies enable CAPI without configuring the deduplication parameter (event_id), causing Meta to count the same event twice. Always set event_id when CAPI fires alongside pixel.
- Customer Information parameters: CAPI requires hashed PII (email, phone) to match users. Agencies often send unhashed data, which Meta rejects silently. Verify the SHA-256 hash format at every CAPI rollout.
- Pixel firing on iframe pages: cross-domain checkout flows (e.g., Shopify Plus checkout) need explicit pixel installation on the iframe domain. Agencies miss this and lose checkout conversions.
At launch (V1)
Meta pixels + Conversions API endpoints as typed nodes. Link to audience nodes for retargeting graphs.
Coming (V2)
Meta Marketing API sync: pixel events received, data quality score, CAPI match rate.
Why we built the integration this way
Most agency CRMs treat third-party tools as text fields: "GA4 Property ID" goes in a custom column on the client record. That works at one or two clients and breaks at five. With every Meta Adsobject as a typed tracking node, the agency can answer questions like "which clients have a misconfigured Meta Adssetup?" or "which Meta Adsconfigurations changed last quarter?" from a single graph query.
The V1 surface is intentionally manual — agencies enter the configuration at onboarding rather than auto-importing. This forces explicit verification at the exact moment the agency takes over the client's tracking, catching most of the commonGotchas listed above before they become production issues. V2 will add API-based sync where the underlying platform supports it; we won't add sync where the underlying API doesn't expose the right data.
When to use this in your client onboarding flow
The standard pattern for digital marketing agencies running Phloz: at every new client onboarding (see the client onboarding audit use case), spend 30 minutes documenting the client's Meta Adsconfiguration as Phloz nodes — pixel IDs, tracking-code installations, conversion-action setup, the relationships to other systems. Verify each one fires by triggering a test event. Set the "verified at" timestamp on each node. Schedule a quarterly verification task on the agency engineer who owns tracking.
The 30 minutes at onboarding catches 90 percent of the tracking issues that would otherwise surface during the first month of campaign optimisation — when finding them would mean a refund conversation. See the broader tracking infrastructure map use case for the agency-wide pattern.
Frequently asked questions
The three questions agencies ask most often about Phloz's Meta Ads integration. Honest answers — same data we'd give a friend evaluating the integration.
- Does Phloz integrate with Meta's Aggregated Event Measurement (AEM)?
- AEM configuration is tracked as part of the Meta pixel node's metadata in V1. Each domain's 8-event configuration is documented as a custom field on the pixel. V2 will add Meta Marketing API sync for live AEM event prioritisation.
- Can Phloz manage Business Manager accounts?
- Yes — Meta Business accounts are modelled as a parent node, with child pixels, ad accounts, and CAPI endpoints linked underneath. For agencies onboarding new clients, the Business Manager node is where the partnership-status verification (admin / advertiser / standard access) lives.
- How does Phloz handle iOS 14.5 SKAdNetwork data?
- SKAdNetwork conversion values are tracked at the campaign level, not the pixel level — so they live as custom fields on the Meta ad account node rather than the pixel. The 64 conversion-value postback configuration is documented per app for agencies running mobile-app campaigns.
Other integrations
Other paid and adjacent tools Phloz integrates with.
14 days free · No credit card · Starter tier free forever