Adobe Target gives rest apis that can be utilized to broaden Drupal/Acquia to make and dispatch tests specifically from the CMS interface. Adobe AEM accompanies these augmentations officially incorporated with the device - which additionally depends on a similar Target APIs for the reconciliations.

For substance conveyance, you have a decision between utilizing Adobe Target's javascript library ( mbox.js ) on the site to call Target servers straightforwardly from the customers program - or have the CMS server call Target on the server side. The server side alternative is prescribed in such situations - as it lessens the quantity of round outings from the program on page stack.

In synopsis, running with Drupal/Acquia would require some improvement exertion on your part to incorporate with Target. This combination comes "out of the container" with AEM.

Please correct me if I'm wrong or give me some sugesstions on this.

Thanks&Regards

Katherine