Your customers are likely to abandon a form if the experience it delivers is not engaging. While it is frustrating for the customers, it can also upturn the support volume and cost for your organization. It is critical as well as challenging to identify and provide the right customer experience that increases the conversion rate. Adobe Experience Manager Forms holds the key to this problem.
AEM Forms integrates with Adobe Target, an Adobe Marketing Cloud solution, to deliver personalized and engaging customer experiences across multiple digital channels. One of the key capabilities of Target is A/B testing that allows you to quickly set up concurrent A/B tests, present relevant content to targeted users, and identify the experience that drives better conversion rate.
With AEM Forms, you can set up and run A/B tests on adaptive forms in real time. It also provides out-of-the-box and customizable reporting capabilities to visualize real-time performance of your form experiences and identify the one that maximizes user engagement and conversion.
Before you begin to create and analyze A/B tests for adaptive forms, you need to set up your Target server and integrate it in AEM Forms.
To integrate AEM with Target, ensure that you have a valid Adobe Target account. When you register with Adobe Target, you receive a client code. You need the client code, email associated with Target account, and password to connect AEM with Target.
The Client Code identifies the Adobe Target customer account and is used as a sub-domain in the URL when calling the Adobe Target server. Before proceeding, log on to https://experience.adobe.com/ and, if you have access, view the Adobe Target option in the Quick Access section.
Perform the following steps to integrate a running Target server with AEM Forms:
On AEM server, go to https://<hostname>:<port>/libs/cq/core/content/tools/cloudservices.html.
In the Adobe Target section, click Show Configurations and then the + icon to add a new configuration.
If you are configuring target for the first time, click Configure Now.
In the Create configuration dialog, specify a Title and optionally a Name for the configuration.
Click Create. The Edit component dialog opens.
Specify your Target account details, such as client code, email, and password.
Select Rest from the API Type drop-down list.
Click Connect to Adobe Target to initialize the connection with Target. If the connection is successful, the message Connection successful is displayed. Click OK on the message and then OK on the dialog. The Target account is configured.
Create a Target framework as described in Add a framework.
Go to https://<hostname>:<port>/system/console/configMgr.
Click AEM Forms Target Configuration.
Select a Target Framework.
In the Target URLs field, specify all the URLs where A/B tests will run. For example, https://<hostname>:<port>/ for AEM Forms server on OSGi or https://<hostname>:<port>/lc/ for AEM Forms server on JEE.
Consider that you want to configure a Target URL for a publish instance and your customers can access it using the hostname or the IP address, you will need to configure both as Target URLs - using the hostname as well as the IP address. If you confgure only one of the URLs, your A/B test will not run for customers coming from the other URL. Click + to specify multiple URLs.
Your Target server is integrated with AEM Forms. You can now enable A/B testing if you have a full license to utilize Adobe Target.
If you have a full license to utilize Adobe Target, start the server with the following parameters after you integrate Target with AEM Forms:
parameter -Dabtesting.enabled=true java -Xmx2048m -XX:MaxPermSize=512M -jar -Dabtesting.enabled=true
If the AEM instance is running on JBoss, started as a service from turnkey, in
jboss\bin\standalone.conf.bat file, add -Dabtesting.enabled=true parameter in the following entry:
set "JAVA_OPTS=%JAVA_OPTS% -Dadobeidp.serverName=server1 -Dfile.encoding=utf8 -Djava.net.preferIPv4Stack=true -Dabtesting.enabled=true"
In addition to jboss server, you can add -Dabtesting.enabled=true jvm argument in server startup script for any application server. Now you can create and run A/B tests for adaptive forms.
If you update the configured Target URLs later, ensure that you update any running A/B tests so that they point to the current URLs. For information about updating A/B tests, see Update A/B test.
AEM lets you create an audience, and use it for an A/B test. The audience you create within AEM is available in AEM Forms. Perform the following steps to create audiences within AEM:
In authoring instance, tap Adobe Experience Manager > Personalization > Audiences.
In the Audiences page, tap Create Audience > Create Target Audience.
In the Adobe Target Configuration dialog, select a Target configuration and click Ok.
In the Create New Audience page, create rules. Rules let you categorize the audience. For example, you want to categorize audiences based on operating system. Your audience A comes from Windows, and audience B comes from Linux.
Specify a name for the created audience, and click Save.
You can select the audience when you configure A/B testing for a form, as shown below.
Perform the following steps to create an A/B test for an adaptive form.
Go to Forms & Documents at https://<hostname>:<port>/aem/forms.html/content/dam/formsanddocuments.
Navigate to the folder containing the adaptive form.
Click the Select tool in the toolbar and select the adaptive form.
Click More in toolbar and select Configure A/B Testing. The Configure A/B testing page opens.
Specify an Activity Name for the A/B test.
From the Audience drop-down list, select an audience to whom you want to serve different experiences of the form. For example, Visitors Using Chrome. The audience list is populated from the configured Target server.
In the Experience Distribution fields for experiences A and B, specify the distribution, in terms of percentage, to determine the distribution of experiences among the total audience. For example, if you specify 40, 60 for experiences A and B, respectively, the experience A will be served to the 40% of the audience and the remaining 60% will see the experience B.
Click Configure. A dialog appears to confirm the creation of the A/B test.
Click Edit Experience B to open the adaptive form in the edit mode. Modify the form to create a different experience than the default experience A. The possible variations allowed in Experience B are changes in:
Go to the Forms and Documents UI, select the adaptive form, click More, and select Start A/B Testing.
You A/B test is now running and the specified audience will be randomly served the experiences based on the specified distribution.
You can update the audience and experience distributions of a running A/B test. To do so:
In the Forms & Documents UI, navigate to the folder that contains the adaptive form on which the A/B test is running.
Select the adaptive form.
Click More and then select Edit A/B testing. The Update A/B testing page opens.
Update the audience and experience distributions, as required.
Once you have allowed the A/B test to run for the desired period, you can generate a report and check which experience has resulted in better conversion. You can declare the better performing experience a winner or choose to run another A/B test. To do this, perform the following steps:
Select the adaptive form, click More, and then click A/B Testing Report. The report gets displayed.
Analyze the report and see if you have enough data points to declare one of the better performing experiences as a winner. You can choose to continue with the same A/B test for more time or declare a winner and end the A/B test.
To declare a winner and end the A/B test, click End A/B test button on the reporting dashboard. A dialog prompts you to declare one of the two experiences as winner. Choose a winner and confirm to end the A/B test.
Alternatively, you can first declare a winner by clicking the Declare Winner button for the respective experience. It prompts you to confirm the winner. Click Yes to end the A/B test.
If you picked experience A as the winner, the A/B test will be put to an end, and going forward, only Experience A will be served to all the audiences.