People act in the marketplace. For example, they act on social media, abandon shopping carts, open email, and visit brick and mortar storefronts.
Partners represent themselves in
Marketers blend data from various partner endpoints to create a view of their target market.
As a Business Partner that participates in
Applications and solutions from Business Partners integrate with
To assist companies that want to join the
Products and solutions from
When a product or solution has completed the provisioning and validation process that is required to integrate with
To address various use cases, marketers use the
After it analyzes identity information in the incoming data,
Products and solutions that are created and supported by
When a user registers an endpoint, the endpoint registration wizard either prompts users for their credentials or provides alternative submission instructions.
When the user registers an endpoint,
All calls to the public
A unique authentication key is generated when
Depending on how you make your solution available in
After you receive the authentication key, you must include the key in the authorization header of every API call that you make to
When you make your application or business solution available in Acoustic Exchange, you specify the type of data that the endpoint can provide and whether the endpoint is a source of data, a destination for data, or both. Acoustic Exchange users can register four types of endpoints.
- Event source
- Event destination
- Audience source
- Audience destination
When you complete partner provisioning to make your solution available as an endpoint, you indicate the type of endpoint. Acoustic Exchange uses information that you provide to present the endpoint as an option in the Acoustic Exchange user interface.
In Acoustic Exchange, users select endpoints to add to their working environment by registering endpoints with Acoustic Exchange. On the Endpoints tab, Acoustic Exchange provides a wizard to guide users through the registration process.
The endpoint registration wizard lists and describes the endpoints that are available for registration. The wizard lists your solution as an available endpoint if you provision your endpoint by creating an
The wizard presents users with two ways to provide their access credentials.
Instructions only. Users contact you to submit the credentials by following instructions that you provide to
Direct connect. Users enter credentials directly through the endpoint wizard. The wizard displays entry fields based on properties that you specify in the call to the onboarding API.
During the registration process,
If you do not use the Integration Manager to integrate with
The endpoint registration wizard can provide Acoustic Exchange users with instructions for how to submit the access credentials that your endpoint requires.
You specify how
The endpoint registration wizard can display entry fields that enable
To simplify the endpoint registration process for
You specify how
Endpoint registration: Custom endpoint
The endpoint registration wizard gives Acoustic Exchange users an option to register an endpoint as a custom endpoint. Registering a custom endpoint requires specific manual actions by the user, the endpoint provider, and the Acoustic Exchange account provisioning team.
When the user registers a custom endpoint, the user manually generates an authentication key in the wizard. The user must contact you to submit the authentication key that identifies the user’s Acoustic Exchange user account. You must provide the means to submit the authentication key. You must also contact the Acoustic Exchange account provisioning team to provision the user account.
Custom endpoints are created and maintained individually. You must make any changes or updates to the endpoint configuration separately for each Acoustic Exchange user that registers the custom endpoint.
An event is a specific activity or interaction that a business application can detect at a specific time and that can be associated with a customer identifier. The application publishes the event to Acoustic Exchange through a REST API call that includes descriptive attributes in a JSON payload. Each type of event is registered with Acoustic Exchange so that subscribing applications can readily interpret the event data.
Acoustic Exchange recognizes various common events that occur in different channels. For example, for commercial web sites, Acoustic Exchange recognizes Cart Abandonment as a distinct type of event. For mobile engagements, Acoustic Exchange recognizes when an individual installs a mobile app on a mobile phone. For email communications, an event is generated when the recipient clicks a link in the email message.
When you register an event, you can define one or more attributes that describe the event activity. You must also specify at least one attribute that can be used to identify the individual that initiated the event. For example, for an email link click event, you might define an attribute that provides the email address of the individual who clicked the link.
Events also include a timestamp to indicate when the event was observed.
Each event is assigned an event code. Acoustic Exchange uses the event code to identify the specific event.
Endpoints that provide events to Acoustic Exchange are referred to as event publishers. Endpoints publish events to Acoustic Exchange with the v1/event API.
When you use the endpoint API to register an endpoint with Acoustic Exchange, you must indicate if the endpoint serves as an event publisher. After you register the endpoint, the Acoustic Exchange user interface identifies the endpoint as an event publisher so that Acoustic Exchange users can more easily identify where to find event providers.
Each event publisher can provide one or more types of events. When you use the v1/eventtype API to register an event with Acoustic Exchange, you specify a name and description for the event. The name and description display in the Acoustic Exchange user interface.
Acoustic Exchange users select publishers from a list of event publishers. For each event publisher, the user can select one or more types of events.
Endpoints that receive event data are referred to as event subscribers. Acoustic Exchange provides events to subscribers as a POST from the event API.
When you use the endpoint API to register an endpoint with Acoustic Exchange, you must indicate whether the endpoint serves as an event subscriber. After you register the endpoint, the Acoustic Exchange user interface identifies the endpoint as an event subscriber. This label helps Acoustic Exchange users to more easily identify which endpoints support receiving event notifications from event publishers.
Acoustic Exchange defines an audience as a collection of IDs that describe a group of individuals that marketers can target with products, services, or other marketing treatments. The IDs can be associated with various descriptive attributes that business users can use to better define the audience and target their marketing efforts.
Typically, the audience is generated by segmenting one or more customer databases according to various business rules and selection logic. Acoustic Exchange provides a means to share the IDs and attributes between Acoustic Exchange endpoints as a bulk exchange of data.
When Acoustic Exchange users share data between endpoint applications, Acoustic Exchange provides a way to map identifier and attribute names between the two applications.
Acoustic Exchange endpoints that provide audience data are referred to as audience sources.
When you register an audience source endpoint on behalf of an Acoustic Exchange user account, you must indicate that the endpoint provides audience data. You also specify at least one unique identifier that can be used to identify individual members of the audience. You can also specify other descriptive attributes that the audience contains.
After you complete endpoint registration, the endpoint appears in the Acoustic Exchange interface and is identified as an audience source. The identifiers and attributes are also available in the Acoustic Exchange interface. When users share audiences, they can use the Acoustic Exchange interface to map identifiers and attributes in the source audience to corresponding attributes in the destination audience.
Acoustic Exchange endpoints that consume audience data are referred to as audience destinations.
When you register an audience destination endpoint on behalf of an Acoustic Exchange user account, you must indicate that the endpoint consumes audience data. You specify the identifiers and attributes that the destination audience contains.
The identifiers and attributes appear in the Acoustic Exchange interface so that users can map the names between the source audience and the destination audience.
Acoustic Exchange provides a collection of public REST APIs that endpoints call to connect to Acoustic Exchange as producers and consumers of event and audience data.
The APIs include various properties to provide customer identifiers and event attributes as part of the API call.
Calls to Acoustic Exchange public APIs must contain a valid authentication key that Acoustic Exchange provides to Acoustic Exchange users for each endpoint that they register. The authentication key identifies the Acoustic Exchange endpoint and a specific Acoustic Exchange user account that is associated with the endpoint.
All data exchanges through Acoustic Exchange occur on behalf of a specific Acoustic Exchange user and user account. Including an authentication key with each API call ensures that the data is directed to the correct destination and that customer identifiers are attributed to the correct Acoustic Exchange account. Acoustic Exchange does not share identifier data across Acoustic Exchange accounts.
The authentication key must appear in the HTTP header of the API call. Acoustic Exchange rejects any API call that does not specify an authentication key that Acoustic Exchange can associate with a valid Acoustic Exchange account.
For a complete description of the Acoustic Exchange public APIs, see
Access to Acoustic Exchange user accounts requires entering a user name and password that Acoustic Exchange creates for each Acoustic Exchange user account. You must contact support to create an Acoustic Exchange account.
As an endpoint provider, you receive a Acoustic Exchange account in the Acoustic Exchange pilot environment that you can use for endpoint testing before going live in the Acoustic Exchange Production environment. Acoustic Exchange provides the URL and credentials to access the pilot environment.
Acoustic Exchange users receive Acoustic Exchange account credentials that include a URL and credentials for the Acoustic Exchange production environment. As an endpoint provider, you can request a user account for testing purposes.
Updated 6 months ago