![]() See Facebook documentation for more information. The custom data object can be used to pass custom properties. ![]() More information on recommended User Data parameters in Facebook’s Best Practices for Conversions API. You must provide at least one of the following parameters in your request. These parameters are a set of identifiers Facebook can use for targeted attribution. Facebook will automatically convert ISO 8601 timestamps to Unix. See Facebook documentation for supported values.Ī Facebook standard event or custom event name.Ī Unix timestamp in seconds indicating when the actual event occurred. This field allows you to specify where your conversions occurred. You’ll want to remove your Test Event Code when sending real traffic through this integration.īuild your own Mappings! Combine supported triggers with the following Facebook Conversions API-supported actions: You can find your Test Event Code in your Facebook Events Manager under the “Test events” tab. Use this field to specify that events should be test events rather than actual traffic. Follow the steps in the Destinations Actions documentation on Customizing mappings.On the Settings tab, enter in your Pixel ID and click Save.Select the source that will send data to Facebook Conversions API and follow the steps to name your destination.Click Configure Facebook Conversions API (Actions) in the top-right corner of the screen.Search for “Facebook Conversions API (Actions)” in the Destinations Catalog, and select the destination.From the Segment web app, click Catalog, then click Destinations.Scroll down to the “Set up through a partner integration section” and click Choose Partner.Ĭonnect Facebook Conversions API (Actions) to your workspace.Go to the Pixel Settings in Facebook Business Events Manager.Enable the setting to “Authorize Segment Connection” and then click Continue.Choose “Segment” from the list of partners. ![]() Select “Conversions API” and then click Connect.Choose “Web” and then click Get Started.Go to the Facebook Business Events Manager and click Connect Data Sources.You can use an existing Facebook Pixel that you already have set up, or create a new one. Set up your Pixel to work with the Facebook Conversions API (Actions) destination. For documentation on other Facebook destinations, see the pages linked below. This page is about the Facebook Conversions API. Other Facebook Destinations Supported by Segment Data is normalized before it is hashed to ensure the hashed value matches Facebook Pixel (browser). Product data nested within arrays, like the products array in the Order Completed event, can be sent to Facebook. Identify calls can be sent to Facebook as a standard or custom event. Page calls can be sent to Facebook as a standard Page View. Mappings for standard Facebook Conversions API events, like Purchase, are prebuilt with the prescribed parameters and available for customization. ![]() Actions-based destinations enable you to define the mapping between the data Segment receives from your source, and the data Segment sends to Facebook Conversions API. Data mapping for actions-based destinations happens during configuration, which eliminates the need for most settings. The Facebook Conversions API (Actions) destination provides the following benefits over the classic Facebook Conversions API destination: Benefits of Facebook Conversions API (Actions) vs Facebook Conversions API Classic To ensure your events don’t throw an error, Segment recommends that you review Facebook’s new requirements. Customer Information Parameters RequirementsĪs of Facebook Marketing API v13.0+, Facebook began enforcing new requirements for customer information parameters (user data).
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |