Hi @LordOfTheRings , Have you setup A4T through server side logging or
client side logging in Analytics? Refer to this document for more
details of either setup:
Hi @jpetermarias1 , Can you clarify a few things in the question: You
mentioned the activity type was XT. In that case how is the "All
Visitors" audience setup in the activity? How is each audience split
into Default Content Vs Modified Content since we are talking about XT
activity? I am making my assumptions to the above - All Visitors might
be an additional audience added to the activity apart from the other
audiences you have mentioned and further split each audience with a
traffic split (ma...
With "New Visitors" condition you might miss those who are not new to
the site but haven't seen the experience before either because they
didn't navigate to the page or the activity wasn't live by then. One
other option you could try is to pass a custom code from within the
Target experience to pass an mbox parameter - which could be used as a
flag to indicate that the user has seen the experience. In your audience
condition use this mbox parameter as an exclusion condition.
Are you signing in my any chance on the site to capture mbox3rdParty id?
If yes, you will continue to see the same experience. If not once you
clear cookies then you will be treated as a new visitor and what
@Gaurav_Singh mentioned holds true.
Hi @jean-philippe_8 , The logic sounds fine. One thing you could check
is the time range you have provided. If you wanted to check for within
the last 30 days you might want to change time frame condition to
something like below: The time frame you selected might be checking for
beyond one month. Depending on your implementation state it might not
qualify any users to the segment. Let us know if changing the time rule
works for you.
@guruanand, 1. You don't have to parameterize URLs for rendering
different personalized variations. Setup different experiences in Target
and it will take care of splitting the audiences and rendering different
experiences to the different audiences. You are using the same URL as an
end user. 2. Check this section of the document on best practices around
using personalized experiences with SEO in consideration:
Thank you @DisaRas for your response. Had followed the steps you
mentioned. Had to raise a clientcare ticket and there seems to be some
caching issue on the site I was trying to render the personalization.
Now it is working for me as well.
Hi @practitioner-pin ,Front and back promotions always take the first
and last slots in your display design. In your example criteria AAA
slots 7 & 8 would be filled with the back promotions. Slot 6 MIGHT be
filled with backup recommendations ONLY IF criteria AAA returns just 3
valid results. If the criteria AAA is able to return 4 or more than 4
results then no products would be served by backup recommendations. Back
up recommendations only come into picture when the intended criteria is
Hi @practitioner-pin , Favourite category is defined by Adobe
Recommendations through a backend algorithm. You will have to pass the
entity.categoryId value when user navigates to a product page that
belongs to a particular category (NOT when user adds a product to my
favourites - that could be defined as a custom key to be used in other
Recommendations algorithm) using the sample code format you shared. The
rest of calculations to define the favourite category is handled by
Refer to this document for the information you are looking for specific
to the favourite category (entity.categoryId has to be passed in mbox