Hi @DebbyNPL , it sounds like you are getting calls from both the "app
load" and the "view change" when your intention is to only make calls on
the "view change". Does your data element change twice on the first load
of the app? Or is there another rule which is firing on on the page load
(via "Library loaded - Page Bottom", "DOM Loaded", or "Window Loaded")?
Must the media team count the green instances only? If not, would using
the Visits metric be enough for them?Also, FYI there's an
Analytics-specific forum at
@DebbyNPL , Does the "the hits where AA had persisted the value in the
absence of it being set" refers to the post-eVars of the duration
setting of the eVar in Adobe Analytics besides the implementation?Yes.
I'm pretty sure of that the "Non-repeating Instances" is not refers to
the values of post-eVars.Good point, I confused myself. So what you did
was correct.What is the expiry setting for your eVar(s)?
Thanks Andrey, can not agree any more! Yes, the DW documents showed no
references to the participation, and I also doubt that the participation
refers to the attibution because the participation always need to assign
"paricipate to what", and I never assign that. For double comfirm, I
think you mean the participation here means occurances (instances+post
Hi seanc33988855 I also faced that issue and I'm working on it. So I've
summarized some possible scenarios which would be happened for you to
check. Should to notice that I'm not a senior, so those would only be
for your reference. 1. While a new visitor visit your website, two
servercall cookie will be sent to. Perhaps the first cookie send the
information of the new visitor information and the visits, and the
second server call is the windows load server call with PV. If a new
user close to fa...
Do any of the answers below answer your initial question? If so, can you
select one of them as the correct answer? If none of the answers already
provided answer your question, can you provide additional information to
better help the community solve your question?
A note with this method:As a pre-req, you will need to make sure that
the s object is defined globally in your Analytics extension.Then, this
code must be placed in an action before sending the beacon or in a rule
must fire before the one used to track your event, event10. If the
intention is to use this after all beacons, then it should go in a
separate rule that fires before any other rules that send a beacon. If
placed in custom code before using the AA extension, you could run into
a race co...
Hi @DebbyNPL - your logic is sound, but it is my understanding that by
using the date range feature in the Segment Builder, you override the
panel's default date range. Ben Gains posted a video introducing rolling
dates in segments and how it superseded the date on the report's panel
itself. It looks like the reverse may be true as well. Here's the video
just for fun:
Those dimensions, Previous URL (prop16) and Previous Page Name (prop17),
are custom dimensions that have been setup by your AA technical
implementation specialist. They are not standard dimensions that AA
provides out-of-the-box.Consult with your implementation specialist to
troubleshoot this problem.
Any traffic that goes from app to web will not have any Referrer,
because there was no previous web page before the current one opened, so
the browser won't set its document.referrer string.Weibo and WeChat are
normally used as mobile apps rather than websites. So you'll encounter
this case.Having said that, you mentioned that your Referrer is getting
set as "linkedin.com"? If so, then could it be that you are using
LinkedIn's shortened URLs with your Weibo/WeChat posts? If yes, then the