You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We need to build a Facebook Pixel Destination Connector that will allow users to send event data from Multiwoven to their Facebook Pixel for tracking website interactions, conversions, and other user behavior data. This connector will help users automatically send events such as page views, purchases, and custom events directly to Facebook Pixel.
Requirements
Authentication:
The connector should support Facebook’s Access Token authentication to interact with the Facebook Marketing API.
Configuration:
The connector should require the following configuration parameters:
access_token: Facebook Graph API access token.
pixel_id: The Facebook Pixel ID where the events will be sent.
event_name: The type of event to send (e.g., PageView, Purchase, Lead, etc.).
event_data: The custom data associated with the event, such as transaction details or user actions.
Connector Features:
The destination connector should be able to:
Send various events to a Facebook Pixel, such as:
PageView
AddToCart
Purchase
Lead
Custom events (defined by the user)
Track success or failure of the event delivery.
Send both standard and custom data for advanced conversion tracking.
API Interaction:
The connector should use the Facebook Marketing API to send event data to Facebook Pixel. API documentation can be found here: Facebook Marketing API - Events
Data Format:
Data must be formatted according to Facebook's required structure for event tracking. This may include user information (e.g., hashed emails or phone numbers) and event-specific data (e.g., purchase amount, currency).
Error Handling:
The connector should handle errors gracefully and provide detailed logs or messages to inform users of any issues in event transmission (e.g., invalid data format, expired access token).
Steps to Implement
Authentication Setup:
Implement authentication using Facebook’s Access Token to allow the connector to send events to the Facebook Pixel.
Connector Configuration:
Create a configuration file that accepts the required access_token, pixel_id, event_name, and other relevant parameters.
Facebook API Integration:
Implement the logic to send event data to Facebook Pixel via the Conversions API. Support multiple types of standard and custom events.
Data Validation:
Ensure that data is properly validated before being sent to Facebook (e.g., required fields like event_nameand pixel_id must be provided).
Testing:
Write unit tests and integration tests to ensure the connector works as expected.
Use mocks for API calls during testing to simulate Facebook Pixel interactions.
Documentation:
Provide a detailed README.md that explains how to configure and use the connector.
Include example payloads for sending different event types (e.g., purchase events, page views).
Acceptance Criteria
The connector can successfully send standard and custom events to Facebook Pixel.
The connector provides clear feedback on the success or failure of event delivery.
Unit and integration tests provide coverage for common scenarios (e.g., valid/invalid event data).
Comprehensive documentation is provided for users to configure and use the connector.
Issue Type:
New Feature / Connector Request
Description
We need to build a Facebook Pixel Destination Connector that will allow users to send event data from Multiwoven to their Facebook Pixel for tracking website interactions, conversions, and other user behavior data. This connector will help users automatically send events such as page views, purchases, and custom events directly to Facebook Pixel.
Requirements
Authentication:
The connector should support Facebook’s Access Token authentication to interact with the Facebook Marketing API.
Configuration:
The connector should require the following configuration parameters:
access_token: Facebook Graph API access token.
pixel_id: The Facebook Pixel ID where the events will be sent.
event_name: The type of event to send (e.g., PageView, Purchase, Lead, etc.).
event_data: The custom data associated with the event, such as transaction details or user actions.
Connector Features:
The destination connector should be able to:
Send various events to a Facebook Pixel, such as:
PageView
AddToCart
Purchase
Lead
Custom events (defined by the user)
Track success or failure of the event delivery.
Send both standard and custom data for advanced conversion tracking.
API Interaction:
The connector should use the Facebook Marketing API to send event data to Facebook Pixel. API documentation can be found here:
Facebook Marketing API - Events
Data Format:
Data must be formatted according to Facebook's required structure for event tracking. This may include user information (e.g., hashed emails or phone numbers) and event-specific data (e.g., purchase amount, currency).
Error Handling:
The connector should handle errors gracefully and provide detailed logs or messages to inform users of any issues in event transmission (e.g., invalid data format, expired access token).
Steps to Implement
Authentication Setup:
Implement authentication using Facebook’s Access Token to allow the connector to send events to the Facebook Pixel.
Connector Configuration:
Create a configuration file that accepts the required access_token, pixel_id, event_name, and other relevant parameters.
Facebook API Integration:
Implement the logic to send event data to Facebook Pixel via the Conversions API. Support multiple types of standard and custom events.
Data Validation:
Ensure that data is properly validated before being sent to Facebook (e.g., required fields like event_nameand pixel_id must be provided).
Testing:
Write unit tests and integration tests to ensure the connector works as expected.
Use mocks for API calls during testing to simulate Facebook Pixel interactions.
Documentation:
Provide a detailed README.md that explains how to configure and use the connector.
Include example payloads for sending different event types (e.g., purchase events, page views).
Acceptance Criteria
The connector can successfully send standard and custom events to Facebook Pixel.
The connector provides clear feedback on the success or failure of event delivery.
Unit and integration tests provide coverage for common scenarios (e.g., valid/invalid event data).
Comprehensive documentation is provided for users to configure and use the connector.
Resources
Facebook Marketing API - Conversions API
Facebook Marketing API Authentication
The text was updated successfully, but these errors were encountered: