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.

Capturing paid interactions from Google Ads

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 Capturing paid interactions.

The following are instructions to configure the destination click URL for Google Ads to capture paid interactions.

Configuring the Google Ads final URL to redirect to your website or microsite

  1. Log in to Google Ads.
  2. In the ad details, configure the destination click URL for the ad:
    1. In the Final URL field, enter the URL of the website or microsite to which the individual should be redirected on clicking the ad.
    2. In the Ad URL options section, in the Tracking template field, specify the URL using valuetrack parameters provided by Google Ads: {lpurl}?adgroup_id={adgroupid}&ref_url={_refUrl}&utm_medium={_utmMedium}
      The {adgroupid} parameter is the ID of the ad group to which the ad belongs. Paid Media Manager uses it to determine the action for which the click was recorded. When an individual clicks the ad, the parameter is replaced by the actual value and passed in the request. You can include other valuetrack parameters as necessary. For more information about valuetrack parameters, see Set up tracking with ValueTrack parameters.
    3. Click Save and create extensions.
  3. Test that the paid interactions are captured in Interaction History. For more information, see Verifying that paid clicks are recorded in Interaction History.
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. is not optimized for Internet Explorer. For the optimal experience, please use:

Close Deprecation Notice
Contact us