Experimentation (A/B Testing)

In AEM, click the Experience Fragments card, navigate to Camping in Western Australia, and click Edit.

In the editor, under the Variations section, click Create, and select Variation.

In the Create Variation dialog:

• Template: Experience Fragment Web Variation Template
• Title: For example, “Off the Grid”

Click Done.

Author the variation by copying the Teaser component from the master variation, then customize the content (e.g., update the title and image).

Repeat the steps to create another variation (e.g., “Wandering the Wild”).

You now have three Experience Fragment variations for A/B testing.

Before displaying variations using Adobe Target, you need to remove the existing static teaser from the homepage. It prevents duplicate content, as the Experience Fragment variations are injected dynamically via Target.

• Navigate to the English homepage /content/wknd/language-masters/en
• In the editor, delete the Camping in Western Australia teaser component.
  

Roll out the changes to the US > English homepage (/content/wknd/us/en) to propagate the updates.

Publish the US > English homepage to make the updates live.

In AEM, navigate to Camping in Western Australia, select the three variations, and click Export to Adobe Target.

In Adobe Target, go to Offers and confirm the variations have been imported.

Install the Adobe Experience Cloud Visual Editing Helper Chrome extension.

In Adobe Target, navigate to Activities and click Create Activity.

In the Create A/B Test Activity dialog, enter the following:

• Type: Web
• Composer: Visual
• Activity URL: e.g., https://wknd.enablementadobe.com/us/en.html

Click Create.

Rename the activity to something meaningful (e.g., “WKND Homepage A/B Test”).

In Experience A, add the Experience Fragment component above the Recent Articles section.

In the component dialog, click Select an Offer.

Choose the Camping in Western Australia variation and click Add.

Repeat for Experience B and C, selecting Off the Grid and Wandering the Wild respectively.

In the Targeting section, confirm the traffic is split evenly across all experiences.

In Goals & Settings, define your success metric (e.g., CTA clicks on the Experience Fragment).

Click Activate in the top-right corner to launch the test.

In Adobe Experience Platform, navigate to Datastreams and click Create Datastream.

In the Create Datastream dialog, enter a Name for your Datastream and click Save.

Once the Datastream is created, click Add Service.

In the Add Service step, select Adobe Target from the dropdown and enter the Target Environment ID. You can find the Target Environment ID in Adobe Target under Administration > Environments. Click Save to add the service.

Review the Datastream details to verify that the Adobe Target service is listed and correctly configured.

In Adobe Experience Platform, navigate to Tags and open the property you created in the Integrate Adobe Tags step.

From the left-hand menu, click Extensions, switch to the Catalog tab, and search for Web SDK. Click Install in the right-side panel.

In the Install Extension dialog, select the Datastream you created earlier and click Save.

After installing, verify that both Adobe Experience Platform Web SDK and Core extensions appear under the Installed tab.

Next, configure a rule to send the Web SDK event when the library is loaded. Navigate to Rules from the left-hand menu and click Create New Rule.

In the Create Rule screen, enter a rule name (for example, All Pages - Library Loaded - Send Event) and click + Add under the Events section.

In the Event Configuration dialog:

• Extension: Select Core
• Event Type: Select Library Loaded (Page Top)
• Name: Enter Core - Library Loaded (Page Top)

Click Keep Changes to save the event.

Under the Actions section, click + Add to define the action that occurs when the event fires.

In the Action Configuration dialog:

• Extension: Select Adobe Experience Platform Web SDK
• Action Type: Select Send Event
• Name: Select AEP Web SDK - Send Event

In the right panel’s Personalization section, check the Render visual personalization decisions option. Then, click Keep Changes to save the action.

Review the completed rule and click Save.

To apply the changes, go to Publishing Flow, add the updated rule to a Library.

Finally, promote the library to Production.

Visit the published site (for example, WKND Enablement website) and observe which variation is displayed. Try accessing it from a different browser or mobile device to see alternate variations.

Open your browser’s developer tools and check the Network tab. Filter by interact to find the Web SDK request. The request should the Web SDK event details.