Destinations

A “destination” in Wondaris is not only the system where Wondaris will send your first party data, but also the place within that system where the data will go. A couple of examples of this are:

Universal Google Analytics (the system) - a structured event hit within a Google Analytics property (the place within the system)
Google Ads (the system) - a customer match list attached to an Ads account (the place within the system)

So it is important to know (and have access to) both the system at the resource / place within that system where you want Wondaris to send the data.

Some destinations can accept event data, some can accept customer data and others can accept both - Wondaris only limits the use of destination types when using it’s realtime event forwarding capabilities.

A number of destinations require some degree of setup prior to being able to send data from Wondaris - this is often to do with legal terms and conditions and could include being allow-listed to be able to send your customer data to that destination. If you are unsure, we have some documentation both in platform (underneath the little icon on destination cards in the Create Destinations section); and in this documentation.

For further support on anything in Wondaris, contact support@wondaris.com or your customer success manager (at Wondaris or your implementation partner).

Destinations

A “destination” in Wondaris is not only the system where Wondaris will send your first party data, but also the place within that system where the data will go. A couple of examples of this are:

Next