Skip to main content


         This documentation site is for previous versions. Visit our new documentation site for current releases.      
 

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.

Embedded strategy

Updated on March 11, 2021

Use the Embedded strategy shape to build transparent multiline strategies that target various marketable audiences within a single strategy canvas. With this shape, you can offer propositions or send messages in a transparent way to multiple audiences, depending on the applicable marketing context, for example, based on contacts, household members, owners of certain devices, specific lines of business, and so on.

The Embedded strategy shape

With the Embedded strategy shape you can perform the following actions on a single strategy canvas:

  • Define multiple embedded strategies as part of the same class.
  • Use the audiences that you preconfigured as part of the pyDictionary rule as contexts for embedded strategies.
  • Define an audience to use as a context for embedded strategies (for example, if no audiences were configured as part of the pyDictionary rule).

The pyDictionary Decision Data rule

Optionally, you can identify the audiences that you want to enable in Strategy rules as contexts by configuring the pyDictionary rule. That rule can include multiple types of audiences, for example, Devices, Subscribers, Household Members, and so on, to simplify strategy design and configuration by providing you with a set of preconfigured audiences to use as contexts.

The default pyDictionary rule is part of the @baseclass class. You must override that rule in the top-level class of your strategy to enable the audiences that you defined that strategy.

Have a question? Get answers now.

Visit the Support Center to ask questions, engage in discussions, share ideas, and help others.

Did you find this content helpful?

Want to help us improve this content?

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