

RudderStack maps the event_name from whatever the name of the event that is being sent is. The same is true if two server events with the same information is sent to Facebook

Both events must have the same event_name, and the same fbp parameter and the same external_id. fbp and external_id method (Not Recommended)įor this approach, it is necessary to send an event, first from the browser, then from the server. The properties listed below are the default denylisted properties.įor more information regarding the logic behind the event_id deduplication, refer to the Facebook documentation. If it is enabled, the properties will be SHA256-hashed and sent to Facebook. Denylist PII Properties: The PII properties mentioned in this field will not be sent to Facebook if Denylist PII Hash Property is not enabled.
#FACEBOOK PIXEL TESTER UPDATE#
Enable Advanced Matching: Enable this setting to update the user information in Facebook Pixel via an identify call.RudderStack will then assign this to the value field of the Facebook payload. Value Field Identifier: You can set this field to properties.price or properties.value.If you want to send more properties for your events, mention those properties in this field. Standard Events custom properties: For the standard events, some predefined properties are taken by Facebook.Map your events with Facebook Standard Events: This option lets you map your events to the standard events defined by Facebook.Enable Standard Event (PageView) for all Page and Screen Calls: If this setting is enabled, RudderStack sets pageview as a standard event for all the page and screen calls.Map Categories to Facebook Content Types: This option lets you specify the category fields to specific Facebook content type.For more information on obtaining your Facebook Pixel ID and Business Access Token, refer to the FAQ section below.
