LinkedIn
Copied!

Table of Contents

Paid Media landing page

Version:

Only available versions of this content are shown in the dropdown

App Studio Settings Channels Paid media

The Paid Media landing page contains the following tabs:

Using the Facebook Ads tab

The Facebook Ads tab allows you to configure one or more paid destinations for Facebook Ads. For more information, see "Configuring Facebook Ads destinations" in the Pega Customer Decision Hub Implementation Guide on the Pega Customer Decision Hub product page.

Using the Google Ads tab

The Google Ads tab allows you to configure one or more paid destinations for Google Ads. For more information, see "Configuring Google Ads destinations" in the Pega Customer Decision Hub Implementation Guide on the Pega Customer Decision Hub product page.

Using the LinkedIn tab

The LinkedIn Ads tab allows you to configure one or more paid destinations for LinkedIn Ads. For more information, see "Configuring LinkedIn Ads destinations" in the Pega Customer Decision Hub Implementation Guide on the Pega Customer Decision Hub product page.

Using the Data Management Platform (DMP) tab

The Data Management Platform (DMP) tab allows you to configure one or more paid destinations for data management platforms (DMPs). You can configure paid destinations for Adobe Audience Manager or a generic DMP. For more information, see "Configuring DMP destinations" in the Pega Customer Decision Hub Implementation Guide on the Pega Customer Decision Hub product page.

Using the Web tab

The Web tab allows you to configure one or more web-based paid destinations. Legacy web-based ad platforms, such as demand-side platforms (DSPs), use pixels, also known as remarketing tags, to access their cookie-based profiles and target ads accordingly. These pixels are typically called when an individual visits a website, and the ads which they display are based on the individual's current website activity.

Paid Media Manager allows you to include the power of Next-Best-Action decisioning into the pixel calls. You can extend the pixel call with a call to the Paid Media web service to determine ad targeting based on the enterprise decisioning and intelligence embedded in Next-Best-Action. For more information, see "Paid Media web service" in the Pega Customer Decision Hub Implementation Guide on the Pega Customer Decision Hub product page.

Using the Sync Tracking tab

The Sync Tracking tab allows you to monitor the status of paid synchronization jobs across segments, real-time, and scheduled runs. You can use it to find failed synchronization jobs and restart them without the necessity to restart the whole outbound run.

The following information is displayed for each synchronization job:

Status
The status of the synchronization job. Possible statuses include Pending, Running, Completed, and Failed. If the synchronization job completed with errors, expand the row to view more information.
Destination
The name of the paid destination of the synchronization job.
Start
The time when the synchronization job started.
End
The time when the synchronization job completed or failed.
Type
Indicates whether the synchronization job was triggered by Next-Best-Action, segment update, or background procesing by an agent. To filter the job table by a specific synchronization type, use the drop-down list above the table.
Details
Depending on the type of the synchronization job, this column shows the name of the Next-Best-Action hierarchy level, customer segment, or agent which triggered the synchronization.
Action
For the latest failed synchronization job, this column shows the Retry option. Click the link to restart the synchronization job without restarting the associated scheduled run.
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.