Tagging with Acoustic Exchange Capture and DDX

Great news! and DDX are entirely compatible! Here is how tagging will work when you use Capture.

When Capture enables Acoustic Digital Analytics, DDX tagging is included automatically. Be aware that for a Capture enablement, the library for the enabled application is loaded and DDX does not need to deploy any Partner Library enablement tagging for the application. As you enable tagging in oneSDK, the same tags should be removed in DDX. Similarly, as you add new partners to Capture, their library loads have to be removed from DDS.

You can use Capture to load Acoustic Experience Analytics and idSync as well and still load vendors with DDX and use it for tagging. Using Capture and Acoustic Experience Analytics in conjunction gives you the benefit of a common session ID.

Capture cannot migrate data from DDX as of now. Note that Capture always loads DDX when it loads Digital Analytics. This means that you can migrate your data whenever you get a chance.

Updated about a year ago

Tagging with Acoustic Exchange Capture and DDX

Suggested Edits are limited on API Reference Pages

You can only suggest edits to Markdown body content, but not to the API spec.