Adobe Target Experiment Targeting Issue/ Visitor qualification for audience

[anujrajput0109]

Hello ,

Issue Description: I am encountering a challenge with the targeting of my experiment. The website is a single-page application with a booking funnel consisting of six steps. On step 5, users have the option to either fill in guest details or log in to the website. The login functionality opens a modal where users enter their credentials.

I have set up a Target activity to show only for logged-in users by firing a view named "Booking funnel step - 5" when the login modal is opened and successfully logged in. However, the experiment changes are not reflected immediately for logged-in users; I have to refresh the page to see the updated experience.

Key Details:

1. Adobe Target VEC used for experiment setup.
2. Single-page application architecture with dynamic rendering of booking funnel steps.
3. Views fired at site are "Booking funnel step - 5," "Login modal," and again "Booking funnel step - 5" after successful login.

Desired Outcome: The experiment should dynamically adjust for logged-in users after successful login without requiring a page refresh. I am expecting to see the changes from the experiment when view fires again for the step - 5 after successful login.

Additional Information:

• Experiment setup includes specific conditions for showing changes to logged-in users.
• Views are properly firing when users interact with the login modal and successfully log in.

I am aware that audience validate on each mbox call but how can I make it work for the view in VEC?

[alexbishop]

Could you provide some information on what the "Experiment setup includes specific conditions" part includes?

[anujrajput0109]

1. AB Test Experiment using Visual Experience Composer. 
2. View are used to deliver the content instead of page load event.
3. Audience using custom>All Mboxes> parameter to validate the user. I can verify launch is successfully adding params to all request(Including TriggerView call) that are mandatory for the authentication of user.
   
   Here is a revised response for better understanding. 

The AB test experiment, executed through the Visual Experience Composer (VEC), is currently active for the "Booking funnel step - 5" view, targeting users categorized within the "Logged In users" audience. The audience specification mandates the inclusion of parameters in all network calls to Adobe Target, facilitating the validation of user authentication status for targeted delivery.

It's imperative to note that our platform operates as a single-page application, meaning page transitions occur without explicit reloads. Consequently, the expected behavior dictates that upon the initial firing of "Booking funnel step - 5," users who are not logged in should not encounter the experiment. Conversely, once a user logs in and triggers the "Booking funnel step - 5" view again, the experiment should commence delivery of its content as the user qualifies for the targeted audience.

To ensure accurate audience evaluation, the TriggerView call for "Booking funnel step - 5" includes the transmission of the Logged-in-True parameter to Adobe Target, facilitating audience segmentation based on user authentication status.

However, despite these measures, the experiment's content is not dynamically displayed for logged-in users without a page reload. The expected behavior is observed only upon manual page refresh.

The desired outcome is for the experiment to dynamically adapt to user authentication changes without necessitating a page reload, enabling seamless delivery of the experiment's content to logged-in users.

---

Feel free to incorporate this revised response into your communication. If you have any further questions or require additional adjustments, please let me know!

[alexbishop]

If a view change has potential to qualify/disqualify a customer then you would use getOffers() (with additional parameters as necessary) & then call triggerView() to then render the content from cache. More details around order of operations is listed here

[anujrajput0109]

Thanks for the solution. 
It makes sense to use getOffers() before triggerView() to update the cache. 
We are using Adobe Launch for the at.js Implementation, If you could please share how we can use getOffers() with adobe target v2 extension in launch would give me a complete solution on this. Thanks Again

Here are my suggestions : 
1. Add one action before firing a triggerView() call using core extension.
Actions > Add, then Select Action Type > Custom Code, then Open Editor and paste below code. 

adobe.target.getOffer({
  "mbox": "custom_mbox_name",
  "params":{
    "Param1": value1,
    "param2": Value2
  },
  "success": function(offer) {
    adobe.target.applyOffer({
      "mbox": "custom_mbox_name",
      "offer": offer
    });
  },
  "error": function(status, error) {
    console.log('Error', status, error);
  }
});

2. Add one action before firing a triggerView() call using Adobe Target V2 extension .
Actions > Add, then select Adobe Target V2 extension, then Select Action Type > Fire Page Load Request, then click Save. 

[alexbishop · Accepted solution]

You will actually need to use a custom code action because getOffers() doesn't have an equivalent action type (see list here) in the Target v2 extension. You can find a full example of how to chain getOffers > applyOffers > triggerView here.