Adobe Target A/B Testing with AEM as a Cloud Service Adaptive Forms | Community
Skip to main content
R
rockstar234
Level 2
August 17, 2026
Question

Adobe Target A/B Testing with AEM as a Cloud Service Adaptive Forms

  • August 17, 2026
  • 1 reply
  • 8 views

Question: Adobe Target A/B Testing with AEM as a Cloud Service Adaptive Forms

Hi ,

I’m currently using AEM as a Cloud Service with Adaptive Forms based on Core Components.

I would like to understand whether Adobe Target is supported with this setup, specifically for running A/B tests on Adaptive Forms.

If it is supported, could someone please share the recommended implementation approach and steps for:

  1. Integrating Adobe Target with AEM as a Cloud Service.

  2. Setting up A/B testing for an Adaptive Form using Core Components.

  3. Creating two different form experiences/variations in Adobe Target.

  4. Configuring the audience and traffic split (for example, 50/50).

  5. Tracking form submissions/conversions as the success metric.

  6. Using A4T/Analytics for reporting, if applicable.

  7. Any required Web SDK, Tags/Data Collection, Target client-side libraries, or Cloud Service configurations.

  8. Any limitations or prerequisites specific to Adaptive Forms Core Components.

If someone has implemented this successfully, a step-by-step guide or example architecture would be greatly appreciated.

Thanks!

 

1 reply

P
Adobe Employee
Pranay_MAdobe Employee
Adobe Employee
August 18, 2026

Hi ​@rockstar234,

Thanks for the detailed question. Here's where things stand:

Short answer: Yes, Adobe Target is supported with AEM as a Cloud Service for A/B testing Adaptive Forms — but the integration path is different from what you may find in older AEM documentation.

**Important distinction**
The legacy AEM Forms ↔ Target connector (the one with a dedicated "client code/email/password" config screen and built-in Forms Analytics reports) has reached end-of-life and is no longer supported. That integration was built for Foundation Component-based forms and doesn't apply to Core Components on AEM as a Cloud Service.

For your setup, the supported approach is to use the same Experience Platform Web SDK / Tags integration that AEM Sites uses to connect to Target and Analytics, leveraging the Adobe Client Data Layer that's already built into the Adaptive Forms Core Components.

**Recommended approach, step by step:**

1. **Target integration**: Set up a Tags (Data Collection) property linked to your AEM environment via Adobe IMS, and deploy the Experience Platform Web SDK through it. Most of the IMS setup is auto-provisioned on AEM as a Cloud Service.

2. **A/B test setup**: There's no built-in "A/B test" button for Core Components forms in AEM's authoring UI (that belonged to the deprecated flow). Instead, configure the test in Target itself, targeting the form's rendered DOM.

3. **Creating variations**: For structural changes (added/removed fields, layout changes), author two separate Adaptive Forms or experience fragments and let Target route traffic between them. For smaller visual/content tweaks, use Target's Visual Experience Composer directly on the form markup.

4. **Audience/traffic split**: Standard Target A/B Test activity setup — no form-specific steps. Set your 50/50 split in the activity's traffic allocation.

5. **Conversion tracking**: Hook into the Core Components submit-complete lifecycle event and fire it into the data layer / via Tags. Use that as your Target success metric.

6. **A4T/Analytics reporting**: Fully supported — send the same submit event to Adobe Analytics via Web SDK/Tags and enable A4T on the activity for Analytics-based lift reporting.

7. **Required components**: Experience Platform Web SDK (alloy.js), a Tags property linked via IMS, and the Adobe Client Data Layer (already built into Core Components). You do not need the old Forms-specific Target Cloud Service configuration.

**One limitation to flag:** If the form is embedded on a page outside of native AEM Sites/Forms rendering (e.g., an external website), Target experience targeting and A/B tests configured on the original form will not carry over, and submission data won't appear in Forms-specific reports. Keep the tested form on a natively rendered AEM page for this to work correctly.

Happy to go deeper on the actual data layer event names for submit tracking, or walk through a sample Target activity configuration for a form-swap A/B test if that would help your team get started.
 

Thanks
Pranay

Terms & ConditionsAccessibility statement

Loading footer...