Hi, your question seems to be around URL and if that's the case you are
definitely ok with 300 bytes, you will have to exceed 2000 bytes before
you will need to start getting concerned.Now if you are referring to the
variable it such as eVar0 or similar then yes 300 bytes exceeds the
limit of an eVar and in the case of props its 100 bytes. Your data will
get truncated.You will need to come up with a way to shorten it.
Hi,Sorry I'm not able to get your scenario, is there anyway I can see
this on the site itself, you can PM me with details.Your original
message said the PLR wasn't firing but your last message is saying you
don't see "said content" and "test for the presence" - Not sure I
completely understand the scenario and issue.
Does the page load rule still match and what about s.t() and s.tl(), I
don't see any reason why it wouldn't work?So to get this right, a page
load, age gate shown, user fills and accept, user redirects to another
page -> page load rule does not fire?
When you say age gate, is it a modal window that request the user
selects the year they were born? The page that doesn't fire is it a new
page that loads after the user submits the form?Is anything else firing
on that page that fails on load, have you tried calling s.tl() or s.t()
in the console and see if that works?
Event is fine but you will need another variable to be able to define
which ad was clicked on by ad name or campaign name or something of that
nature. If you have a small number of ad then yes you could just use a
unique event for each but I wouldn't recommend it.
laetizia_2018 - usually your ESP will do this for you provided you are
using one that has a connector into Adobe Analytics. If not, its still
possible but may get very technical. Reach out to me directly if you
still want the technical spill as I'll need a bit more details to
provide a solution.
sandras28979200 - you should not be affected, DNT has been around for
ages and its usually up to client to enable it or account for the flag
when implementing a web analytics platform such as Adobe Analytics but I
haven't seen or heard of any tool that automatically honors it.
FrancisDCon - It depends on what you mean by links, if they are
download, exit links and if Adobe has been setup correctly it should be
tracking those automatically. However, if they are just regular links,
you will need some development help. You could also try Activity Map and
see if that helps.
Hi FrancisDCon, yes you are going to need some development help to
track events on form and field interaction. Once that data is collected
you may now report on it. I usually take it a step further and track
error messages also.
Hi, your question is a bit confusing as you first asked how to track how
many visitors successfully login but at the bottom you said how to
distinguish visits by visitor type - either doesn't fully ask a
question.Are you trying to figure out how to track on a single page
scenario when the browser doesn't reload?
H, it sounds like you will have to tag and track all the actions that
will lead to user to exit your site and report on those. So if you know
"Configure" sends the user to another site, you fire a call of your
choice to Adobe and the redirect the user. That call will then be the
user's last call.
I'm not aware of a best practice guide but we always tag them as normal
page views and that provides us with everything that need when it comes
to reporting. Track the main page as a referrer so you can tell the
source of the click and if you have multiple CTA's on the same page you
can tag those too and use pathing to decipher, we don't usually get that
deep as the referrer is usually enough.
Hi, it sounds like your DTM isn't configured probably and to test it
out, try calling "s.t()" or "s.tl()" in the console after page load and
see if you get a call in the network tab. If you do then you definitely
have a DTM problem and if you don't you probably still have a DTM
Sure, you will need a click-stream report, also known as data feeds.
Create a data feed report with all the available columns "a lot" and you
should be all set. The data can be sent to FTP or Amazon S3 -
Ankit,Pass the referrer details such as google cpc details to the
iframe, via messaging or query parameter and from within the iframe
page, grab and send that to Adobe and that should solve your problem.
Ah I see, yes that is possible, my answer still stands. The chrome
extension will inject the Adobe script and call s.*, however, keep in
mind that if your chrome extension is going to run on sites that already
have Adobe install - public chrome extension, you may want to ensure you
implement a different S object so you don't overlap on an existing
implementation. As a matter of fact, you should do that regardless to be
on the safer side but everything else should work as normal.