Hi, I'm trying to figure out the interrelationship between Criteria (or
Criteria Sequence), (Front/Back)Promotion, and Backup settings. After
I've read through the online documentation couple of times, I outline
two examples below based on my understanding. Does anyone help to
validate this? Thank you,
Hi @kchaitanya, Thank you so much for clarifying the "Favorite
Category," which is handled by Target Recommendations at the backend.
And point out the approach of a custom key if needed to specify the
behavior.It helps me to figure out the logic behind the official
document. Thank you again.
Hi @kchaitanya, Thank you for your information. May I explore more about
this approach? The document mentions that "When this option is selected,
the entity.categoryId value must be passed as a parameter to the display
mbox." Do you know when / where to pass it? Does it mean setting a
Launch rule to track a visitor's click behavior on the "Add this product
to my favorite" icon with the targetPageParams() method? The document
doesn't elaborate on the "Favorite Category." Back to the page of "Pass...
Hi @mosesmaxen, thank you for the clarification. These two statements
help me a lot to know the logic behind them.user.XXX represents a Target
profile script, which is a way to track behavioral data using code
executed on Target's server-side on each mbox / location request.
profile.XXX represents a profile parameter that is passed in through the
mbox / location request. One more question is about the setting process.
I found no value from the dropdown field (the red rectangle below). Is
Hi, I'm curious about how to prepare the behavior data for OOTB - "Most
Viewed Products within a Visitor's Favorite Category." According to the
documentation - Pass behavioral information and context, I can't find
any practice or sample code mentioning to pass a Visitor's Favorite
Category. If the related data isn't available, I guess this OOTB
Criteria couldn't work correctly. In addition, I found that many OOTB
templates seem to have required behavior data in place before adopting
Hi @mosesmaxen, thanks for your prompt response and pointing out the
document linkage. The document only shows a custom key that can be added
when creating a new Criteria. It's not a setting step from the
"Settings" interface. Supposedly, I need to configure a new custom
attribute first. Then, I could use the targetPageParams method to pass
data into it. Or leverage a profile script that you mentioned earlier.
Besides this custom attributes setting, I'm also confused about both
user's attribute ...
Each item type (ex. article or product) have their own feed and
entity.id position. For example, feed A for "Article" item type with
pre-fix like "article-12345" in entity.id field.And another feed B for
"Product" item type with pre-fix like "prod-12345" in the entity.id
field. That means there is no duplicated identity data in entity field.
Then when you can create a Criteria, you can use "Filter" setting to
limit learning scope for "article" or "product". That's what I know the
product logic a...