Skip to main content

​
Overview

Meta Pixel for frontend event tracking and Conversions API (CAPI) for server-side event deduplication and enhanced match quality. Category: Analytics
Catalog status: Not specified in the connector catalog

​
Supported capabilities and connector actions

​
Direction

  • P2HS → Facebook / Meta: Yes — supported actions can send data or requests to the provider.
  • Facebook / Meta → P2HS: No inbound trigger is listed in the catalog.
  • Webhooks: No webhook or inbound event is declared in the catalog.

​
Prerequisites

  • A Facebook / Meta account with permission to create or authorize the connection.
  • The credentials or authorization flow required by P2HS (Api key).
  • Any provider-side account, workspace, repository, store, or sending-domain permissions required for the selected capability.

​
Connect the integration

  1. Open the P2HS dashboard.
  2. Select the project or workspace where the connector will be used.
  3. Open Integrations and choose Facebook / Meta.
  4. Select Connect and complete the provider authorization or credential form.
  5. Save the connection and run the verification check.
  6. Bind the connection to a compatible capability, App Block, or Feature Pack.

​
Credentials and configuration

Authentication: Api key. The current catalog requires these credential fields:
  • access_token
Configurable fields exposed by the connector:
  • pixel_id
P2HS stores connector credentials as managed secrets. Rotate or revoke them from the connection settings; do not commit them to source code or expose them in browser code.

​
Generated applications

After Facebook / Meta is connected, compatible capabilities and composed application features can bind to the connection. The generated application should call the approved P2HS capability rather than embedding Facebook / Meta credentials.

​
Events and webhooks

No inbound event is declared for this connector in the current catalog.

​
Troubleshooting

  • Authentication failed: confirm the credential or authorization flow and the provider account selected.
  • Permission denied: verify that the provider account can access the configured resource and action.
  • Action unavailable: confirm that the capability is admitted for the project and supported by this connector.
  • Event not received: check the connection status, provider event configuration, and the project environment.

​
Disconnect or rotate credentials

Update or revoke the connection from the project or workspace Integrations settings. Dependent capabilities may stop working after disconnecting; reconnect and verify the binding before retrying the application flow.