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.

Support Article

Use Decision Date Store flag not affecting contact summary



After selecting the option "Use Decision Date Store" in the marking portal the customer summary records are still written to the RDBMS table <ext mkt schema>.mkt_contact_summary rather than than been applied to Cassandra. It looks like this flag is not altering the application to use Cassandra (DDS).

Error Messages


Steps to Reproduce

Run a Pega Marketing Campaign with 'Use decision data store' set.
Inspect the mkt_contact_summary table to check that records still getiing inserted.

Root Cause

To write the contanct summary data to the DDS it is requied to update the DF_OfferResults Data Flow as detailed in the Pega Marketing implementation guide (v.7.22).
See the section "Extending and updating the OfferResults data flow"


It is advised to use the database to store contact summary data.

In the upcoming release of Pega Marketing 7.31, we are moving away from storing Contact Policy data in the DDS (Cassandra).
So, regardless of the Use Decision Data Store application setting, the system will read and write Contact Policy data from the database.

Suggest Edit

Published August 26, 2017 - Updated December 2, 2021

Did you find this content helpful? Yes No

Have a question? Get answers now.

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

We'd prefer it if you saw us at our best.

Pega Community has detected you are using a browser which may prevent you from experiencing the site as intended. To improve your experience, please update your browser.

Close Deprecation Notice
Contact us