Question
Rabobank
NL
Last activity: 14 Sep 2021 8:06 EDT
How to configure a Facebook Ads Use Case In Pega 8.5.1?
Hi,
We are currently in Pega v8.5.1. We have a Pega marketing setup in place and working and are trying to do a POC on Facebook Paid Media Ads. We have already established a successful integration with Facebook by adding the destination.
Can someone please explain the detailed step by step process to post Ads to Facebook? I mean what are the artifacts that we need to configure step by step. Till now we have done the following steps after successfully establishing the Facebook destination:
1) Configure the paid destination in Next Best Action Designer.
2) Create a simple Paid strategy with Proposition import and results(in the NBAD itself).
3) Enable a particular action for Paid channel.
4) Enable all the Paid media related agents.
I have gone through loads of articles on PDN but none of them explain the end to end configuration setup.
Thanks,
Chiranjeet Mishra
Accepted Solution
Updated: 14 Sep 2021 8:05 EDT
Pegasystems Inc.
PL
@ChiranjeetM5260 As far as I understand, it is not necessary to enable the paid synchronization for a segment that is used as the starting population for next best action. The starting population segment is not sent to the ad platform directly, but rather used as a starting point for the strategy to select the next best action.
Segment synchronization is a good starting point to test the synchronization without configuring the more advanced use cases. You only need to configure the destination (https://community.pega.com/knowledgebase/articles/pega-customer-decision-hub-implementation-guide/85/configuring-facebook-ads-destinations) and enable paid sync on the segment itself, then run the segment (https://community.pega.com/knowledgebase/articles/pega-customer-decision-hub-user-guide/85/enabling-segment-updates-paid-destinations). You do not need to enable actions for paid or run campaigns. After the segment runs, you can verify the results on the Audiences page, or in the destination platform, where you should now have a paid audience based on the segment.
@ChiranjeetM5260 As far as I understand, it is not necessary to enable the paid synchronization for a segment that is used as the starting population for next best action. The starting population segment is not sent to the ad platform directly, but rather used as a starting point for the strategy to select the next best action.
Segment synchronization is a good starting point to test the synchronization without configuring the more advanced use cases. You only need to configure the destination (https://community.pega.com/knowledgebase/articles/pega-customer-decision-hub-implementation-guide/85/configuring-facebook-ads-destinations) and enable paid sync on the segment itself, then run the segment (https://community.pega.com/knowledgebase/articles/pega-customer-decision-hub-user-guide/85/enabling-segment-updates-paid-destinations). You do not need to enable actions for paid or run campaigns. After the segment runs, you can verify the results on the Audiences page, or in the destination platform, where you should now have a paid audience based on the segment.
A more advanced Paid use case is using next-best-action to generate audiences for specific actions, and communicating those audiences to destination platforms. The process is as you described above, except it doesn't require that you enable segment synchronization for the starting population segment (@moryh please correct me if I'm wrong here!). You configure the destination (https://community.pega.com/knowledgebase/articles/pega-customer-decision-hub-implementation-guide/85/configuring-facebook-ads-destinations), configure Next-Best-Action Designer (https://community.pega.com/knowledgebase/articles/pega-customer-decision-hub-user-guide/85/triggering-paid-updates-through-next-best-action), ensure you have some actions that are enabled for paid (https://community.pega.com/knowledgebase/articles/pega-customer-decision-hub-user-guide/85/enabling-actions-paid-channels), optionally specify if you want the synch to create campaigns in the paid destination (https://community.pega.com/knowledgebase/articles/pega-customer-decision-hub-user-guide/85/streamlining-campaign-generation-next-best-action-paid-audiences), then trigger the paid run e.g. through a schedule (https://community.pega.com/knowledgebase/articles/pega-customer-decision-hub-user-guide/85/configuring-recurring-schedule-next-best-action).
I would suggest that you first test the basic, segment-based synchronization and verify that it works before enabling paid schedules. This should make it easier to troubleshoot in case of errors.
Best regards,
Katarzyna
Pegasystems Inc.
IN
Hi @ChiranjeetM5260, the simplest way to start is via segment rule. You can create a customer segment with certain criteria. After this add, Facebook paid destination in Paid sync tab of segment rule. Then run the segment.
You can monitor the progress of this segment paid sync from the Paid sync tab itself. Or you can navigate to App Studio->Settings->Channels->Paid media->Sync tracking page to monitor the progress.
Once the job status is COMPLETED then you can navigate to the Paid media audience page from App Studio -> Audiences -> Paid Media. Audiences generated in the ad networks will be visible on this landing page.
Rabobank
NL
@moryh Thanks for the information. I have a query related to the segment which you have suggested.
Suppose the segment gets created and populated. Will I use it in a stand-alone campaign? Because the NBA schedule campaign already has a segment configured.
Secondly, how does this segment get updated or populated with paid sync enabled? As Pega NBA best practice, we should keep just the starting population criteria in segment and the complex ones in engagement policies. Does, syncing the segment with paid media mean whatever offers are returned by the strategy, those offers will appear in the Facebook feeds of the customers?
Thanks,
Chiranjeet Mishra
Pegasystems Inc.
PL
@ChiranjeetM5260 Hello Chiranjeet,
in addition to what Harindra has said above, here's a document about enabling paid synchronization for segments: https://community.pega.com/knowledgebase/articles/pega-customer-decision-hub-user-guide/85/enabling-segment-updates-paid-destinations
For Facebook destinations, segment-based audiences are updated when the segment is updated in CDH. Segments generate audiences based on the contents of that segment, for example, a list of individuals who have opted in for the newsletter. If you would like to use audiences that are based on next best action, you must define the trigger for the update. This article provides an overview: https://community.pega.com/knowledgebase/articles/pega-customer-decision-hub-user-guide/85/triggering-paid-updates-through-next-best-action and this one has more specific information about configuring recurring schedules: https://community.pega.com/knowledgebase/articles/pega-customer-decision-hub-user-guide/85/configuring-recurring-schedule-next-best-action
I hope this helps! Let me know if you have questions or comments.
Best regards,
Katarzyna
Rabobank
NL
@koltk Thank you for the links and your inputs!
So what I understand is as follows:
1) Enable paid sync in the segment used in NBAD
2) Enable Paid destination in NBAD->Channels
3) Run a NBA campaign as per the schedule
4) If the customer is eligible for an offer and the offer is enabled for paid media, the offer will appear in the Facebook feed of the customer who is registered in Facebook with the email id which is mapped to the customer in Pega
Let me know if my understanding is correct?
Thanks,
Chiranjeet
Accepted Solution
Updated: 14 Sep 2021 8:05 EDT
Pegasystems Inc.
PL
@ChiranjeetM5260 As far as I understand, it is not necessary to enable the paid synchronization for a segment that is used as the starting population for next best action. The starting population segment is not sent to the ad platform directly, but rather used as a starting point for the strategy to select the next best action.
Segment synchronization is a good starting point to test the synchronization without configuring the more advanced use cases. You only need to configure the destination (https://community.pega.com/knowledgebase/articles/pega-customer-decision-hub-implementation-guide/85/configuring-facebook-ads-destinations) and enable paid sync on the segment itself, then run the segment (https://community.pega.com/knowledgebase/articles/pega-customer-decision-hub-user-guide/85/enabling-segment-updates-paid-destinations). You do not need to enable actions for paid or run campaigns. After the segment runs, you can verify the results on the Audiences page, or in the destination platform, where you should now have a paid audience based on the segment.
@ChiranjeetM5260 As far as I understand, it is not necessary to enable the paid synchronization for a segment that is used as the starting population for next best action. The starting population segment is not sent to the ad platform directly, but rather used as a starting point for the strategy to select the next best action.
Segment synchronization is a good starting point to test the synchronization without configuring the more advanced use cases. You only need to configure the destination (https://community.pega.com/knowledgebase/articles/pega-customer-decision-hub-implementation-guide/85/configuring-facebook-ads-destinations) and enable paid sync on the segment itself, then run the segment (https://community.pega.com/knowledgebase/articles/pega-customer-decision-hub-user-guide/85/enabling-segment-updates-paid-destinations). You do not need to enable actions for paid or run campaigns. After the segment runs, you can verify the results on the Audiences page, or in the destination platform, where you should now have a paid audience based on the segment.
A more advanced Paid use case is using next-best-action to generate audiences for specific actions, and communicating those audiences to destination platforms. The process is as you described above, except it doesn't require that you enable segment synchronization for the starting population segment (@moryh please correct me if I'm wrong here!). You configure the destination (https://community.pega.com/knowledgebase/articles/pega-customer-decision-hub-implementation-guide/85/configuring-facebook-ads-destinations), configure Next-Best-Action Designer (https://community.pega.com/knowledgebase/articles/pega-customer-decision-hub-user-guide/85/triggering-paid-updates-through-next-best-action), ensure you have some actions that are enabled for paid (https://community.pega.com/knowledgebase/articles/pega-customer-decision-hub-user-guide/85/enabling-actions-paid-channels), optionally specify if you want the synch to create campaigns in the paid destination (https://community.pega.com/knowledgebase/articles/pega-customer-decision-hub-user-guide/85/streamlining-campaign-generation-next-best-action-paid-audiences), then trigger the paid run e.g. through a schedule (https://community.pega.com/knowledgebase/articles/pega-customer-decision-hub-user-guide/85/configuring-recurring-schedule-next-best-action).
I would suggest that you first test the basic, segment-based synchronization and verify that it works before enabling paid schedules. This should make it easier to troubleshoot in case of errors.
Best regards,
Katarzyna