For realtime audience based destination
The "Automatic Audience Replay" feature is designed to enhance dynamic segments usage within real-time audience-based destinations like Facebook Custom Audiences.
In our previous system, for real-time audience-based destinations, only users who joined a segment after the creation of the destination were automatically sent to that destination. This approach overlooked users who were already in the segment. The Audience Replay feature rectifies this by ensuring that all segment users, both existing and new, are sent to the relevant destination.
When Creating a Destination:
Immediate Activation: If the destination is activated immediately, an operation is launched to send all users from the segment to the destination without delay.
Scheduled Activation: For destinations set to activate later, an operation is scheduled to send all users in the segment to the destination at the specified start time.
When Updating a Destination:
Reactivation/Modification: Some updates to the destination (changing start times or timezones) automatically initiates an operation to send all segment users to the updated destination.
Adding New Segments: Incorporating new segments into the destination triggers an operation to send only the users from these new segments.
This feature works seamlessly with various real-time, audience-based destinations, including:
Facebook Custom Audiences
Google Customer Match
Criteo Audiences
Google Ads Customer Match
Rakuten
Google DDP
Comprehensive User Engagement: Ensures every historical relevant user in the segment is sent to the destination, enhancing audience coverage.
Efficient Automation: Reduces manual efforts and error potential, streamlining the process of managing audience data.
Current and Relevant Audience Data: Keeps your audience segments up-to-date, maximizing the impact of your marketing efforts.
Find here the full list of destinations already configured.
You can search a destination by name and filter on environment (production or staging), status (active or inactive) or on specific source.
4 sections are available: Cloud mode, Device mode, Audience and Raw Data.
It refers to event based destinations that execute on the server (aka server-side tags): destinations that run in real-time and push your events (purchases, page views...).
It refers to destinations that needs to be executed in the browser (aka client-side tags). For example : survey tag, A/B testing, heatmapping tool, live chat, web notification, ... Currently, client-side tags are manageable in the web containers section. They will move progressively on the device mode section.
It refers to destinations that push user's segments, each time a user enter or leave a segment you created.
It refers to scheduled destinations, through file exchange like FTP, S3 or Cloud Storage.
The trend represents the evolution of number of events pushed to the destination on the last month (maximum data retention period).
Health allow to quickly visualize the status of the destination, if everything is well sent (sunny) or not (stormy) on the last hour. Click on it to access to Event Delivery interface and have more details (see also Event Delivery documentation).
