How to Connect Perspection to Meta Conversions API (CAPI) for Server-Side Tracking

How do you connect Perspection to Meta Conversions API?

To connect Perspection to Meta CAPI, open the Perspection dashboard, navigate to Connectors then Destinations, and select Meta (Facebook). Enter the Pixel ID from Meta Events Manager Data Sources Settings and paste the Access Token from Events Manager Settings Conversions API. Perspection validates the connection by sending a test PageView event to the Meta Graph API v21.0 endpoint.

Step-by-step: Generate Meta CAPI credentials

1. Open Meta Events Manager and select the correct Business Manager account.

2. Click Data Sources in the left sidebar and select the Pixel or Dataset associated with the ad account receiving conversions.

3. Navigate to Settings and copy the Dataset ID (also called the Pixel ID). The Pixel ID follows a 15-digit numeric format, for example 123456789012345.

4. Scroll down to the Conversions API section and click Generate Access Token. Meta generates a long-lived system user token starting with EAA. Store the Access Token securely -- Meta does not display the Access Token again after the Access Token is generated.

5. When Events Manager prompts for a setup method, select Set up manually. Do not select Datahash, Gateway, or Partner integration.

Step-by-step: Configure the destination in Perspection

1. Log into the Perspection dashboard and select the workspace that should send events to Meta.

2. Open Connectors > Destinations from the left navigation.

3. Under Available Destinations, click the Meta (Facebook) card labeled "Conversions API."

4. Paste the Pixel ID into the Pixel ID field.

5. Paste the Access Token into the Access Token field.

6. (Optional) Enter a Test Event Code such as TEST12345 for validation in Meta Events Manager before going live. Remove the Test Event Code after validation -- a stale Test Event Code silently routes all production events to the Meta Test Events tool instead of counting the events as real conversions.

7. (Optional) Enter a Baseline Pixel ID to compare Perspection-recovered conversions against the existing tracking setup. Perspection uses the Baseline Pixel ID to calculate how many conversions the old pixel missed.

8. Toggle the Live switch to enabled.

9. Click Save. Perspection creates the destination and displays a "Live" health badge.

10. Click Test to send a validation PageView event to the Meta Graph API. Perspection reports the connection test result and latency in milliseconds.

Required and optional fields

What data does Perspection send to Meta CAPI?

Perspection sends every server event to Meta CAPI with the event name, Unix timestamp, action_source set to "website" for browser-originated events, SHA-256-hashed email and phone, Facebook Browser ID (fbp), Facebook Click ID (fbc), client IP address, user agent, external_id, and custom data including value, currency, content_type, content_ids, and order_id for purchase events.

Perspection transforms raw events from the Perspection SDK into the Meta CAPI payload schema before dispatch. The Perspection Meta connector (running on the Perspection dispatch worker) maps each field to the exact parameter name Meta expects:

User data parameters

Event name mapping

Perspection automatically translates common event names to Meta standard events:

The Perspection Meta connector automatically skips internal events that have no analytics value for Meta, including identify, session_start, page_hidden, javascript_error, and consent update events. Custom event names that do not match the mapping table pass through to Meta unchanged.

Custom data for purchase events

For purchase events, Perspection automatically structures the custom_data payload:

{
  "value": 149.99,
  "currency": "USD",
  "content_type": "product",
  "content_ids": ["SKU-001", "SKU-002"],
  "contents": [
    { "id": "SKU-001", "quantity": 1, "item_price": 99.99 },
    { "id": "SKU-002", "quantity": 2, "item_price": 25.00 }
  ],
  "order_id": "ORD-20260227-001"
}

{
  "value": 149.99,
  "currency": "USD",
  "content_type": "product",
  "content_ids": ["SKU-001", "SKU-002"],
  "contents": [
    { "id": "SKU-001", "quantity": 1, "item_price": 99.99 },
    { "id": "SKU-002", "quantity": 2, "item_price": 25.00 }
  ],
  "order_id": "ORD-20260227-001"
}

