Meta Integration

Meta

Configure Meta Pixel/Conversions-style forwarding from Selwise events with mapping and filters.

Audience: Paid social and performance marketing teams using Meta events for optimization.

Critical: Meta provider key is meta and is configured via PUT /api/v1/sites/:siteId/integrations/meta.

Integrations OverviewEvent MappingOperations

Who This Page Is For

Use this page when you need consistent event forwarding to Meta with configurable mapping, filtering, and troubleshooting.

Quick Start (2-5 Minutes)

1

Configure pixel settings

Set pixel ID, access token, and advanced matching options.

PUT /api/v1/sites/:siteId/integrations/meta

2

Map required conversion events

Align Selwise events to Meta conversion event schema.

{ "eventMapping": { "purchase": "Purchase", "add_to_cart": "AddToCart" } }

3

Apply optional filters

Control which events are forwarded to Meta.

{ "eventFilters": { "purchase": { "enabled": true } } }

4

Run connectivity test

Validate channel health and credentials.

POST /api/v1/sites/:siteId/integrations/meta/test

5

Monitor delivery logs

Review failed deliveries and retry outcomes.

GET /api/v1/sites/:siteId/integrations/meta/logs?limit=50

Meta config example

{
"enabled": true,
"config": {
  "pixelId": "123456789012345",
  "accessToken": "META_ACCESS_TOKEN",
  "advancedMatching": true
},
"eventMapping": {
  "page_view": "PageView",
  "add_to_cart": "AddToCart",
  "purchase": "Purchase"
},
"testMode": false
}

Required Fields / Minimum Payload

Field	Required	Type	Used by events	Description
config.pixelId	Required	string	Meta update payload	Meta pixel identifier.
config.accessToken	Optional	string	Meta update payload	Access token for server-side forwarding contexts.
config.advancedMatching	Optional	boolean	Meta update payload	Toggle advanced matching enrichment behavior.
eventMapping	Optional	Record<string,string>	Meta update payload	Canonical-to-Meta event map.
testMode	Optional	boolean	Meta update payload	Logs only; no downstream sends when true.

Currency Behavior

• Meta payload currency is resolved with fallback order: event -> order -> site -> EUR.
• Forwarded values keep source currency; no FX conversion is applied.
• Avoid client-side fixed symbol/ISO assumptions when validating Meta payloads.

Event or Endpoint Decision Matrix

Scenario	Use This	Why
Configure/rotate Meta credentials	PUT /integrations/meta	Primary config write path.
Validate transport before launch	POST /integrations/meta/test	Connectivity and auth check.
Inspect failures	GET /integrations/meta/logs	Troubleshoot delivery and payload issues.
Need baseline mapping set	GET /integrations/meta/mappings	Default map as starting point.
Need temporary dry run	testMode=true	Safe validation in staging-like conditions.

Common Errors and Fixes

Meta test endpoint fails

Cause: Invalid pixel/access token combination.

Fix: Regenerate token and verify pixel ownership.

Purchase events missing in Meta

Cause: eventMapping missing purchase mapping or filter blocks event.

Fix: Add explicit purchase mapping and inspect eventFilters.

Duplicate-like signal patterns

Cause: Client and server pathways both forwarding without coordination.

Fix: Define single authority path or dedup strategy per event.

Events appear in logs only

Cause: testMode enabled.

Fix: Disable testMode for production sending.

Production Checklist

• Meta credentials are validated through test endpoint.Required
• Purchase and add-to-cart mappings are explicitly defined.Required
• Advanced matching policy is reviewed for compliance requirements.Required
• testMode is off in production.Required
• Meta delivery logs are monitored post-release.Required

Next Steps

• Google Ads
• Event Mapping
• Operations