Hello everyone,I recently implemented AA tracking for our site. We
already have GA tracking in place so over the past week, I've been
monitoring the discrepancies in data on the two platforms to see if AA
is tracking data accurately. For the most part AA tracking is in place.
However, Firefox browser on Desktop is tracking much lesser visits
compared to what I am seeing in GA. The discrepancy is almost 500% which
obviously I can't ignore. Further deep dive suggests that particularly
@josejr19, I think I know why the reports are messed up. It;s because of
my custom report descriptions. I think I have them jumbled up and hence
it is sending the wrong value. Let me fix it and see if the reports
rectify. If not I'll share the beacon. Thanks for your responses.
@josejr19, No processing rules set yet. I've just set up custom report
descriptions so far. In the report, for page type (prop) it's giving the
value of click pathing. All the values are cross-referenced. Also for
screen size (prop), it's giving me values for language. Hope this makes
Hello everyone,I recently completed the first phase of implementation
for our site. I validated all the tags and events in QA and we deployed
in production. All the tags are firing as expected on the production
site, however, the reports are not showing the right values. For example
for page type the eVar is showing the right values in the reporting but
incorrect values for the corresponding prop. When the page type is
validated on the browser, omnibug is showing the right value for both
Hello, I manage a content website and for me the customer loyalty would
be defined in a different way as there is not purchase event. In AA is
it possible to define your own customer loyalty parameters?For example-
Loyal customer =a customer who visits the site 4+ times in a monthRepeat
customer - A customer who visits the sites 1, 2 or 3 times in a
month.New customer- 1st visitSo on and so forth.Looking forward to the
responses. Thank you.
Yuhuisg, thanks for the global report suite option however, as
mentioned, our main site has limited evars available and not sure if
adding the othersite report suite to the existing one will help. I am
not sure if the global report suites allows more evars. In that case the
solution might work but if not, we'll have to go the independent report
suite but the challenge in that case would be the pathing between site
as you mentioned.
Thank you for your response. However, as I mentioned, I am leaning
towards building a new report suite due to the limited evar
availability. I may have found a possible solution to track visitors
across sites using the CNAME implementation and following the steps
mentioned in the article.
Do let me know your thoughts on this solution. Thank you.
I have a question related to domain and sub domain tracking in Adobe
Analytics. I have a main domain names www.xyz.com and a sub-domain
www.abc.xyz.com and I am trying to look at options for Adobe analytics
(AA) implementation on the sub domain site. The main site already has AA
implementation in place but the sub domain does no. There are two
options in this situation, either to build new report suite for the sub
domain or to build it within the existing domain. The end goal is that I