I understand the offer flow and attributes and the various shapes used in the offer flow. However could not understand how the offerflow is called from strategy. Also when there is a limitation on the offer/channel, how the subsequent runs select different users/segments and apply the limitation logic.
It's good to see your curiosity about the internal operations of Pega Marketing.
The strategy doesn't directly invoke the offer flow. It's the Program-Run process flow that orchestrates the execution of the various stages of a marketing program:
1) First the customers in the starting population is identified.
2) Next, the strategy is run in a batch mode for each customer in the starting population.
3) Then the constraint optimization is applied on the result of the strategy which eliminates offers that do not satisfy the offer/channel limitation.
4) And finally the Offer flow execution takes place for each resulting offer/customer combination.
Hope this helps. Feel free to write back if you need further clarification.
Can you also please detail how the subsequent program execution do not pick the same customers (segment); Is this done by using Interaction history? Hope earlier execution and it's associated offerflow data can be used for this filteration.
would appreciate under the hook steps (very high level) from NBAA portal perspective too. NBAA is real time and I believe the strategy execution is for every interaction by the customer.
If you intend to disqualify customers from receiving the same offer in subsequent programs, then you have to use the Interaction History (IH) check - either in the Segment criteria or in the Strategy.
In Segment criteria: Click on Add Criteria, go to the Communication History tab and select one of the conditions.
In Strategy you can do it in two ways:
a) To import IH for one of more propositions imported by a proposition component: Go to the Interaction History tab of a proposition component, enable Interaction History, fetch the IH information and use a filter component to filter strategy results.
b) To import IH for multiple issues/groups: Import > Interaction History component. Use group by (if required) and filter component to filter strategy results.
NBAA is a standard Pega 7 application that uses process flows which in turn calls the Next-Best-Action Strategy via an Interaction rule, for one customer at a time, in real-time. As you may have noticed, the Next-Best-Action Strategy in-turn references other sub-strategies to come up with the best 'action' for a customer in a given situation.
I was also curious about the linkage with proposition and offer flow. How pega identifies which offer flow to invoke for a specific proposition? Offer flow name and proposition name should be same? As I can see offer flow identifier should not have space while proposition can have space.
Suppose I have 2 business issue, each of it having 3 groups. I want one single default offer flow for all of them. how to achive that.
In Pega Marketing, there is a one-to-one relation between offers and propositions. In Pega Marketing, when you create an offer, a proposition with the same name is automatically created for you. When a strategy selects a proposition for a customer, the offer flow associated with that proposition is invoked.
Regarding your second query: as of today, there is no way to create offer flows that you can be reused across offers. If there are two offers that have exactly same flow design, you still have to build those flows for both the offers. You can copy an offer (using Save As) to save time.