Skip to main content

This content has been archived and is no longer being updated.

Links may not function; however, this content may be relevant to outdated versions of the product.

Configuring LinkedIn Ads destinations in Paid Media Manager

Suggest edit Updated on October 7, 2021
Note: This article describes Paid Media Manager as implemented with Pega Customer Decision Hub™ 8.5 or earlier. For Pega Customer Decision Hub 8.6, see Configuring LinkedIn Ads destinations in Paid Media Manager.

After you create a LinkedIn account and authorization profile, configure the connection to a LinkedIn Ads destination in Paid Media Manager.

  1. Log in to Pega Marketing or Pega Customer Decision Hub as an operator with access to App Studio.
  2. In App Studio, click Settings > Channels > Paid Media > LinkedIn 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 LinkedIn Ads. For more information, see Creating a LinkedIn account.
  5. Take note of the URL in the Redirect URL section. LinkedIn uses this URL to authorize connections. For more information, see Creating a LinkedIn account.
  6. Fill out the following fields:
    • Destination name

    • Account ID

    • Source platform - enter PEGA

    • Client ID - Enter the Client ID. Pega Support provides the required Client ID after authorizing the Paid Media connector for LinkedIn.

    • Client Secret - Enter the Client Secret. Pega Support provides the required Client Secret after authorizing the Paid Media connector for LinkedIn.

  7. Optional: Configure the additional settings in the LinkedIn 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