Hi All,
We would like to start passing visitor cookie ID and session ID values into our data feed.
Would someone please point me to how this data is named and how I can find it?
Thanks!
Solved! Go to Solution.
Views
Replies
Total Likes
Right so I would advise you to read these articles first:
Do all customers get assigned one of the visitor IDs above or could they land in multiple columns?
Multiple type of visitor identification can and will be assigned to a unique visitor but only one will prevail per the following processing order:
There are several ways a visitor can be identified in Analytics (listed in the following table in order of preference):
Order Used | Query Parameter (collection method) | post_visid_type column value | Present When |
---|---|---|---|
vid (s.visitorID) | 0 | s.visitorID is set. | |
aid (s_vi cookie) | 3 | Visitor had an existing s_vi cookie before you deployed the Visitor ID service, or you have a Visitor ID grace period configured. | |
mid (AMCV_ cookie set by Experience Cloud ID service) | 5 | Visitor's browser accepts cookies (first-party), and the Experience Cloud ID service is deployed. | |
fid (fallback cookie on H.25.3 or newer, or AppMeasurement for JavaScript) | 4 | Visitor's browser accepts cookies (first-party). | |
HTTP Mobile Subscriber header | 2 | Device is recognized as a mobile device. | |
IP Address, User Agent, Gateway IP Address | 1 | Visitor's browser does not accept cookies. |
In many scenarios you might see 2 or 3 different IDs on a call, but Analytics will use the first ID present from that list as the official visitor ID, and split that value across the post_visid_high and post_visid_low columns. For example, if you are setting a custom visitor ID (included in the "vid" query parameter), that ID will be used before other IDs that might be present on that same hit.
The following column should cover this:
visid_type
post_visid_type
visid_high
visid_low
post_visid_high
post_visid_low
cust_visid
post_cust_visid
mcvisid
post_mcvisid
visid_type
post_visid_type
visid_high
visid_low
post_visid_high
post_visid_low
cust_visid
post_cust_visid
mcvisid
post_mcvisid
Is a unique session ID created somewhere that we can reference and join on?
There is no such thing as a session ID in the data feed. The only thing close to it is a visit which following the industry standard of last hit plus 30 minutes of inactivity.
The following allows you to calculate a visit:
Visits |
*In rare circumstances, internet irregularities, system irregularities, or the use of custom visitor IDs can result in duplicate visit_num values for the same visitor ID that are not the same visit. To avoid resulting issues, also include visit_start_time_gmt when counting visits. |
Is you are using one of the mobile SDK then there is a notion of session but it is calculated client side (visits are still calculated as normal) and a launch event will be automatically sent.
Views
Replies
Total Likes
Dear Paul,
The link Data Column Reference has all the details. Make use of it.
It has everything that are available in Data Feed i.e. Columns, Descriptions, and Data Types.
Thank You
Arun
Ok if we consider that cookie ID for you is the Visitor ID and session ID is the visit then you will need these columns from the data feed:
visid_type
post_visid_type
visid_high
visid_low
post_visid_high
post_visid_low
cust_visid
post_cust_visid
mcvisid
post_mcvisid
And for the visit
visit_num
visit_page_num
Thanks for your help!
Is a unique session ID created somewhere that we can reference and join on?
Do all customers get assigned one of the visitor IDs above or could they land in multiple columns?
Really hoping to begin passing a single cookie ID and session ID from our Adobe data to our database, but not sure if it is going to be that simple.
Views
Replies
Total Likes
Right so I would advise you to read these articles first:
Do all customers get assigned one of the visitor IDs above or could they land in multiple columns?
Multiple type of visitor identification can and will be assigned to a unique visitor but only one will prevail per the following processing order:
There are several ways a visitor can be identified in Analytics (listed in the following table in order of preference):
Order Used | Query Parameter (collection method) | post_visid_type column value | Present When |
---|---|---|---|
vid (s.visitorID) | 0 | s.visitorID is set. | |
aid (s_vi cookie) | 3 | Visitor had an existing s_vi cookie before you deployed the Visitor ID service, or you have a Visitor ID grace period configured. | |
mid (AMCV_ cookie set by Experience Cloud ID service) | 5 | Visitor's browser accepts cookies (first-party), and the Experience Cloud ID service is deployed. | |
fid (fallback cookie on H.25.3 or newer, or AppMeasurement for JavaScript) | 4 | Visitor's browser accepts cookies (first-party). | |
HTTP Mobile Subscriber header | 2 | Device is recognized as a mobile device. | |
IP Address, User Agent, Gateway IP Address | 1 | Visitor's browser does not accept cookies. |
In many scenarios you might see 2 or 3 different IDs on a call, but Analytics will use the first ID present from that list as the official visitor ID, and split that value across the post_visid_high and post_visid_low columns. For example, if you are setting a custom visitor ID (included in the "vid" query parameter), that ID will be used before other IDs that might be present on that same hit.
The following column should cover this:
visid_type
post_visid_type
visid_high
visid_low
post_visid_high
post_visid_low
cust_visid
post_cust_visid
mcvisid
post_mcvisid
visid_type
post_visid_type
visid_high
visid_low
post_visid_high
post_visid_low
cust_visid
post_cust_visid
mcvisid
post_mcvisid
Is a unique session ID created somewhere that we can reference and join on?
There is no such thing as a session ID in the data feed. The only thing close to it is a visit which following the industry standard of last hit plus 30 minutes of inactivity.
The following allows you to calculate a visit:
Visits |
*In rare circumstances, internet irregularities, system irregularities, or the use of custom visitor IDs can result in duplicate visit_num values for the same visitor ID that are not the same visit. To avoid resulting issues, also include visit_start_time_gmt when counting visits. |
Is you are using one of the mobile SDK then there is a notion of session but it is calculated client side (visits are still calculated as normal) and a launch event will be automatically sent.
Views
Replies
Total Likes
Dear Paul,
For session, do the below:
The combined string is Session or Session ID.
For Unique Visitor, do the below:
The combined string is Visitor or Visitor ID.
Thank You
Arun
Check this article as well Using Adobe Analytics Data Feeds and SQL for Basic Reporting – The Data Feed Toolbox
Views
Replies
Total Likes
Thank you both!!!
We are now well on our way to getting the data we needed!
Views
Replies
Total Likes
Views
Like
Replies
Views
Like
Replies