Destinations
Exporting data to your DSPs and storage buckets for targeting and manipulation.
Destinations are used when exporting audience data from a DCN. The type of data exported from an audience to a destination consists of type-prefixed identifiers and identity clusters. There are different types of destinations, such as Google Cloud Storage (GCS) and Amazon Simple Storage Service (S3) buckets.
You can create a new destination from your DCN UI or using the CLI by running
optable-cli destination create with the type of destination, the bucket location, and access credentials. You can create as many destinations as you like.DSPs are platforms to which you can export your audience for real time programmatic advertising. Examples of DSPs are The Trade Desk and Google's Display & Video 360 (coming soon). You can push audiences to these destinations via the "Export" button in the audience you wish to export.
Storage buckets are destinations to which you can export your audiences as either CSVs, TSVs or JSON objects. Examples of storage buckets are Google Cloud Storage (GCS) and Amazon SImple Storage Service (S3). Exporting to these destinations enables you to use the output files in your preferred data visualization, modeling and reporting tools.
You can view a history of all exports to a specific destination as well as errors related to those exports by navigating to your destination in Integrations > Destinations and clicking on the "History" tab.
Expiry/TTL is a feature that enables you to set a specific expiration date for your data when you export to some destinations such as The Trade Desk. Each time you export an audience to a destination supporting Expiry/TTL you will reset the timer. This will ensure that stale audiences don't remain in your export destinations for longer than necessary.
Destinations can support append and replace operations. When you append to an audience, it will add all new IDs to that destination without affecting the original data. If replace is available as an option, each time you export it will completely replace the audience/segment in your destination.
From the UI
From the CLI
Destinations can be archived via the UI by navigating to the specific destination you wish to archive in Integrations > Destinations and clicking "Archive".
optable-cli destination archive <id>Note that data (exported results) will not be deleted from the destination when archiving said destination.
Destinations can be deleted from the DCN UI or by using optable-cli with the following invocation
optable-cli destination archive <id>You can list all destinations with the CLI by running
optable-cli destination list command. The command returns a list of destinations encoded in JSON. You can use the excellent jq utility to parse and manipulate JSON from the command line. For example, to list just the names and type of all destinations:$ optable-cli destination list | jq '[.name,.kind]'
[
"example-s3-bucket-name",
"DESTINATION_KIND_S3"
]
Last modified 1mo ago