Pegasystems Connector Setup Guide

This article describes how to set up the Pegasystems connector.

Prerequisites

  • Tealium EventStream or AudienceStream
  • Pega Customer Decision Hub access to the following:

Connector actions

Action Name AudienceStream EventStream
Send Custom Audience Data (Real-Time)
Send Custom Audience Data (Batched)
Send Custom Event Data (Real-Time)
Send Custom Event Data (Batched)

While Tealium can support batched actions to Pega, we recommend that you discuss your use case configuration and need for batching with your Pega account team.

Configure settings

Navigate to the Connector Marketplace and add a new connector. For general instructions on how to add a connector, see the About Connectors article.

After adding the connector, configure the following settings:

  • Client ID Required: The unique ID that is assigned to the client.
  • Client Secret Required: The password that the system assigns to the client to authenticate with the Pega Platform authorization module.
  • Access Token URL Required: The request URL used to receive an access token for the client as a response after authentication.

Your REST service authenticates the client by using the Client ID and Client Secret.

Click Done when you are finished configuring the connector.

How it works

Accurate predictions of customer’s preferences and next best products rely on a good understanding of that customer and most recent interactions across all touchpoints. Tealium enhances Pega’s Customer Decision Hub by making it easy to connect this accurate and rich customer data to inform decisions and recommendations.

The Pegasystems connector connects valuable customer data in two ways:

  1. Tealium and Pega share consolidated customer information based on a 360° view of the customer, aggregating all cross-channel signals in a standardized customer profile.
  2. Tealium streams customer interactions across web, app, call-center and other channels in real-time to Pega to provide in-the-moment context for decision making.

The Pegasystems connector supports both EventStream and AudienceStream actions and lets you track page views/interactions through EventStream. Using a Customer Identifier or Cookie ID you can configure and map differing page types to send interaction history to Pega.

Additionally, trigger next best actions within the Pega Customer Decision Hub by sending audience segments and statuses to Pega along with a Customer Identifier.

Action settings — parameters and options

Click Continue to configure the connector actions. Enter in a name for the action and then select the action type from the drop-down menu.

The following section describes how to set up parameters and options for each action.

Action — Send Custom Audience Data (Real-Time)

Use this action to send audience data to Pega to help trigger next best action decisioning within the Pega Customer Decision Hub. Send audience data and additional parameters relevant to that visitor’s profile for decisioning in real-time.

Parameters

Parameter Description
Service Endpoint URL The value is the Service Endpoint URL defined in your Pega system.
The Service Endpoint URL uses the following structure, but is customizable and may be provided by your Pega contact: https://<host>:<port>/prweb/PRRestService/<servicepackage>/<serviceclass>/<servicemethod>
Customer ID (Required) The primary key for a Pega Customer Profile.
Segment Name (Required) The audience name to be sent to the Pega platform. We recommend configuring your audience name or similar value as a string to be passed to Pega.
Segment Status (Required) The audience trigger action to join or leave an audience. Based on the desired action, we recommend that you include mapping Join or Leave values to the Segment Status field.
Namespace Category (Required) Any subcategory parameters used to supplement the audience data provided to Pega.
Last Qualification Timestamp The timestamp when the user joined the audience. Date attributes will be converted to the ISO 8601 format. If not mapped, this parameter will be initialized with the current timestamp in the ISO 8601 format. For example: 2022-08-30T01:13:16.081Z.

Action — Send Custom Audience Data (Batched)

Batch Limits

This action uses batched requests to support high-volume data transfers to the vendor. Requests are queued until one of the following thresholds is met:

  • Max number of requests: 10000
  • Max time since oldest request: 60 minutes
  • Max size of requests: 100 MB

Use this action to send audience data to Pega to help trigger next best action decisioning within the Pega Customer Decision Hub. Send audience data and additional parameters relevant to that visitor’s profile for decisioning in real-time.

While Tealium can support batched actions to Pega, we recommend that you discuss your use case configuration and need for batching with your Pega account team.

Parameters

Parameter Description
Service Endpoint URL The value is the Service Endpoint URL defined in your Pega system.
The Service Endpoint URL uses the following structure, but is customizable and may be provided by your Pega contact: https://<host>:<port>/prweb/PRRestService/<servicepackage>/<serviceclass>/<servicemethod>
Customer ID (Required) The primary key for a Pega Customer Profile.
Segment Name (Required) The audience name to be sent to the Pega platform. We recommend configuring your audience name or similar value as a string to be passed to Pega.
Segment Status (Required) The audience trigger action to join or leave an audience. Based on the desired action, we recommend that you include mapping Join or Leave values to the Segment Status field.
Namespace Category (Required) Any subcategory parameters used to supplement the audience data provided to Pega.
Segment Timestamp The timestamp when the user joined the audience. Date attributes will be converted to the ISO 8601 format. If not mapped, this parameter will be initialized with the current timestamp in the ISO 8601 format. For example: 2022-08-30T01:13:16.081Z.

Action — Send Custom Event Data (Real-Time)

Use this EventStream action to send real-time event data, primarily page views, to Pega for aggregation within the Pegasystems endpoint.

Parameters

Parameter Description
Service Endpoint URL The value is the Service Endpoint URL defined in your Pega system.
The Service Endpoint URL uses the following structure, but is customizable and may be provided by your Pega contact: https://<host>:<port>/prweb/PRRestService/<servicepackage>/<serviceclass>/<servicemethod>
Page Type The type of the page visited.
Device Type The device used in event generation.
Event Type (Required) The name of the event. Recommended to use your tealium_event value.
Customer ID Primary key for Pega customer profile. Required if Cookie ID is not provided.
Cookie ID Required if Customer ID is not provided. If both are provided, only Customer ID is used.
Event Timestamp Time of the event generated. Date attributes will be converted to the ISO 8601 format. If not mapped, it will be initialized with the current timestamp in the ISO 8601 format. Example: 2022-08-30T01:13:16.081Z.
Page Location Page URL is required when PageView event is provided.
Page View Active Time The time in seconds the visitor spent on the page.

Action — Send Custom Event Data (Batched)

Batch Limits

This action uses batched requests to support high-volume data transfers to the vendor. Requests are queued until one of the following thresholds is met:

  • Max number of requests: 10000
  • Max time since oldest request: 60 minutes
  • Max size of requests: 100 MB

Use this EventStream action to send batched event data, primarily page views, to Pega for aggregation within the Pegasystems endpoint.

While Tealium can support batched actions to Pega, we recommend that you discuss your use case configuration and need for batching with your Pega account team.

Parameters

Parameter Description
Service Endpoint URL The value is the Service Endpoint URL defined in your Pega system.
The Service Endpoint URL uses the following structure, but is customizable and may be provided by your Pega contact: https://<host>:<port>/prweb/PRRestService/<servicepackage>/<serviceclass>/<servicemethod>
Page Type The type of the page visited.
Device Type The device used in event generation.
Event Type (Required) The name of the event. Recommended to use your tealium_event value.
Customer ID Primary key for Pega customer profile. Required if Cookie ID is not provided.
Cookie ID Required if Customer ID is not provided. If both are provided, only Customer ID is used.
Event Timestamp Time of the event generated. Date attributes will be converted to the ISO 8601 format. If not mapped, it will be initialized with the current timestamp in the ISO 8601 format. Example: 2022-08-30T01:13:16.081Z.
Page Location Page URL is required when PageView event is provided.
Page View Active Time The time in seconds the visitor spent on the page.

Vendor resources

Was this page helpful?

This page was last updated: May 4, 2022