Thanks, I'm going to try this; I'm also looking at creating a new field
on the CSV too with just the raw url, then reference that instead of one
being sent via the mbox.
Thanks Eric, we are passing this information via the mbox (done via the
DTM), as the moment we can't update the code to fix this issue and since
it's on page load using the csv approach also doesn't work as that get
overridden via the mbox call. I know it's not ideal to use velocity to
fix this issue but the issue is currently stopping us launching to need
a solution using that method if possible?
We are passing the full url of a page via the mbox but realised that it
is also including the # fragment or parameters, we want to then use the
url in our recommendations design, an example entity url
is:http://www.example.com/page1.html?adobe=QA In our design we set:$entity1.nameIt outputs like this:My Itembut we
really want it to out like:My ItemIs there a way
through Velocity Scripting to remove any parameters and # fragments so
that only the raw url is left?
I didn't have a entityID on my page, once I added that everything
started working. The documentation I read didn’t clearly highlight this,
it was my assumption that providing a Feed was enough, on this page
under Attributes, it says:Attributes can be provided in the mbox or
through a feed. I thought that I didn’t need the mbox part as I’m
providing it via feed, I realise now as a minimum I need the mboxCreate
and set a unique entityID for each page, then I can use my Feed to add
additional Attri...
I created a CSV feed and have a entity.id, entity.name, entity.message
for each item along with adding my entity.pageUrl (setting this to the
absolute URL of my pages), I created a Design and set my Criteria. I
then created a Recommendation activity and set it up with a Design,
Criteria and Collection, all is displaying as expected in Edit mode, but
when I launch it, no recommendations show and if I use mboxTrace, I get
the following message at the bottom of the output: "response" : { "node"
: "...
