Clarity Diamonds — Meta Conversions API (CAPI) Setup Guide

Date: 2026-03-15
Status: Planning
Related: Launch Plan — First 30 Days, Meta Ads Strategy

Why CAPI + Pixel (Not Pixel-Only)

The Meta Pixel fires from the browser. CAPI fires from your server. You need both because:

• iOS 14.5+ and browser privacy — Safari ITP, Firefox ETP, and ad blockers strip or block pixel fires. You lose 20-40% of conversion data with pixel-only.
• Meta's algorithm needs signal — fewer events = worse optimisation = higher CPAs. Meta downgrades delivery for advertisers with poor data quality.
• Event Match Quality (EMQ) — Meta scores how well it can match your events to real users. CAPI passes hashed email, phone, and name directly, which the pixel can't reliably capture. Higher EMQ = better audience matching = lower costs.
• Required for Advantage+ — Meta's best-performing campaign types lean heavily on strong server-side signal.
• Deduplication — Meta deduplicates pixel + CAPI events via event_id, so you get the best of both without double-counting.

Bottom line: Pixel-only is fine for Month 1 launch (don't let CAPI block going live). But set up CAPI as soon as possible after launch — ideally within the first 2 weeks.

Events to Set Up

These match the pixel events in the Launch Plan — First 30 Days plus additional server-side signals.

Core Events (Must Have)

Note: PageView is pixel-only — no need to send it server-side. The pixel handles it fine, there's no customer data to enrich, and losing a few pageviews to ad blockers doesn't affect optimisation.

Recommended Events (Add When Ready)

Events You Don't Need Yet

When to add Purchase: If you ever add online ordering or a deposit payment flow, add Purchase with value and currency parameters immediately. This unlocks value-based optimisation in Meta.

Customer Information Parameters

CAPI's advantage over the pixel is passing hashed customer data for better matching. Send as many of these as you have:

Important: All personal data must be SHA-256 hashed before sending. Most integration tools handle this automatically. Never send plaintext personal data to the API.

Critical: Always pass fbp and fbc cookies from the browser to your server. These link CAPI events to pixel events for deduplication and connect conversions to ad clicks.

Deduplication

When running both pixel and CAPI, Meta deduplicates using event_id. Every event needs:

1. Same event_name — pixel and CAPI must use identical event names
2. Same event_id — generate a unique ID (e.g., UUID) when the event occurs, send it via both pixel and CAPI
3. Within 48 hours — CAPI event must arrive within 48 hours of the pixel event

Example flow:

1. User submits concierge form
2. Browser fires: fbq('track', 'Lead', {event_id: 'abc-123'})
3. Server fires: CAPI Lead event with event_id: 'abc-123'
4. Meta receives both, deduplicates on event_id, keeps the best-matched one

If deduplication isn't set up correctly, Meta will double-count conversions — inflating your numbers and messing up optimisation.

Implementation Options

Option 1: Platform Native (Easiest)

If claritydiamonds.au is on Shopify, WordPress/WooCommerce, or Squarespace:

• Most platforms have a built-in CAPI integration — it's a toggle or plugin
• Shopify: Settings → Customer Events → Meta CAPI (automatic)
• WordPress: Use the official "Meta for WordPress" plugin or "PixelYourSite Pro"
• Squarespace: Limited CAPI support — may need Option 2

Pros: No dev work, handles deduplication automatically
Cons: Less control over which events fire and what data is passed

Option 2: Gateway (Recommended for Control)

Use a server-side tagging platform:

• Stape.io — server-side Google Tag Manager hosting, Meta CAPI connector
• Server-side GTM — Google's free server-side container (requires hosting)

Pros: Full control, works with any website platform, handles deduplication
Cons: Moderate setup, ~$10-20/month hosting cost (Stape)

Option 3: Direct API (Most Control)

Implement CAPI directly using Meta's Marketing API:

• Requires server-side code (Node.js, Python, PHP, etc.)
• Full control over every parameter
• Best for custom setups

Pros: Maximum control and data quality
Cons: Requires dev work, you manage deduplication

Recommendation for Clarity Diamonds

Start with Option 1 if your platform supports it. Move to Option 2 (Stape + server-side GTM) if you need more control or your platform's native integration doesn't pass enough customer data.

EMQ Score Targets

After setup, check Event Match Quality in Meta Events Manager:

Where to check: Events Manager → Data Sources → Your Pixel → Event Match Quality tab

Setup Checklist

• Choose implementation option (platform native, gateway, or direct API)
• Set up CAPI for ViewContent event
• Set up CAPI for Lead event (concierge form) — do this first
• Set up CAPI for Contact event
• Set up CAPI for CompleteRegistration event (guide/quiz signups)
• Verify deduplication: event_id matches between pixel and CAPI for each event
• Verify customer parameters: email and fbp/fbc cookies passing on all form events
• Check EMQ score in Events Manager (target: 6+)
• Test using Events Manager → Test Events → Server Events tab
• Monitor for 48 hours — confirm no double-counting in Events Manager

Timeline

CAPI setup is a one-time investment that improves every campaign you run. The sooner it's live, the better Meta can optimise your $1,000/month budget.