Audience lifecycle in streaming destinations

This page describes how audience name updates and mappings in Experience Platform are synchronized with streaming destination platforms. When you modify audience names or remove audience mappings in Experience Platform, the behavior varies depending on the destination platform’s capabilities.

Understanding these differences is important for managing audience lifecycle operations and ensuring your destination platforms reflect the current state of your audiences in Experience Platform.

Audience name propagation behavior audience-name-propagation

When you activate an audience to a streaming destination, the audience name is sent to the destination during the initial activation. However, audience name update behavior varies by destination:

Destinations which support audience name updates name-update-supported

The following streaming destinations support automatic audience name updates when you modify audience names in Experience Platform:

Destinations which do not support audience name updates name-update-not-supported

For destinations not listed above, audience names remain static after the initial activation. If you need to update an audience name for these destinations, you must:

Destinations which support audience removal support-removal

When you remove (unmap) an audience from a streaming destination, Experience Platform attempts to remove the corresponding audience from the destination platform. However, not all destinations support this functionality.

The following streaming destinations support automatic audience removal when you unmap an audience from the destination:

Destinations which do not support audience removal no-removal-support

For destinations not listed above, when you unmap an audience from the destination, Experience Platform only removes the mapping. The audience in the destination platform remains active until you manually delete it in the partner platform.