Destination types

This article explains the difference between active destinations and passive destinations.


After collecting and harmonizing data in Adverity, transfer it to a destination to store and further process information.

In Adverity, there are two types of destinations:

  • Active destinations

  • Passive destinations

Active destinations

When you set up an active destination for a datastream, each time Adverity fetches data for the datastream, Adverity actively pushes the data to the active destination.

To transfer data from a datastream to an active destination, perform the following actions:

  1. Add the active destination to the workspace which contains the datastream.

    When you add an active destination, you save the information about how to connect to it. After you add an active destination to a workspace, you can assign the active destination to datastreams in the child workspaces.

  2. Assign the active destination to the datastream.

    When you assign an active destination to a datastream, data is transferred to the active destination each time data is fetched for the datastream.

  3. Enable data transfer to the destination from the datastream.

Passive destinations

When you set up a passive destination for a datastream, the passive destination periodically pulls data from Adverity. When Adverity fetches data for the datastream, it does not actively push it to the passive destination.

The passive destination pulls all of the datastream's data extracts with Collected or Imported status.

Only three destinations in Adverity are passive destinations:

Assigning multiple destinations to a datastream

You can assign as many destinations to a datastream as you want.

Some destinations require specific Data Mapping, such as Hubspot and Facebook Offline Conversions. If these Data Mapping requirements conflict, the destinations cannot be assigned to the same datastream.

For some destinations, such as File, you can choose not to apply Data Mapping before transferring data. In this case, the limitation about destinations using the same Data Mapping does not apply.