Integrations
Meta
Configure purchase conversions through the Meta Conversions API.
What Is This Integration
The Meta integration sends server-side purchase conversions from Pharos into Meta through the Conversions API.
It allows completed purchases in Pharos to contribute to Meta ad measurement and reporting.
When to Use It
Use Meta when you want:
- server-side purchase conversion reporting in Meta
- purchase attribution tied to completed orders in Pharos
- a measurement flow that does not depend only on browser-side events
Prerequisites
Before configuring Meta, make sure:
- you have a Meta account setup with the relevant pixel
- you have a valid access token
- you know the pixel ID
- you have a plan for preserving Meta attribution identifiers into checkout
- you know the test event code if you want to validate the setup in a test mode
How to Configure It in Pharos
- Open the Meta integration page in admin settings.
- Enable the integration.
- Enter the access token.
- Enter the pixel ID.
- Enter the test event code if you want to validate before relying on live data.
- Save the settings.
What Happens After It Is Enabled
After the integration is enabled:
- Pharos stores the Meta credentials for the account
- completed purchases can be sent to Meta as server-side
Purchaseevents - Pharos uses captured Meta attribution and identity data when it is available
How to Verify It Is Working
To verify the setup:
- completing a test purchase
- checking that the purchase event appears in Meta
- using the test event code if your team wants to validate without relying on live production reporting
Limitations or Important Notes
- the current setup is purchase-focused
- attribution quality depends on the identifiers captured before the purchase is completed
- this is not a full-funnel implementation of every Meta event type
Troubleshooting
If conversions do not appear:
- confirm the integration is enabled
- confirm the access token and pixel ID are correct
- confirm the relevant attribution data was captured before purchase
- confirm your test event code is correct if you are validating in test mode