Few years ago Yandex (Search System) following Google removed any search-phrase information from referer (only origin is known –
https://yandex.…/), and now Yandex-traffic mostly becomes "referral" in GA.
To solve this problem i've added a new organic search source in property tracking settings (we using
analytics.js-script of Universal Analytics):
- Search Engine Name:
- Domain Name Contains:
- Query Parameter and Path Contains left blank.
So, a properly added custom organic source must have a higher priority than referral (as described on Processing flow chart) and matched traffic must becomes "organic".
But it didn't work, and Yandex search traffic still marked as "yandex.ru / referral" instead of "yandex.ru / organic".
I've tryed different combinations of the "Domain Name Contains" pattern:
yandex.ruwith no effect.
By default there are built-in Yandex source, but it catch only traffic with referrer and "text"-parameter – only organic traffic. But Yandex doesn't send path and parameters in the referer anymore, as i told above.
And two built-in hosts – http://www.yandex.com/ and http://yandex.ru – is not enough: Yandex has a many TLDs: yandex.ru, yandex.ua, yandex.kz and many more – one for every country where it works.
So, built-in organic sources for Yandex are obsolete. What's why i'am trying to use a custom organic search.
- Why no one of the variants (
yandex.ru) is not worked for Yandex's traffic and i'am still see same "yandex.ru / referral" share?
- Can regular expression patterns (
https://yandex.ru) be used in the "Domain Name Contains" field of the organic search source?
- Which value for "Domain Name Contains" field should i use for
https://yandex.ru/referer (without any path and parameters in referer URL) as an organic search source?