The browser activation responds to Activation Requests with pixel-based activations.
It requires you to define a list of Activated Parameters and a Templated data transfer URL which configures where the pixel request will be issued. This URL is a template where you can define how the data should be interpolated in the URL. Optionally, specify a Data transfer fallback URL to use in case there are no parameters to send.
Similar to a Generic Pixel but responds with fully-configurable HTML code activation.
It requires you to define a list of Activated Parameters and a Templated body HTML field.
Webhook activations will make a real-time HTTP request to a third party service.
It requires you to define a list of Activated Parameters
and allows configuring the
body. The last two are Templated Fields.
Additionally, this destination can select which User IDs (associated to the User Profile) to activate simultaneously.
Generic File Drop
File drop activations are accumulated in the CDP side and periodically written in in a compressed file in a S3 Bucket in the AWS account that hosts the CDP or to a SFTP server.
S3: The files are named using the user id type being sent out, the file format and timestamp at which they were written. Each file drop activation has its own bucket prefix, identified by the destination key. Third parties that consume these file-based activations should be provided read access to the S3 bucket prefix, using the credentials generated by the CDP. By default, the bucket is
For example, for a destination with id "client1" exporting a CSV with email data, the file will be stored in
sftpis chosen, the
ssh_keywill need to be configured.
Additionally, the exported file format can be selected (
json lines) together with
the periodicity of the exports.
Finally, this destination can select which User IDs (associated to the User Profile) to activate.
For more details about on how to interpolate your segments in the URL see Templated Fields.