Skip to content
Apex

Meta Ads · Both

Meta ads measured against real outcomes — CAPI loop coming soon. Facebook, Instagram, and WhatsApp spend, measured against real outcomes.

Apex imports your Meta cost, impressions, and audience data today and reports them alongside your downstream revenue. Outbound Meta Conversions API delivery — Apex writing hashed first-party conversions back so Meta's bidding learns from Stripe purchases and in-app revenue — is on the near-term roadmap.

Start freePricing

No credit card to start.

What teams use it for

The questions people actually ask.

  • How do I set up Meta Conversions API without paying for Segment or building a server-side stack?

    Apex is being built as the server-side stack. Today the OAuth flow and pixel/ad-account mapping are wired up. The outbound CAPI delivery itself — server-to-server event upload, hashed-identifier handling, event-ID deduplication against the pixel, signal-loss rules — is on the near-term roadmap and the first item teams are migrating off Segment/Stape.io for.

  • How do I measure iOS 14+ installs under ATT and keep Meta bidding optimised?

    The Apex Mobile SDK collects SKAN conversion-value signals and ATT status today. Once outbound Meta CAPI ships (near-term roadmap), install and in-app revenue events will fire to Meta server-side, restoring the signal ad blockers and iOS 14 currently eat. Pre-roadmap, Apex's read-side Meta integration still ingests AEM-attributed campaign data.

  • Can Meta's bidding optimise against real revenue from Stripe or HubSpot closed deals?

    This is the design intent of the outbound CAPI integration on our near-term roadmap. When it ships, every Stripe subscription start, HubSpot deal close, and in-app purchase will fire a matching CAPI event to Meta with the actual revenue value and a hashed customer identifier — so Meta's Advantage+ bidding prioritises audiences that produce paying customers instead of top-of-funnel form fills.

What flows in

What Apex receives from Meta Ads.

From Meta Ads

  • Campaign, ad set, and ad-level cost, impressions, and clicks
  • Audiences, placements, and device breakdowns
  • Conversions and custom conversions reported by the pixel
  • Install and app event reporting from Meta's SDK where applicable

What it powers

Where this data shows up.

  • Mobile Measurement

    Install-to-revenue attribution for iOS and Android that works under SKAN and Meta's Aggregated Event Measurement.

  • Communications

    Export CAPI events so Meta's bidding learns from Apex's qualified outcomes instead of pixel-only events. (Outbound CAPI is on the near-term roadmap.)

  • Intelligence

    Spend efficiency models use Meta impression and click data alongside revenue to flag creative fatigue and audience saturation.

Setup · OAuth 2.0

Connect Meta Ads.

Connect your Meta Business account via OAuth and choose the ad accounts and pixels you want Apex to read from. Outbound CAPI delivery (event mapping, identifier hashing, pixel dedupe, signal-loss handling) is on the near-term roadmap — the OAuth scope is requested and validated today so that integration ships as a flip-the-switch upgrade.

Setup docs · All integrations

FAQ

Meta Ads and Apex, answered.

  • Why is the Meta Conversions API a big deal?

    Client-side pixels get eaten by ad blockers (uBlock, Privacy Badger), Safari ITP, iOS 14 App Tracking Transparency, and the growing set of browser privacy features. Meta's Conversions API runs server-side, so the events reach Meta regardless of client-side restrictions. The industry baseline: once CAPI is in place, Meta sees 30-50% more conversions and bids much more accurately. Apex's CAPI integration is on the near-term roadmap.

  • Do I still need the Meta pixel if I use the Conversions API?

    Usually yes — the pixel becomes a complement to CAPI rather than the primary signal once both are in place. Apex's outbound CAPI design (on roadmap) deduplicates against the pixel using Meta's standard event_id scheme, so Meta counts each conversion once. Today, only the pixel side carries conversions.

  • What events should I send to Meta?

    Any downstream Apex event that correlates with real customer value: Stripe subscription starts, trial-to-paid conversions, HubSpot deal closes, in-app purchases, feature activations. Send high-intent events sparingly (Meta bidding learns fastest with clear signal). The event mapping UI ships alongside the outbound CAPI integration on the near-term roadmap.

  • How does Apex handle hashed identifiers for matching?

    The outbound CAPI integration (on roadmap) will hash email, phone, and external_id with SHA-256 before sending to Meta, per the CAPI spec. Raw values never leave Apex's servers. Meta uses the hashed identifiers to match server-side events to their user graph. Hashing infrastructure is being built as part of the shared outbound-S2S core; talk to us if CAPI is a near-term gate.

  • Can this replace Stape.io or CAPIG?

    That's the design intent. Stape.io and similar server-side GTM proxies solve the forwarding problem alone; Apex's outbound CAPI (on the near-term roadmap) solves it as part of a broader attribution + experimentation platform. Pre-roadmap, you'll still need Stape or similar if you can't wait.

  • Does it support WhatsApp Business and Instagram ads too?

    Yes. The Meta Ads integration covers Facebook, Instagram, Messenger, and WhatsApp placements, they all share the same ad manager and Conversions API endpoint. Cost data and conversion events flow for every placement type.

  • What about Meta App Events / mobile conversion feedback?

    Mobile install and in-app events are captured by the Apex Mobile SDK into your Apex workspace today. Automatic server-side delivery to Meta (CAPI / App Events–equivalent pathways) is on the near-term roadmap alongside the shared outbound-S2S core; until then, do not assume Meta receives conversions from Apex without your own forwarding layer.

Your move

Connect Meta Ads this week.

Start free, then attach this source. One live feed is enough to start the loop.

Start freeView pricing