mohammedm30428844 As documented at Upgrading from at.js 1.x to at.js
2.x , In at.js 2. x , you no longer see “ target-global-mbox ” visibly
in the network calls. Instead, we have replaced the “ target-global-mbox
” syntax to “ execute > pageLoad ” in the JSON payload sent to the
Target servers,Hence you can filter by delivery?client in the network
calls and you should be able to see the target call.
As documented at Plan and implement Recommendations you can have data
from feeds and page for the same domain. You will need to pass the
required entity parameters on the article pages and through the mbox
data collection , these entities will be available in the catalog.You
can also then use collections to manage them easily.Hope this helps.
moritzh76280848 It would depend on what attributes you are already
passing on your feed. If you are already passing attributes like
category, price etc you can use them as keys to recommend other items.
If you are trying to recommend articles, I would assume that they are
not part of the product feed. In that case you could set up a feed with
the articles or use mbox data collection to collect the entities. Ref:
Plan and implement Recommendations Entity attributes
christophert87757717 Yes passing the custom parameter would require
that you call the targetpageparams() function through DTM/Launch or on
the page. If you don't have the option to do that I am afraid that the
above suggested approach won't be applicable to you.
vijayselvaraj_90 Instead of using a cookie the easier approach would be
to store the category value in the user's visitor profile or pass it as
an mbox parameter and then use that build the audience to show your
content. Information on the same can be found at Methods
As mentioned above, there is an enhancement request logged for the
same.Ref: https://forums.adobe.com/ideas/11688 . Please feel free to
upvote the idea so that if more users request the same it can be
prioritized .In the meantime, you could try and grab these values and
pass them as custom parameters and then use them for targeting . For
example, just pass a custom parameter named "browserWidth" and set it to
document.body.offsetWidth . You could also use window.screen object to
get the resolu...
IanS1982 To achieve this, yes you would need some developer assistance
as there is no out of the box way to do this. You could also check
Experience Templates which has some examples of templates to show
banners which might give you some sample code to work with as well.
This usually means that the Launch library is not referenced correctly
and hence it cannot find the launch libraries . You could maybe validate
your launch implementation by following the steps mentioned at Publish
your Launch property
justinl40680371 Is there a publicly accesible site where you have this
implementation so that we can take a quick look to see what might be
going on? Without that it is hard to help pin point where in the
implementation the issue lies. Also I would recommend using the Launch
Debug switch and examining the console statements to check if all your
Launch rules are firing as expected .
justinl40680371Have you verified that target calls are firing on the
page as expected? If you go to the network tab and filter by .tt, you
should see the target call. Once you have verified that, check if the
activity is delivering on the page by running the mbox trace.Information
on how to run the mbox trace can be found at Troubleshoot content
FYI, if you URL-encode the entire batch contents after "batch=" , then
you should not be seeing such issues.The issue is that the URL
parameters (batch=...&test) are parsed by the servlet container and the
batch parameter value is "truncated" (from the user's perspective)
before the Target code even sees the parameters, so this is not
something Target can even detect as an error.
cordellb6767183 Please do check out the resources available at the
Launch documentation page specifically Upgrade preparation guide .These
are some blogs that have some useful tips and tricks.The Migration
Process from Adobe DTM to Adobe Launch | Adobe Blog
only the ECID, Adobe Analytics, and Google Universal Analytics tools
will be converted over into the matching Launch extensions with matching
MktgCloudUser Could you try using user.activeActivities ? I tested that
and it works for me. Fyi , response tokens are not available until after
the content decision is made, whereas a profile script evaluates before
the content decision is made.
Hi @m_v, As documented at Plan and implement Recommendations , when
combing mbox data with a CSV feed, Priority is given to whichever set of
data runs most recently. If you pass the feed first and then update the
page parameters, changes that are made in the page parameters will be
shown, replacing item information passed in the feed or vice versa.
Hence instead of passing all the parameters though the mbox and feed,
separate them such that in the feed you pass the entities that does not
gaureshk30144236 The recommendation engine prepares the number of recs
candidates based on the design. So for a design with 3 slots, the recs
algorithm will try to generate 3 * number of design slots candidates. So
when the design changes it will need to recalculate the no of candidates
again. Hence the reason that you need to wait for the results again when
you make changes to the design.