Skip to main content

Configuring Facebook Ads destinations in Paid Media Manager

Suggest edit Updated on September 21, 2021

After you create a Facebook App to access the Facebook Marketing API, configure the connection to a Facebook Ads destination in Paid Media Manager.

  1. Log in to Pega Customer Decision Hub as an operator with access to App Studio.
  2. In App Studio, click SettingsChannelsPaid MediaFacebook Ads, as in the following figure:
    Accessing the Paid Media landing page
    Accessing the Paid Media landing page
  3. Click Add destination.
  4. Enter the credentials that you created in Facebook Ads.
  5. In the Field mapping section, map destination API properties to Pega Customer Decision Hub properties.
    1. Map the Facebook Ads Email (EMAIL) parameter to a property.
    2. Optional: Map additional PII properties, such as device ID, address, phone number or date of birth.
      Note: Mapping multiple properties makes it possible to generate higher match rates and reach more individuals.
    For more information about PII mapping, see Mapping individuals to paid destinations with CRM attributes.
  6. In the Use External Id (EXTERN_ID) field, specify a unique ID that can be used in place of hashed data for subsequent updates for a given individual.
    This feature is enabled and set to use the class key from your Customer class by default. Keep in mind that disabling this setting will result in slower synchronization with Facebook.Note: The property used as external ID is not hashed during synchronization with Facebook. If you want to change it, select a property that can identify an individual uniquely without exposing their internal data.
  7. Configure the additional settings in the Facebook Ads assets generation section:
  8. Click Apply.
Did you find this content helpful? YesNo

Have a question? Get answers now.

Visit the Collaboration Center to ask questions, engage in discussions, share ideas, and help others.

Ready to crush complexity?

Experience the benefits of Pega Community when you log in.

We'd prefer it if you saw us at our best.

Pega.com is not optimized for Internet Explorer. For the optimal experience, please use:

Close Deprecation Notice
Contact us