LinkedIn
Copied!

Table of Contents

Responding to individual engagement on paid channels with real-time events

Version:

Only available versions of this content are shown in the dropdown

You can define real-time events that correspond to real-time engagement opportunities on paid destinations.

Real-time events are entry points into the application which can be initiated by internal or external systems and can trigger the execution of outbound runs in Next-Best-Action Designer. For more information, see Responding to real-time customer engagement with real-time event triggers.

For example, you can configure a real-time event that triggers when an individual makes a large deposit into a savings account. If the source of the deposit is, for example, a pension payout or a lottery win, the deposit is a signal for the bank that they may take the opportunity to discuss investment options with the individual, or consider upgrading the individual to their Private Banking services. Paid Media Manager helps advertisers pursue this opportunity on paid channels by targeting the individual with relevant ads on Facebook Ads, Google Ads, and LinkedIn Ads destinations

  1. Define a real-time event. For more information, see Responding to real-time customer engagement with real-time event triggers.

  2. In the Channels tab of the Next-Best-Action Designer, in the Triggered by Events section, click Configure.

  3. Select the event that you created.

  4. In the Business structure level list, select the business issue and group with which the event is associated.

    As a best practice, always define the event trigger at the top level of your business hierarchy. Real-time events calls at lower levels of the hierarchy can produce undesired results, for example, removing an individual from all eligible audiences other than those at the same hierarchy level as the event.
  5. Ensure that at least one Facebook Ads, Google Ads, or LinkedIn Ads destination is configured for the same issue and group.

  6. Configure an action and enable it for paid destinations.

    For more information, see Enabling actions for paid channels.
  7. Click Submit.

  8. Click Save.

  9. Log in to your application as an operator with access to Dev Studio.

  10. Save the CDHEventSource data set into your application ruleset.

  11. On the Settings tab of the CDHEventSource data set, disable the authentication.

  12. Create a real-time data flow run for the ProcessEventFromSource data flow of the class PegaMKT-Data-Event, as described in Triggering a real-time event with the Event Stream service.

    Example request payload:
    {
    
    "EventName" : "ApplicationAbandon",
    
    "CustomerID": "CID-5"
    
    }
Audiences created after the event is triggered are synchronized to the paid destination or destinations selected in step 5. You can also view them on the Paid Audiences landing page in Pega Customer Decision Hub.
Did you find this content helpful?

Have a question? Get answers now.

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