Transaction detail extension overview

Overview

This topic provides additional detail related to the Transaction Detail Extension Feed Layout, including the use of the Feed Layout, how the data is reflected in the database, and how to use the data in Redpoint CDP.

This section provides the following detailed information:

Feed layout intent

Transaction Detail Extension Feed could be used to have more attributes available in Redpoint CDP platform for detail level information from a transaction. The advantage of the extension file is its Key-Value pair fields (custom_field_name and custom_field_value), allowing you to pass any type of data that needs to be available in Redpoint CDP for future analysis or research. Though, these data are not used in built-in aggregates provided in Redpoint CDP platform, they could be used at the transaction level in various situations, for example for a product's attributes like the product's web page link, product specific review page, etc.

Feed layout areas of consideration

If there are multiple business units available, then the Transaction Detail extension will store data at the business unit level based on the actual Transaction Feed Layout, as well as if different types of information need to be available in the Redpoint CDP platform.

Identity matching

Transaction Detail extension data do not go through matching.

Use in RPI

Transaction Detail extension data can be used in RPI to use extension attributes as part of an Interaction selection or suppression criteria.