Right so I would advise you to read these articles first:
Calculating Metrics
Identifying Visitors
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:
Analytics Visitor IDs
There are several ways a visitor can be identified in Analytics (listed in the following table in order of preference):
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 | - Exclude all rows where exclude_hit > 0.
- Exclude all rows with hit_source = 5,7,8,9. 5, 8, and 9 are summary rows uploaded using data sources. 7 represents transaction ID data source uploads that should not be included in visit and visitor counts. See datafeeds-hit-source.html#concept_FE4C114F6A524F7593D5CAC944C36C42.
- Combine post_visid_high, post_visid_low, visit_num, and visit_start_time_gmt*. Count unique number of combinations.
*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.