Triggers and Destinations

Triggers#

A Trigger is the entry point for an activation request to Velocidi. It holds the basic activation configurations, as well as the list of Destinations that should be triggered on an Activation request.

A trigger can be reactive or scheduled.

  • A reactive trigger will activate users on live campaign audiences in real-time;
  • A scheduled trigger will activate batches of users at pre-determined intervals and can only be associated with Destinations that support offline activations.
    For example, scheduled triggers can be used in cases where the destination platform needs audiences of email lists rather than attributes, such as MailChimp or Facebook Custom Audiences.

Activation Triggers can be added to the system using the Dashboard under Activate > Triggers and clicking on the New Trigger button.

dashboard new trigger

Reactive Triggers#

The following fields are available:

  • Name: Name for the Trigger.
  • Key: The key or ID that identifies this trigger. It is used later to issue requests for this specific trigger.
  • Active: Enables or disables the trigger. A disabled trigger does not provide responses for activation requests.
  • Enabled Destinations: The list of Destinations to activation on request.
  • Activate on Match Requests: Defines if this trigger should fire when a match request is issued.
  • Browser Cache Duration: Defines the period that a browser should cache the response.
  • Referrer Validation Domains: If enabled, evaluates the referrer domain, only responding when the request is issued from a website of a valid referrer.
  • Redirect Activation Strategy: Defines the destination to be triggered when a redirect activation is requested. Since the browser can only redirect the client to one location, redirects can either be configured to point to a specific destination or choose a random destination for each request.

Scheduled Triggers#

For scheduled triggers, the following fields are configurable:

  • Name: Name for the Trigger.
  • Key: The key or ID that identifies this trigger. It is used later to issue requests for this specific trigger.
  • Active: Enables or disables the trigger. A disabled trigger does not provide responses for activation requests.
  • Enabled Destinations: The list of Destinations to activation on request. For scheduled triggers, the destinations you can select are restricted to the ones that support offline activations.
  • Triggering Frequency: The frequency to activate the users.
  • Skip destination if the user was activated to it in the last: Allows configuring the activation strategy for users that were activated recently.
  • Skip users inactive for: Allows configuring the activation strategy for users that are inactive.

Destinations#

Destinations are configured to hold the details of how to execute an activation and what data is sent out. In order for a destination to be used, it has to be associated to a Trigger.

Activation Destinations can be added to the system using the Dashboard under Activate > Destinations and clicking on the New Destination button.

Dashboard Destination New

Destinations are divided in two types:

  • Third-party Integrations: Easy to configure integrations with several third-party partners where just the essential configurations are required. For detailed information see the Activation Integrations.
  • Generic Integrations: These integrations give you complete control on how to activate your users and allow you to integrate with partners we don't support natively yet.

Third-party Integrations#

See Activation Integrations for a comprehensive list of third-party integrations.

Generic Pixel#

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.

Generic HTML#

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.

Generic Webhook#

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 http method, headers, endpoint and 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 s3://adstax-<client>-partner-activations.

    For example, for a destination with id "client1" exporting a CSV with email data, the file will be stored in s3://adstax-client1-partner-activations/client1/email_sha256_2020-01-01_23-45.csv.gz

  • sftp: If sftp is chosen, the host, port, path, username and password/ssh_key will need to be configured.

Additionally, the exported file format can be selected (csv, tsv and 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.

Last updated on