Hi @rockstar234,
Subject: RE: Documentation for Core Components Adaptive Forms A/B Testing
Hi [Name],
Thanks for the update — great to hear the IMS integration is in place and your form variations are set up as Experience Fragments pushed to Target.
To directly answer your question: **there isn't a dedicated Adobe document for "Core Components Adaptive Forms end-to-end A/B testing."** The Forms-specific A/B testing documentation you may come across is for the legacy OSGi-based integration, which has reached end-of-life and doesn't apply to a Web SDK + Experience Fragments setup like yours.
That said, since your architecture (IMS, Web SDK, Experience Fragments as Target offers) is functionally the same pattern AEM Sites uses, the closest and most relevant official walkthrough is Adobe's Sites experimentation tutorial. It covers the exact mechanics you've already implemented — just demonstrated on a Sites page rather than a form:
1. **Experimentation (A/B Testing) — AEM as a Cloud Service**
https://experienceleague.adobe.com/en/docs/experience-manager-learn/cloud-service/personalization/use-cases/experimentation
End-to-end flow: exporting Experience Fragment variations to Target as offers, creating a Datastream to connect Web SDK to Target, building the A/B Test activity, setting the traffic split, defining success metrics, and activating.
2. **Use Adobe Target and Web SDK for personalization**
https://experienceleague.adobe.com/en/docs/target-dev/developer/client-side/aep/target-overview
Explains the Web SDK + Target edge decisioning architecture (Datastream, Edge Network, A4T handoff) underlying any AEM as a Cloud Service A/B test, including form-based ones.
3. **How Do I Use AEM Experience Fragments? — Adobe Target**
https://experienceleague.adobe.com/en/docs/target/using/integrate/aem/fragments/experience-fragments-aem
Covers exporting Experience Fragments as Target offers and consuming them via the Visual Experience Composer or Form-Based Experience Composer — the same offer-export step you've already completed.
**A few things worth validating on your specific setup, since none of the above documents address Forms directly:**
- **Duplicate/default content**: Confirm your Adaptive Form's container isn't rendering a hardcoded default fragment alongside the one Target injects dynamically — the Sites tutorial calls out removing the static default before activating, and the same applies here to avoid a flash of the wrong experience.
- **Datastream vs. legacy config**: Make sure your Datastream (not the older mbox/at.js-based Target Cloud Service config) is what's routing requests to Target, since that fully replaces the legacy integration.
- **Form model initialization timing**: Core Components Adaptive Forms initialize a client-side FormJSON model on load. Worth checking that this doesn't fire before the Web SDK personalization block resolves and swaps in Experience B — Target's page-hiding snippet should handle this, but it's worth confirming in the DOM.
- **Submit event coverage**: Since each experience is a separate Experience Fragment/form instance, verify your submit-success data layer event is registered on both variants, not just the default-rendered one.
Happy to put together a validation checklist or a short script to confirm the Web SDK personalization block is properly gating the form's model initialization, if that would help move testing along.
Thanks
Pranay