The Google Analytics SDK or tracking code sends campaign and traffic source data through a number of different fields. Which of the following is one of the fields used to send campaign or traffic source data?
- Location
- Campaign Medium
- Device Category
- Interest Category
The google analytics sdk or tracking code sends campaign and traffic source
Explanation:
Users arrive at your website or application through a variety of sources, including advertising campaigns, search engines, and social networks. This article describes how Analytics collects, processes, and reports the campaign and traffic-source data.
Understanding campaigns & traffic sources
In Analytics, the ad campaigns, search engines, social networks, and other sources that send users to your property are collectively known as campaigns and traffic sources. The process by which campaign and traffic-source data is sent to Analytics and populated in reports has the following steps:
- Collection – values are sent to Google Analytics in the campaign and traffic-source fields using the SDKs or tracking code.
- Processing – collected values are used to populate the final report dimensions according to a processing logic.
- Reporting – campaign and traffic-source dimensions and metrics become available in the web interface and Reporting API.
Collection, processing, and reporting behavior can be customized.
Collection
The Analytics SDKs and tracking code use these fields when sending campaign and traffic-source data:
| Field Name | Protocol Parameter | Field Description | Sample Value |
|---|---|---|---|
| Campaign Source | &cs |
Sets the source dimension in reports. | email_promo |
| Campaign Medium | &cm |
Sets the medium dimension in reports. | email |
| Campaign Name | &cn |
Sets the campaign name dimension in reports. | january_boots_promo |
| Campaign Content | &cc |
Sets the content dimension in reports. | email_variation1 |
| Campaign Term | &ck |
Sets the term dimension in reports. | winter%20boots |
| Document Location | &dl |
Sets dimensions whencustom campaign (utm) parameters are embedded. | http://store.example.com/boots?utm_source=promo_email &utm_medium=email&utm_campaign=january_promo &utm_content=copy_variation1 |
| Document Referrer | &dr |
Describes the referring source and may set dimensions when no other campaign or traffic source fields have been set. | http://blog.blogger.com/boots |
Note that each session can be attributed to only one campaign or traffic source. Thus, if new campaign or traffic source values are sent to Analytics at collection time in the middle of an existing session, it causes the current session to end and a new session to start.
Processing
During processing, traffic-source and campaign field values are finalized into dimension values and attributed to sessions. The Campaign & Traffic Sources Processing Flowchart illustrates the processing logic.
The following methods apply to processing that uses utm_ parameter values (e.g., display, social, referral, email, paid search, etc.).
- Source precedence—A direct-traffic visit that follows a paid-referred visit will never override an existing paid campaign. Whatever is the latest paid campaign visit is listed as the referral for the visit
- Campaign precedence—Each visit to your site from a different paid source—such as from a paid search-engine link, an Adwords link, or a banner ad—overrides the campaign cookie information set by a previous source.
- One Campaign Per Session—Each visit to your site from a different campaign—organic or paid—triggers a new session, regardless of the actual time elapsed in the current session. Specifically, a change in value for any of the following campaign URL parameters triggers a new session:
utm_source,utm_medium,utm_term,utm_content,utm_id,utm_campaign,gclid. For more information on sessions, see How a session is defined in Analytics.
https://www.youtube.com/watch?v=pchsqiaUeV0
