The Acoustic Exchange-DSP Offer Optimization integration allows you to sync your ad placement and audience sharing partner IDs (for example, MediaMath or The Trade Desk), Interact, and cookie IDs using JavaScript accessible APIs in order to optimize ad placement or share audiences.
Acoustic Exchange is a cloud-based service from Acoustic that provides a way to selectively exchange event and identity data between various Acoustic and client second-party marketing automation and analytics applications.
A demand-side platform (DSP) automates the execution of paid media buying across all channels, and optimize campaigns in real time.
Leverage Acoustic Exchange to syndicate offer recommendations to partners so that your customers receive timely and relevant offers. With this integration, you can receive offer responses (Viewed, Accepted, and Rejected) from ad placement partners so that future offer recommendations are based on continuous learning.
You can integrate your demand-side platform with Unica Campaign to share audiences through your demand-side platform.
With the Interact integration, leverage Acoustic Exchange to syndicate offer recommendations to partners so that your customers receive timely and relevant offers. With this integration, you can receive offer responses (Viewed, Accepted, and Rejected) from ad placement partners so that future offer recommendations are based on continuous learning.
The Acoustic Exchange-DSP Offer Optimization integration with Interact also leverages Interact Omni-channel Message Orchestrator to deliver offers through various channels.
Sample ID sync
The ID sync is required for Acoustic Exchange integration with any demand-side platform.
To perform an ID sync, you need to combine JavaScript that invokes the ID sync with your demand-side platform pixel.
You can use the sample JavaScript and pixels as examples for your Acoustic Exchange integration with your demand-side platform.
The ID sync may not work properly if third-party cookies are not enabled because the ID sync typically relies on the DSP to set their cookies in the browser.
Use the GET /v1/endpoint/{endpointId}/eventinfo
API to use an authentication key that is only used by browsers to send events. To use this API, you must use an authorization header with your endpoint authorization key.
It returns a simple JSON object.
{
"endpointId": ...,
"eventAuthKey": ...
}
The GET /v1/endpoint/{endpointId}/eventinfo
call only needs to be done once. After you make this call, you must use the eventAuthKey
in the /v1/customEvent
API.
Sample JavaScript
This sample JavaScript is where a matched Identity event occurs when a user logs in to a website.
<script type="text/javascript">
function getuserId()
{
// Fill in this function to retrieve and return the client user id
from the page
return null;
}
try
{
var USER_ID = getuserId();
if (USER_ID)
{
var DSP_PIXEL_URL = "{Replace with DSP ID Sync Pixel URL}";
var DSP_NAME = "{Replace with DSP Name}";
var DSP_UUID ="{Replace with DSP UUID Name}";
var USER_ID_Name = "{Replace with Partner User ID Name}";
var UBX_HOST = "{Replace with Exchange Host Name}";
var AUTHKEY = "{Replace with Exchange DSP Endpoint Auth Key}";
//Exchange URL Format is
https://{UBX_HOST}/v1/customevent/matchedIdentity/{AUTHKEY}/DSPID_{DSP_NAME}
={DSP_UUID}/{USER_ID_Name}={USER_ID}
var UBX_CALLBACK_URL = encodeURIComponent("https://"+UBX_HOST+"
/v1/customevent/matchedIdentity/"+AUTHKEY+"/DSPID_"+DSP_NAME+"=") +
DSP_UUID + encodeURIComponent
("/"+USER_ID_Name+"="+USER_ID);
var DSP_FINAL_CALLBACK_URL = DSP_PIXEL_URL + UBX_CALLBACK_URL;
new Image().src = DSP_FINAL_CALLBACK_URL;
}
}
catch (err) {
console.log('Error:'+err.message);
}
</script>