{
  "value": 149.99,
  "currency": "USD",
  "content_type": "product",
  "content_ids": ["SKU-001", "SKU-002"],
  "contents": [
    { "id": "SKU-001", "quantity": 1, "item_price": 99.99 },
    { "id": "SKU-002", "quantity": 2, "item_price": 25.00 }
  ],
  "order_id": "ORD-20260227-001"
}

How does Perspection calculate Meta Event Match Quality?

Perspection calculates a weighted Event Match Quality score from 0 to 100 for every event before dispatching to Meta CAPI. The EMQ score uses six factors: email hash (25%), phone hash (20%), external_id (15%), browser data (15%), address data (15%), and custom data completeness (10%). Scores at 80+ rate "excellent"; scores below 50 trigger critical warnings.

The Perspection Meta connector runs the EMQ calculation inline before every dispatch call. The Perspection EMQ analyzer evaluates 15 individual parameters across two categories:

Hashed PII parameters (weighted by matching value)

Unhashed identifier parameters

EMQ rating thresholds

The Perspection dashboard displays a Data Completeness coaching panel that aggregates EMQ analysis across the last 7 days of dispatched events. The coaching panel shows the completeness distribution (excellent/good/fair/poor), identifies the most common missing parameters, and provides prioritized recommendations to increase the EMQ score.

EMQ thresholds by source

Perspection applies different EMQ warning thresholds depending on the event source, because different sources have different data availability:

Events below the threshold still dispatch to Meta -- Perspection never silently drops events. The Perspection connector logs a warning with coaching recommendations when the EMQ score falls below the threshold.

What is CPAS and how does Perspection support Collaborative Ads?

CPAS (Collaborative Performance Advertising Solution) is Meta's official partnership program with Shopee and Lazada. CPAS enables product catalog sync from marketplace to Facebook, conversion tracking without strict EMQ requirements, and Dynamic Product Ads from marketplace catalog data. Perspection supports CPAS by relaxing EMQ validation for marketplace events and dispatching catalog-linked conversions to Meta.

Marketplace events from Shopee and Lazada lack browser data because the purchase occurs inside the Shopee or Lazada app, not in a web browser. Without CPAS, Shopee events typically score 39/100 EMQ and Lazada events score 69/100 EMQ -- both below the standard 70 threshold. CPAS solves the low-EMQ problem by linking the marketplace product catalog directly to the Facebook ad account.

How CPAS works with Perspection

1. The marketplace (Shopee or Lazada) shares the product catalog with the advertiser's Facebook Business Manager.

2. The advertiser accepts the catalog share and creates a dedicated ad account for CPAS campaigns.

3. In Perspection, the workspace administrator enables the CPAS toggle for Shopee or Lazada in the Meta destination configuration.

4. When Perspection receives a marketplace order event, the Perspection Meta connector detects the source_system field (either shopee or lazada) and activates CPAS mode.

5. In CPAS mode, Perspection dispatches the event to Meta without blocking on low EMQ scores. Meta uses the shared catalog to attribute the conversion.

CPAS configuration fields

CPAS requirements

• Dedicated ad account: CPAS requires a separate Facebook ad account. Do not use an existing ad account.

• Minimum ad spend: Varies by region, typically $1,000-$5,000 per month.

• Approval timeline: 2-3 weeks from application for both Shopee and Lazada.

• Eligibility: All marketplace and ShopeeMall sellers (Shopee); no counterfeit products (Lazada).

While waiting for CPAS approval, Perspection still dispatches marketplace events to Meta. The events may have lower match rates without CPAS catalog linking, but Perspection never drops marketplace conversion data.

How does Perspection deduplicate browser and server events?

Perspection sends a unique event_id with every server-side event dispatched to Meta CAPI. Meta deduplicates by matching event_id plus event_name against browser pixel events within a 48-hour window. When both browser and server signals carry the same event_id, Meta counts the event exactly once.

