Event Handler for Clickable Banners

[JyotiSharmaV]

i have a experience fragment activity created with three experiences with different audiences. The change in these 3 experience is display of different home page banners on my home. However, i have been checking the Activity QA link for experiences and found that the changes in my experiences are reverting back many times to default. Why this is happening?

Also, if I would like to change the navigation link of my clickable banner then how should I do that? I did try the Edit HTML and update the link but that is in methodology of event handler as AEM assignment so my changed url navigation link is not getting updated. How can I take care of it in Target?

[JyotiSharmaV]

@alexbishop any thoughts on this?

[alexbishop]

For your first point where you say "reverting back to default", a couple of questions:
i) do you see that you are qualifying for Exp B (based on the response from Target) but you see Exp A default content?
ii) if so, do you never see Exp B content or do you initially see it and then it gets overwritten by default?

In terms of the navigation link, if you're using Experience Fragments, then it would make most sense to update the link as part of the XF in AEM. Is that not possible?  

[JyotiSharmaV]

@alexbishop I have created 5 different experiences and as I mentioned I was able to replace the home page banner for all three 5 different experiences. When I mention revert back to default, I mean to say that when I load my activity QA links in browser to see if the changes reflected or not then they do shows up but after a while sometime the changed banner reverts back to default old banner.

Just FYI, I did the banner change by Navigating Edit->Styles->Banckground (update URL here) and hit save.

Every experience loads with its changes in the home page banner. And, challenge I am facing is tagging different navigation link to every experience's banner. 

[alexbishop]

One thing you might want to try is creating some QA audiences (e.g. query contains qa=true). Then you can apply those audiences to your activity/experiences, activate the activity and then validate whether you see the same issues. I've occasionally seen some odd behaviour with the QA links, so it would make sense to rule that out first.

[JyotiSharmaV]

@alexbishop I dint understand what you are trying to say. But I already have a separate audience assigned to each experience already.

I also want to check when I am seeing the mobile version of my website then why that banner is not squeezing to mobile version. I did change the mobile DAM link of banner in HTML of each experience. 

[alexbishop · Accepted solution]

Sometimes the QA urls can behave a bit strangely, so you could also QA against a live activity. Of course, you don't want it to be live to everyone, so that's why you apply the condition of "query string contains qa=true" to each of your audiences.

So, for example, if Exp A currently has an audience of Favourite Category = Books, you can add an AND condition of "query string contains qa=true". You would then do the same for each audience. Then you could activate the activity but it's only you that will be entered into it, when you use the ?qa=true query param in the URL. Once you're happy with everything you can then de-activate that test, duplicate it, remove the "query string contains qa=true" condition from each audience and activate it

[JyotiSharmaV]

we dont want to use experience fragment for the banner change because this is pretty forward to us to replace banner dam link. Dont you think it's better and straight forward