Acoustic Campaign as an audience producer

This example illustrates how to configure v1/endpointattributes to provide Acoustic Exchange with the login and connection information it requires to receive audience data from Acoustic Campaign.

PUT v1/endpointattributes
 
{
   "podUrl" : "http://api-<campaign-us-X>.goacoustic.com/,
   "refreshToken" : "<account-specific refresh token>"
} 

<number> corresponds to the number of the Acoustic Campaign pod to which your organization is assigned. For example, if your organization uses Acoustic Campaign pod1, the value for xmlAPIUrl is http://api-campaign-us-1.goacoustic.com. For a complete list of updated URLs, click here.

The refresh token is the refresh token provided by Acoustic Campaign for your organization.

Acoustic Digital Analytics as an audience source

This example illustrates how to configure v1/endpointattributes to provide Acoustic Exchange with the login and connection information that it requires to receive audience data from Acoustic Digital Analytics.

{
  "clientID" : "<clientID>",
  "user": "<Digital Analytics user name>",
  "password":"<Digital Analytics password>",
  "exportAPIUrl":"https://export.coremetrics.com/eb/segmentapi/1.0/api.do"
}

Facebook as an audience consumer

This example illustrates how to configure v1/endpointattributes to provide Acoustic Exchange with the login and connection information that it requires to download audience data to Facebook.

{
   "redirectURI":"http://localhost:8080/WebApplication1/NewServlet",
   "adAccountID":"<accountID>",
   "accessToken":"<access token>",
   "clientID":"<facebook client ID>",
   "clientSecret":"<facebook client secret>" //
}

accessToken: The user must generate an access token for Acoustic Exchange to use to access the user's Facebook account.

clientID: This value is required so that Acoustic Exchange can automatically renew the accessToken.

clientSecret: This value is also required so that Acoustic Exchange can automatically renew the accessToken.