Hi,Could someone please explain to me why the actions that are returned
by Target are sometimes duplicated in the JSON response? If by design,
why and how does the AT.js code process these duplicates? Some examples
are high-lighted below but there are many in the example below.
Additionally how/where are they mapped to the actual mark-up
changes/modifications that take place on the client's webpage?{
"sessionId": "a7d72ca5635a4e99a00c22c5a796a133", "tntId":
"a7d72ca5635a4e99a00c22c5a796a133.28_4...
I figured out where the response with json that contained the offers for
Target were being read in so I used the promises already in place and
just modified the array of objects of offers.
I'm looking at the obfuscated code from Adobe Target (At.js) . What I'm
trying to pin-point is where it initially reads the response with the
json structure. I started on this line (Line #4697):$p = ["/m2/", Rp,
"/mbox/json"].join(As),And started to follow it back but didn't have
much luck! Below is a sample
response:https://bankofthewest.tt.omtrdc.net/m2/bankofthewest/mbox/json?mbox=target-global-mbox&mboxSession=0412a0c635b84e0093c135eac04005c1&mboxPC=7c97aeb8c37b4392850e231de01f27ec.28_48&mbo...
Hi,I can't find any information on the web about this so I thought I 'd
try here! What we want to do is validate Target’s action response (based
on Target business rules) against a white-list of valid action
responses. If Adobe Target’s action response call is valid then it
should be used to present experience/content to user. If the Adobe
Target’s action response call is invalid then user should be presented
with the default content. The default content is not driven by Adobe
Target. I understa...
We have an issue with DTM and Adobe Analytics’ report suites switching
for custom links in our dev. env. The report suite is not maintained for
the custom link call after the page load call (which reports correctly).
When a custom link call is made from any of our dev. env. it reports our
production report suite. If you go to the dev. console after the custom
link call and type in “s.account” it will display the dev. report suite.
I have even tried hard-coding the report suites but this doesn’t ...
Hi Daniel,I thought that was you! :0) Good to hear from you. So you were
correct. Once I deleted the 3rd party Adobe cookie I got the PCID in the
mbox cookie again. So my question is, if a user deletes their 1st party
cookies there is no way to read the PCID on the client any longer?
Thanks,MJ
What 3rd party cookie am I looking for exactly? I don't see any
pertaining to Target other than the "mbox" cookie? Please see attached
image. Thanks,MJ
Thanks for the response, I checked and I do see the mboxPC in the
request Headers (see image) but still not in the mbox cookie? So what
does this mean? How do I read the PCID into Adobe Analytics then? That
is why I was reading the "mbox" cookie previously to get the PCID. We
are using DTM.and the Marketing Cloud ID Service if that matters or
impacts anything at all?1. Cookie:mboxPC=1446674230821-145371.28_22;
s_vi_x7Elzx7Edxxzxxen=[CS]v4|2A89A0B4850123DD-4000010C000A516B|55134169[CE];
s_vi_ewae...
I am trying to solve a mystery. We are using DTM and trying to pull in
the Target PCID into Adobe Analytics via a data element. We never had
issues in the past but are now noticing that we aren't getting the PCID
set in the mbox cookie? The weird thing is on our Bank network, Everyone
that tested got the same results:Chrome Browser Normal mode on VPN -
mbox cookie without PCID but contains session idChrome Browser Incognito
mode on VPN - mbox cookie with PCID Chrome Browser Normal mode at Home -...
I'm using DTM and I have some javascript code for automatically tracking
elements on a page. It is some js code that listens for a click and then
will make a custom link call if certain conditions are met. I don't know
where this should go in DTM? I want to be able to control which pages
run this code also. Any ideas?
You can use something like this as a custom script for your data
element. return (function () { "use strict"; var now = new Date(); var
year = "" + now.getFullYear(); var month = "" + (now.getMonth() + 1); if
(month.length == 1) { month = "0" + month; } var day = "" +
now.getDate(); if (day.length == 1) { day = "0" + day; } var hour = "" +
now.getHours(); if (hour.length == 1) { hour = "0" + hour; } return year
+ "-" + month + "-" + day + " " + hour; })();
Hi,Please re-read my question as it is very specific and the document
you pointed me to does not answer my question. I have scoured the web
and can't find an answer yet? Thanks,Michael
I can't figure out how to dynamically update a pre-defined data element?
For example if you are capturing onClick a custom HTML-5 attribute
('data-analytics-tracking-name') value and you want to update a
pre-defined data element ('custom link name') with that new value? I can
do it with a dynamically created data element as per below but not with
a pre-defined data element?var linkName =
this.getAttribute('data-analytics-tracking-name');_satellite.setVar('custom
link name', linkName);return true...
I just found out from a friend that to make this work, whatever data
element name I use in the _satellite.setVar function, ensure that it
does not exist as a pre-defined data element. It will not allow you to
overwrite the definition with the _satellite.setVar function. So I can
just add a custom condition to the event rule to dynamically get the
value from this attribute that was listening for the attribute click.
I have some listening code that is being served as a custom script for
the data element that could make multiple updates per page view which is
capturing the value of a HTML5 Custom Attribute. The issue is I can't
get listening code to return the value for data element to be set. Not
sure what I'm doing wrong and have tried numerous approaches. When ever
I check the value of the data element I get the default value that was
set in the UI. Any idea how I make the data element update every time a
...
I work for a bank and security is a major concern. We are currently
using a cname on Adobe's collection servers (e.g. stats.bank.com) in
order to have Adobe serve first party cookies on the bank.com domain.
Our security council now says we shouldn't provide Adobe with a new SSL
cert for stats.bank.com because it is too risky and if stats.bank.com is
compromised and someone attacks our customers then we our liable due to
it being our brand and all the cookie data is exposed as well as leaving
cus...