The deduplication mechanism

The Perspection SDK generates a unique event_id (UUID v4 format) at the moment the SDK captures each event in the browser. The same event_id is sent in two directions:

1. Browser path: The Meta Pixel (if installed alongside Perspection) fires the event with the event_id directly to Meta from the browser.

2. Server path: The Perspection SDK sends the event to the Perspection ingestion API, which processes, enriches, and dispatches the event to Meta CAPI with the same event_id.

Meta receives both signals and matches the signals by event_id + event_name. Meta keeps the server-side event (which contains richer user data from Perspection identity resolution) and discards the duplicate browser event.

Why deduplication matters

Without deduplication, advertisers running both the Meta Pixel and Perspection server-side tracking would see inflated conversion counts. A single purchase would appear as two purchases in Meta Ads Manager, doubling reported ROAS and corrupting campaign optimization signals. The event_id deduplication ensures Meta counts exactly one conversion per actual user action.

Deduplication rules

How do you verify Meta CAPI events in Events Manager?

To verify Meta CAPI events, enter a Test Event Code into the Perspection Meta destination, trigger a test conversion on the website, then check the Test Events tab in Meta Events Manager. Meta displays each server event with parameters and warnings. Remove the Test Event Code after verification to prevent production events from routing to the test tool.

Step-by-step: Verify with Test Event Code

1. Open Meta Events Manager and select the correct Pixel / Dataset.

2. Click the Test Events tab.

3. Copy the Test Event Code displayed at the top of the Test Events tab (formatted as TEST followed by 5 alphanumeric characters, for example TEST12345).

4. In the Perspection dashboard, navigate to Connectors > Destinations and expand the Meta (Facebook) destination card.

5. Paste the Test Event Code into the Test Event Code field and click Save.

6. Open the website connected to the Perspection workspace in a separate browser tab.

7. Perform a tracked action -- for example, view a product page (triggers ViewContent), add an item to cart (triggers AddToCart), or complete a purchase (triggers Purchase).

8. Return to Meta Events Manager Test Events tab. Within 30 seconds, the test event should appear showing the event name, timestamp, user data parameters (em, ph, fbp, fbc, external_id, client_ip_address, client_user_agent), and custom data.

9. Verify the event parameters match expectations. Meta highlights any parameters with formatting warnings.

10. After successful verification, return to the Perspection dashboard and clear the Test Event Code field, then click Save. A stale Test Event Code causes all production events to route to the Test Events tool, preventing the events from counting as real conversions.

Step-by-step: Verify in the Overview tab

1. In Meta Events Manager, click the Overview tab for the Pixel / Dataset.

2. Filter by Connection Method > Server to isolate CAPI events.

3. Check the event volume graph to confirm server-side events are arriving alongside (or replacing) browser pixel events.

4. Click any individual event type (such as Purchase) to see the Event Match Quality score Meta has assigned -- Meta calculates Event Match Quality independently using Meta proprietary algorithms, but the Meta EMQ score should correlate with the Perspection EMQ score displayed in the Destination Health dashboard.

Step-by-step: Use the Perspection connection test

1. In the Perspection dashboard, expand the Meta destination card.

2. Click the Test button. Perspection sends a minimal PageView event to the Meta Graph API v21.0 endpoint.

3. Perspection reports the result as "Connection test successful!" with the response latency in milliseconds, or displays the specific Meta API error message if the connection fails.

4. Common failure causes: expired Access Token, incorrect Pixel ID, insufficient permissions on the system user token, or network connectivity issues.

How does Perspection handle rate limits and retries for Meta CAPI?

The Meta Conversions API enforces 200 requests per second per Pixel ID. Perspection tracks the rate limit counter internally and pauses dispatch when remaining capacity reaches zero, resuming after the window resets. For transient failures (HTTP 5xx, 429), the Perspection Meta connector retries with exponential backoff. Non-retriable errors (HTTP 4xx) route to the Dead Letter Queue.

