To offer guidance for publishing and subscribing to event data, Exchange provides a list of events that Exchange recognizes as typical activities in common business situations. Exchange refers to these events as recognized events.
Different business applications view and track customer and entity interactions in different ways. Each application can observe different interactions and record data for different attributes for each interaction. Because Exchange provides a way to view customer actions across multiple applications, it establishes a standard framework for describing typical business interactions. This framework is described in the Acoustic Exchange event catalog.
The event catalog lists various identifier and descriptive attributes that event publishers can use to describe an event. As an event publisher, you can provide values for all of the standard event attributes, or for only few of them. However, some attributes are required of all events.
Event publishers might not provide values for every possible attribute in an event. Endpoints that subscribe to events must design their systems to ignore missing values in the JSON payload that Acoustic Exchange provides when it delivers the event data to the subscribing endpoint.
Acoustic Exchange defines several types of recognized events and organizes them into classes that are based loosely on the channel in which the events are observed.
Acoustic Exchange defines the following event types.
- Web Events
- Email Events
- Mobile Events
- Social Events
- SMS Events
- Contact Center Events
- Aggregate Events
Exchange also recognizes custom events that are defined by Exchange Business Partners, but only after consultation and agreement on the event name, event code, and support for event attributes. Such consultation helps ensure that Exchange can correctly recognize and process the data that the custom event promises to deliver.
If Exchange recognized events do not adequately describe the event data that an endpoint can provide, the endpoint can define a custom event.
Endpoints that define custom events typically define custom event attributes. However, the endpoint must use caution when it defines an event code for a custom event. Event publishers cannot use an event code that is already used by an Exchange recognized event. To avoid potential confusion and errors, consult with Exchange before defining a custom event.
Endpoints that subscribe to custom events must consult with the event publisher to determine the event attributes that they can expect.
Event publishers cannot add custom event attributes to an Exchange recognized event.
Every event that you publish to Exchange must define attributes that describe the event. The number and quality of attributes that you include in the event can improve the value of the event notification to event subscribers and Exchange users.
When an endpoint publishes an event, the call to v1/event typically includes several event attributes. Each attribute specifies a name, value, and data type. The attributes in the event notification must include required attributes. The event notification might also include certain recommended attributes that are considered best practice attributes. The publishing endpoint might also include other attributes that Exchange considers general attributes.
Exchange requires specific event attributes to distinguish between events, facilitate identity enhancement by the Exchange Identity Service, and to properly represent the event in the Exchange user interface. Some descriptive attributes of published events, specifically, the event code and event name, are defined when an endpoint registers the event with Exchange.
Exchange reserves specific property names for recognized events. When you register and publish a recognized event, use only the reserved property names.
Exchange requires that you define specific attributes for all published events. Exchange applies depending on the type of event, or on the specific event, Exchange might impose more attribute requirements.
Exchange requires that you define the following attributes for all published events, including Exchange recognized events and custom events.
- channel Where the event was observed.
- name Name of the type of identifier that is used to identify the individual or entity that initiated the event. For example, emailAddress.
- value The identifier value for the specific event that is being published by the endpoint.
- code The event code that Acoustic Exchange assigned to the event. Acoustic Exchange assigns a unique event code to recognized and custom events.
- Timestamp The date and time when the event was observed. The time must be submitted in ISO-8601 format.
For example, for social event publishers, unique user identifiers such as User ID, User Name (Facebook and Instagram), Twitter Handle, Twitter ID (Twitter), are required attributes that you define as identifiers during endpoint registration and include when you publish events from the endpoint.
The following example illustrates the structure of the JSON payload in the call to
v1/event to publish an event.
The type of device or method that the individual uses to interact with the business or service provider.
For example, mobile if the customer used a cell phone.
Required for individual events.
One or more unique name-value pairs that can be associated with a specific individual and only that individual.
Acoustic defines the event code to identify the specific event. You must use the Exchange event code. Do not create a different one.
The time stamp indicates when the event was observed by the publishing endpoint, not when the endpoint transmits the event notification. The format must be ISO-8601.
The list of attributes that describe the event. The attributes that are included in the JSON package depend on the event.
The attributes section must contain values for all required attributes for the event. You can add other attributes, depending on the information that the business application can gather and report.
Exchange has identified various event attributes that can be added to most event definitions
to enhance the potential insights that Exchange users can derive from the event notification.
Best practice attributes are based on the experience of Exchange and Acoustic Exchange Business Partners.
The examples that are presented are typical values. They do not represent the only values that are possible or acceptable.
Category for a commercial activity or tactic.
A tracking code for a commercial activity or tactic. Usually associated with the event for attribution purposes.
Name of the activity or tactic.
Name of the application used during the interaction.
Version of the application used during the interaction.
URL location for a physical asset.
Browser used on the device used during the interaction.
Browser version used on the device used during the interaction.
Category for a campaign conducted to generate customer interactions.
Tracking code for a campaign conducted to generate customer interactions.
New Year - New Opportunities!
Name of the campaign conducted to generate customer interactions.
Carrier vendor of a mobile device.
Classify a channel as owned or paid media.
Wireless connection speed.
Not case sensitive.
Example value: sms,opt-out
Indicates that an individual does not want to receive SMS messages.
Communication consent preference for an individual, as recorded by a messaging endpoint.
Indicates channel and preference.
Device screen depth
Type of device used during a customer event.
Permissible use of identifier as defined by the publisher of the event or identity.
Note: Null defaults to Join.
Person or system that initiated the event. You can set the default during event registration.
IP address of the device that was used during the event.
Unique identifier for a visit. Sometimes called a session ID. Can be used to connect related
For example, if a cookieId identifies a visitor, the
A null value is acceptable, but you must generate a unique value when you publish the event.
Classification to the event. For example, distinguish between events that generate revenue and events that do not generate revenue.
You can set the default during event registration.
Event location latitude.
Event location locale.
Event location address.
Event location city.
Event location country.
Event location name.
Event location region.
Event location longitude.
Model of the device.
Classification category for an offer.
Offer code, for attribution.
Name of the offer.
Type of offer.
Operating system of the device used during an event.
Platform or client used on the device during an event.
Device screen resolution.
Stage or phase that describes the customer journey status of the event.
(Typical examples. Not an inclusive list.)
A more granular descriptor of the channel where an event occurred.
Exchange privilege key mapping for published identifier. Used to join identities by identity type.
Vendor of the device used during an event.
Operating system version of the device used during an event.
Updated over 2 years ago