Both the approaches to view data is correct. It depends on what data you
want to see.Is you want to see the data from visitors who saw a specific
campaign, use Visitor container. If a visitor sees a campaign in one of
his visits and not in other, he will still qualify for the segment and
therefore data for both the visits will be reported. That is why you see
more data when using Visitor container.While using VIsits container, it
will report on only those visits where the campaign was seen, ther...
Currently Data Feeds can only be sent to FTP/SFTP, Azure and S3. There
is no option to share data in Snowflake. You might work with Adobe
Engineering Services team to see if they can build or already have a
Depending on look back period you have selected for the rule, the value
can still be Unspecified if it is an old one (that means the value
arrived in your reporting beyond the look back period). If that is not
the case and you are still seeing the issue, please contact Customer
Care to help troubleshoot this.
If you are using traffic metrics like Visits, you will get Undefined
line item because evar value is not set on every visit. If you are using
Custom events as metrics and seeing Undefined, that means, evar value
was not set (or expired) when the event was fired.
Not sure if I understand the query. Do you want to get data from API
1.4? If yes, I would advise moving to API 2.0 as 1.4 will be deprecated
in near future. You may check this doc to for specifications:
Tracking is done based on web beacons(calling Adobe Analytics SDK APIs),
so it does not matter if the user is browsing through the app or web
view within the app. If you are firing web beacons from within web views
you should be able to track the visitors. There is one important aspect
you need to consider is to tie the visitors from the app to the web
view. You can achieve this by visitor
The first call should be a s.tl() call (m_s) and that should not inflate
Page Views. Please check if there is any processing rule which is
setting page names. if you set Page Name in a s.tl() call that will be
treated as s.t(), a Page View call. If that is not the case, you would
need to review your implementation.
You are correct in your assumptions.1. It is the first value set for
pages variable which the first value sent in the trackState call. It
does not necessarily need to be sent right after the lifecycle calls.
trackAction calls can be made prior to this.2. Yes, the Entry Page value
will be assigned with the value from the first trackState Call.
I assume you are looking for a method to get the data in the reports
using APIs. You may use Analytics Reporting API 2.0 to get data via API
requests. Please refer to the following
let me know if that helps.
You may consider using Mobile App Acquisition for tracking links which
can be correlated to in-app
API 2.0 works differently. While 1.4 allowed break down of one dimension
with another, 2.0 allows break down of a line item of a dimension with
another dimension. Check the following link for more info on 2.0
It is easy to duplicate Workspace reports by using Workspace
You would need to build a calculated metrics with the formula. Below is
the documentation containing the steps to create calculated
The API request you pasted, does not show correctly at my end. Perhaps,
I have the font missing. Also, the request IDs can be checked by the
Customer Care team as well as the debug logs. I would advise reaching to
Customer Care team for help.