Rate limiting

The Perspection dispatch worker maintains a per-destination rate limit tracker. When the Meta API returns rate limit headers, the Perspection Meta connector updates the rateLimitRemaining counter and rateLimitResetTime timestamp. If an event dispatch attempt detects zero remaining capacity, the Perspection Meta connector returns a rate limit error and the event is re-queued for dispatch after the reset window.

Retry behavior

Timeout

The Perspection Meta connector enforces a 5-second timeout per API call to the Meta Graph API. If the Meta API does not respond within 5 seconds, the request is aborted and retried.

Privacy compliance

Perspection supports Meta Limited Data Use (LDU) for privacy compliance. When consent fields indicate restricted data processing requirements (ad_storage denied or ad_user_data denied), the Perspection Meta connector automatically applies data_processing_options: ["LDU"] to the Meta event payload.

Methodology

All Meta CAPI configuration steps and event mapping tables in this guide were verified against the Perspection production dashboard and live Meta Events Manager test events as of February 2026.

"The single highest-impact action for improving Meta CAPI attribution is capturing the _fbc cookie -- the Facebook Click ID. The _fbc parameter carries a weight of 2.5 in the EMQ scoring model, the highest of any single parameter. When a user clicks a Facebook ad, the FBCLID appends to the landing page URL and is stored in the _fbc cookie. Perspection's first-party domain setup preserves the _fbc cookie beyond Safari ITP limits, which is why advertisers using Perspection first-party domains see 20-40% higher attributed conversions compared to standard browser pixel implementations." -- Perspection Engineering Team

How does Perspection map events to Meta CAPI parameters?

Perspection provides a visual and JSON-based event mapping editor that customizes how Perspection events translate to Meta CAPI events. The mapping editor supports event name remapping, property remapping via dot-notation paths, event ignoring to skip specific events, and toggling between drag-and-drop visual mode and raw JSON mode.

Beyond the default event name mapping, Perspection provides a visual and JSON-based event mapping editor for customizing how Perspection events translate to Meta events. The mapping editor supports:

1. Event name remapping: Map a custom source event name (for example product_viewed) to a specific Meta event name (for example ViewContent).

2. Property remapping: Map source properties to destination-specific custom data keys using dot-notation paths (for example properties.price mapped to value).

3. Event ignoring: Mark specific source events to skip dispatch to Meta entirely.

4. Visual and JSON modes: Toggle between a drag-and-drop visual editor and a raw JSON editor for advanced configurations.

To configure event mapping, expand the Meta destination card in the Perspection dashboard, scroll to the Event Mapping section, and add mapping rules. Save the mapping configuration separately from the destination credentials.

Sources & References

1. Meta for Developers, "Conversions API - Get Started," https://developers.facebook.com/docs/marketing-api/conversions-api/get-started

2. Meta for Developers, "Conversions API - Parameters," https://developers.facebook.com/docs/marketing-api/conversions-api/parameters

3. Meta for Developers, "Conversions API - Deduplicate Events," https://developers.facebook.com/docs/marketing-api/conversions-api/deduplicate-pixel-and-server-events

4. Meta for Developers, "Event Match Quality - Best Practices," https://developers.facebook.com/docs/marketing-api/conversions-api/best-practices

5. Meta for Business, "Collaborative Performance Advertising Solution (CPAS)," https://www.facebook.com/business/cpas

6. Apple Developer Documentation, "App Tracking Transparency," https://developer.apple.com/documentation/apptrackingtransparency

7. WebKit, "Intelligent Tracking Prevention," https://webkit.org/tracking-prevention/

8. Perspection Product Guide, "Event Match Quality Coaching," /library/event-match-quality-guide

9. Perspection Product Guide, "Destination Health Monitoring," /library/destination-health-failed-events-guide

10. Perspection Product Guide, "First-Party Domain Setup," /library/first-party-tracking-domain-guide