In which scenario should a RTCDP extension be used instead of a RTCDP connection?

The scenario where a Real-Time Customer Data Platform (RTCDP) extension is preferred over a RTCDP connection is when behavioral data needs to be forwarded to an external system. Using an extension allows for the integration of additional features or functionalities that might be required for handling data more flexibly or for additional processing needs. In this context, the extension acts as a bridge, capturing behavioral data and facilitating its transfer to external systems, enabling organizations to leverage this data in other platforms or tools that perform specific tasks, such as CRM systems or marketing automation tools.

This capability is particularly crucial when organizations are looking to enhance their operational efficiency or to use that data for external audience segmentation or analysis outside the primary platform. The use of an extension in this scenario also provides the opportunity for real-time updates, making it especially advantageous for maintaining up-to-date information across systems.

In contrast, while the other scenarios may involve data interactions, they are typically handled within the core functionality of the RTCDP itself, whether it's targeting segments, aggregating data for analytics, or performing analytics directly on the platform. These use cases focus more on internal processes or functionalities, rather than the external forwarding of behavioral data, which is where the extension is particularly beneficial.