We're having an issue with regards to the disableThirdPartyCookies
method. For the VisitorAPI service, when the method
disableThirdPartyCookies is set to true the documentation* states that
"the ID service does not return the third-party demdex-cookie". And "if
a visitor already has this cookie in thier browser, the ID service won't
use it to create a new ECID or return an exisiting ID". Still, the
demdex-server is responding with a demdex-cookie. How come?
Viewing the Adobe Logs (through Customer Care) the problem was at the
receving side (S3 bucket). The file/feed got generated correctly and
pushed to the queue, however there was an authorization mechanism in
place that was not supported.Would be great though if such error
messages are reported back in Data Feed UI as well.
Hi,We're running into some unknown issues with Data Feeds to S3 bucket.
We simply used a one-day all columns export but the transfer keeps
failing. (a day in the past but within 30 days)In Analytics UI we see
status 'complete'. However, in the email we receive 'failed to complete
successfully (Status: Failed to complete successfully). And no
description about why it failed.. anyone else having this issue? and a
I am not sure if I completely follow. So from the example visit page the
marketing email click that led to the first server call will also be
tied to server call 9 and 10 where CID1 is the effictive visitor ID (and
when this is CID1's first hit ever)? And if server call 11 was generated
using Natural Search for instance, server call 12 will not have this
information since it is not CID1's first hit ever and therefore
continues from known CID1 profile and will be reported as Direct,
Thanks for the update. In the mean time I also opened a discussion about
this on #measure slack channel. And I am not sure if the Example Visit
page represents the real story of what happens when using the
s.visitorId variable (authenticated hits). From the discussion on slack
I understood that whenever mid-visit the s.visitorID method is
introduced it creates a new visitor profile. And so, nothing will be
copied from the previous hits (ie. ECID hits) in that same (browser)
'session'. From this ...
How does Adobe Analytics cope with unauthenticated and authenticated
server calls within a session and over different sessions? For this
particular case I'd like to know what happens when setting s.visitorID
variable (enabling vid parameter) and what Adobe Analytics counts as a
unique visitor when s.visitorID cannot be set and Adobe falls back to
mid as the identifier. From this page it is pretty clear the within a
session unauthenticated hits and subsequent authenticated hits are
counted as two...
It seems that more time is invested in Virtual Report Suites (VRS).It
would be nice to be able to set up a VRS with a customized calendar to
mimic fiscal patterns or mon-sun weeks. Basically the option you have
right now within the report suite settings but then through a VRS and
(if possible) retroactively.
hi Gigazelle, Thanks for your reply.With respect to the second question,
can I make use of the following documentation?Supported XML Tags and
Query Variables | Adobe Developer Connection If I am correct using POST
or GET you need to provide , or . If I use
the (the client's) customer ID for the -field and use
customer ID in the right eVar field I should be able to connect the
"purchase", however during the client-side process Adobe reports on
visitorId or MCID and not on the client's customer I...
Can anyone share some best practices with respect to 1) collecting your
applications.1) how can I best collect my own customer/ user ID? Should
this be in an evar and what should be the settings of this evar (also
with GDPR in mind)?2) if for this customer the real conversion takes
place in a back-end application, what can be used to link this
conversion to the same visitor for Adobe Analytics? Thanks!
Hi Gigazelle, Yes, I was aware this is a permission issue. This is why I
asked a feature request.Suppose, there are 5 users (1, 2, 3, 4 and 5).
And user 1 has access to all report suites (A,B,C,D) and User 2, 3, 4,
and 5 only have access to respectively report suite A,B,C,D. This is
necessary because I don't want that user 2 can access report suite C
which belongs to user 3. If user 1 makes a project in report suite A and
shares this with user 5, user 5 is not able to copy or open this project