QA Analytics considers URLs with different URL parameters as different pages.
However, for some special URL parameters below, special processing is performed.
What is determined to be a special URL parameter in QA Analytics:
URL parameter | Significance | Processing |
---|---|---|
?s | WordPress standard site search | Store keywords and consider them as access to the ?s page. |
?utm_xxx | Google Analytics URL parameter | The same determination as Google Analytics is used, and the access is considered to be to a page without the utm parameter. Only four parameters are considered: campaign (utm_campaign), source (utm_source), media (utm_medium), and term (utm_term). Other utm-related parameters are ignored. |
?gclid | Access from Google Ads | Considered as access from Google ads (cpc), excluding gclid parameter |
?_ga | URL parameters given by Google Analytics cross-domain | Deemed to be access to the page without _ga parameter |
?fbclid | From Facebook | Set “utm_source=facebook” and “utm_medium=social” and consider the access without the fbclid parameter |
?twclid | From Twitter | Set “utm_source=twitter” and “utm_medium=social” and consider the access without the fbclid parameter |
?gad (Ver3.6 and later) | from Google ads | Treated as access excluding the gad parameter, with utm_source=google and utm_medium=cpc |
?yclid (Ver3.6 and later) | from Yahoo ads | Treated as access excluding the yclid parameter, with utm_source=yahoo and utm_medium=cpc |
?ldtag_cl (Ver3.6 and later) | from LINE ads | Treated as access excluding the ldtag_cl parameter, with utm_source=line and utm_medium=cpc |
?msclkid (Ver3.6 and later) | from Microsoft (Bing) ads | Treated as access excluding the msclkid parameter, with utm_source=microsoft and utm_medium=cpc |
“Ver3.6 and later” items apply to data measured with QA Analytics version 3.6.0.0 or higher.
(There is no retroactive reflection.)