Selecting users who viewed specific site pages (for example, the product catalog in one of the categories), in order to use Yandex.Direct to offer these users a product or service related to these pages.
If we take the data from the Sources, Summary report, we can select the information about users who went to the site and viewed a page with a promotional offer from March 1 to March 15.
In the Sources, Summary report data, we can select users who completed an order for an amount over 10,000 rubles.
Sometimes, a high volume of internal traffic on a site can indicate that the Yandex.Metrica counter is missing on some pages. Let's look at an example.
A user followed a link from an external source to a page that doesn't have a counter (for instance, contacts.html), then immediately (during the same session) navigated to a page with a counter (in this case, page1.html). This means that two conditions are met: the session starts from page1.html (because Yandex.Metrica doesn't have data about the contacts.html pageview due to the absence of the counter on this page), but the page the user navigated from (contacts.html) belongs to the same site that is specified in the counter settings (http://mysite.example/).
To detect the page without the counter:
This gives us information about the pages that the session started from. To determine how the user got to these pages, add a dimension with the referrer (source) that started the session:
Now the report shows the pages that the session started from, and the second level of the report hierarchy shows the pages that click-throughs came from. For convenience, you can move the Referrer dimension to the top of the list of dimensions. Then the first level will show the pages that presumably might be missing the counter code, and the second level will show where users navigated to from them.
A small number of sessions in this report indicates that everything is probably fine with the counter, and the internal referrals are caused by session timeouts.