Post by account_disabled on Feb 11, 2024 10:43:45 GMT
You have noticed that the number of successful transactions has dropped sharply in the E-commerce reports over the past week. However, their number in CRM remained at the same level. What is the reason? After checking all your view settings, you have concluded that the problem is not with Google Analytics. Since transaction data comes through the Measurement Protocol, you decide to check the correctness of the https request - there is probably an error in it. However, the https request turned out to be correct.
Cause If you had anticipated this case in advance and Antarctica Email List created a Raw Data View, you would have solved this problem faster. Raw Data View has transactions, which means there are problems in settings and filters. It turns out that someone excluded calls from robots and “spiders” in the Master View (“working”) view, which affected the number of transactions.
Excluding robots and spiders in view settings spiders in view settings How to fix? In order not to lose original data when adding new filters and other adjustments at the presentation level, we recommend creating at least a Raw Data View, a Test View, and a Master View. The Raw Data View remains untouched for the life of the resource and does not contain any filters. It stores “raw” - clean - data. Test View - intended for testing planned changes to the Master View, for example, new filters. The Master View view contains the filters tested in the test view.
Cause If you had anticipated this case in advance and Antarctica Email List created a Raw Data View, you would have solved this problem faster. Raw Data View has transactions, which means there are problems in settings and filters. It turns out that someone excluded calls from robots and “spiders” in the Master View (“working”) view, which affected the number of transactions.
Excluding robots and spiders in view settings spiders in view settings How to fix? In order not to lose original data when adding new filters and other adjustments at the presentation level, we recommend creating at least a Raw Data View, a Test View, and a Master View. The Raw Data View remains untouched for the life of the resource and does not contain any filters. It stores “raw” - clean - data. Test View - intended for testing planned changes to the Master View, for example, new filters. The Master View view contains the filters tested in the test view.