When Acoustic Exchange users share an audience, Acoustic Exchange sends a collection of IDs and associated data that is defined as a segment in a source database and moves the data to a segment that is defined in a destination database. No point-to-point software integration is required.

To share audience data, a registered Acoustic Exchange endpoint can call APIs that are hosted by Acoustic Exchange or implement specific Acoustic Exchange APIs that Acoustic Exchange can call. The APIs enable Acoustic Exchange to describe the audience data that you can produce, run jobs to export or import the data, and report on the status and success of each audience data exchange.

  1. An endpoint provider registers with Acoustic Exchange as an audience source. The endpoint declares a contact
    URL and the personal identifiers and descriptive metadata it can provide.
  2. Acoustic Exchange calls the source endpoint to gather audience metadata. Acoustic Exchange displays summary descriptions of
    the audience and its contents in the Acoustic Exchange interface.
  3. In Acoustic Exchange, users select a source audience and destination endpoint. Users also map identifiers and
    attributes in the source audience to corresponding data in the destination endpoint. Acoustic Exchange users can share the audience immediately, schedule sharing for a later time, or schedule sharing on a recurring basis.
  4. Acoustic Exchange calls the source endpoint to get the audience data. The source endpoint uploads the audience over HTTP.
  5. Acoustic Exchange can download the audience data to the registered URL for the destination endpoint over HTTP.
    The destination endpoint can use the Acoustic Exchange Toolkit to pull the audience data from Acoustic Exchange.

Request audience data

Acoustic Exchange provides a graphical interface for users to search for appropriate audiences, review
audience descriptions, and specify how and when to share audience data.

Acoustic Exchange gets the details about the audience by making an API call to the URL that was specified when
the endpoint was registered.

In Acoustic Exchange, users specify how to share audiences as follows.

  1. Select an audience. Users search for and select an audience that provides identifiers and attributes that are best suited to achieving a business objective.
  2. Select a destination. Users select a destination endpoint. Each user can see only the endpoints that are registered with Acoustic Exchange on behalf of their Acoustic Exchange user account.
  3. Map identities and attributes. Users map identities and attributes that are present in the source audience to corresponding data that is used in the destination endpoint.
  4. Share the audience. Users can share the audience immediately, schedule sharing for later, or schedule sharing on a recurring basis. Users can also indicate how Acoustic Exchange modifies the destination audience. Acoustic Exchange can add records to a new or existing database, replace records in an existing database, or remove specific records from the destination database.

Connect audience endpoints with Acoustic Exchange

Acoustic Exchange endpoints connect with Acoustic Exchange through RESTful APIs. Endpoints call or implement Acoustic Exchange APIs
depending on how the endpoint provides or consumes audience data.

Acoustic Exchange refers to the exchange of audience data between endpoints through Acoustic Exchange as data
syndication
. As an endpoint provider, you can use the Acoustic Exchange Integration Manager to declare a syndication type when you define the Acoustic Exchange application on which your Acoustic Exchange endpoint is based. After completing the process to be an approved Acoustic Exchange endpoint, you can exchange audience data through Acoustic Exchange by implementing APIs that Acoustic Exchange can call, or by calling various APIs that are hosted by Acoustic Exchange.

All API requests to Acoustic Exchange require that the request header include an authorization bearer that is a customer-supplied authentication key. Providing the authentication key verifies the connection between a specific Acoustic Exchange user account and a user account in the endpoint application. As part of its
Click to Connect endpoint registration, Acoustic Exchange supports two ways for users to provide their authentication credentials.

Audience data is shared through Acoustic Exchange by a source and a destination endpoint as a list of
comma-separated values (CSV). Acoustic Exchange requires that, as an audience producer or consumer endpoint, you
indicate whether the data exchange occurs as a push to Acoustic Exchange or the endpoint, or as a
pull from Acoustic Exchange or the endpoint.

The distinction between audience sharing as PUSH or PULL depends on how the audience data moves
between an endpoint and Acoustic Exchange. How the data flows between Acoustic Exchange and source and destination endpoints
also determines where the audience sharing APIs are hosted.

  • PULL-type audience producer. Acoustic Exchange calls APIs that are hosted and implemented by
    the source endpoint. When the source endpoint indicates that data is available, Acoustic Exchange pulls audience
    data from the source endpoint.
  • PUSH-type audience producer. The source endpoint calls APIs that are hosted by Acoustic Exchange. When the source endpoint determines that it can make audience data available, the source
    endpoint pushes data to Acoustic Exchange.

  • PULL-type audience consumer. The destination endpoint calls APIs that are hosted by Acoustic Exchange. When the destination endpoint is ready to accept audience data, it pulls data from Acoustic Exchange.
  • PUSH-type audience consumer. Acoustic Exchange calls APIs that are hosted and implemented by
    the destination endpoint. Acoustic Exchange pushes audience data to the endpoint when the data is shared by an
    audience source.

As an endpoint provider, you must declare an endpoint type as part of the endpoint provisioning
and review process when you use the Acoustic Exchange Integration Manager to define the Acoustic Exchange application on which
to base your endpoint.

Join The Discussion

Your email address will not be published. Required fields are marked *