The distinction between exchanging data as PUSH or PULL depends on how the data moves between an endpoint and Acoustic Exchange. The way that data flows between endpoints and Acoustic Exchange determines how the Acoustic Exchange APIs are called or implemented by the endpoint.

Acoustic Exchange recognizes the following syndication types. Depending on the types of data exchanges that your product or solution supports, you can select more than one data syndication type.

Event publisher: PUSH. All Acoustic Exchange endpoints publish event data to Acoustic Exchange as a PUSH-type event publisher. Publishing events to Acoustic Exchange also requires an API call to Acoustic Exchange.

Event consumer: PUSH. An endpoint that receives event data that Acoustic Exchange sends as soon as it is available is considered a PUSH-type event consumer.

Event consumer: PULL. An endpoint that receives event data only when it specifically requests the data from Acoustic Exchange is considered a PULL-type event consumer.

Audience producer: PULL. 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.

Audience producer: PUSH. 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.

Audience consumer: PULL. 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.

Audience consumer: PUSH. 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. Often, cloud-based business applications (also called SaaS applications) connect to Acoustic Exchange as a push-type audience consumer.