RSS
 

Pega Marketing: Real-Time Container plugin for WordPress

09 Nov

Lately I was working on integrating a Pega Marketing Campaign’s Decision Strategy with an WordPress-based external website: the final objective was to display the resulting offers somewhere in the web pages by minimising the effort in terms of client-side coding.

I’ve ended up building a plugin that displays a custom widget in WordPress and that can be set to consume offers from an existing Real-Time Container.

The container is not made to be use on a production environment, but it can be taken as an example to apply the necessary modifications that would make it suitable for a real deployment.

Wordpress Plugin - RealTime Container

Read the rest of this entry »

 

Pega Marketing: Indentify which Real-Time Container triggered a Campaign

09 Nov

Similarly to the previous post, let’s see how to identify which Real-Time Container is consuming a marketing campaign’s Decision Strategy.

You may have multiple Real-Time Containers mapped to the same campaign, so if you wish to be able to drive a specific proposition behaviour depending on the container that has been used, you need to be able to find out within the Decision Strategy what was the name of that container.

When a marketing campaign’s decision strategy is executed by a Real-Time Container, the corresponding container name is stored in the ContainerPayload.ContainerName property.

Below you can see an example of Decision Strategy that uses that property in a switch component: if the container WebContent is detected, then we return all the eligible offers (in this scenario the container is rendered as an offer slider).

Real-Time Container Detection

Enjoy ;-)

 

 

 

Pega Marketing: Identify which Event triggered a Strategy

09 Nov

Just a quick post on how to identify which event triggered a marketing campaing’s Decision Strategy.

You may have multiple events mapped to the same campaign, so if you wish to be able to drive a specific proposition behaviour depending on the event that has been triggered, you need to be able to find out within the Decision Strategy what was the name of that event.

When a marketing campaign is triggered by n event, the corresponding event name is stored in the EventPayload.EventName property.

Below you can see an example of Decision Strategy that uses that property in a switch component: if the event CallDropped is detected, then we assume the customer is a potential churn and we push a retention offer.

Event Detection

Enjoy ;-)

 

Pega Marketing: Full Interaction History View

03 Nov

Interaction History tables store all the information of your marketing campaign, including the feedbacks associated to the offers.

This information is organised in a star schema that considers the following tables:

IH Tables

I’ve created this post to provide a SQL script that creates a database view that joins all the Interaction History tables together.

Read the rest of this entry »

 
No Comments

Posted in Database

 

Pega Marketing: Real-Time Containers

31 Oct

Today we focus on inbound marketing and how to use real-time containers in the context of customer interactions on a website.

This post will explain how to create and especially how to use real-time containers by focusing on the integration aspects.

For the following scenario I’ve used a WordPress website to setup the integration with Pega Marketing through real-time containers and display the Next-Best-Offer in the home page.

From now on we will assume you’ve already created your campaign, including a meaningful Decision Strategy and Propositions/Offers; moreover we will assume that a valid image URL is associated to the proposition itself.

Read the rest of this entry »