Uploading data from the system to Universal Analytics
Copy the link to the article

It is also possible to send information about offline orders to Universal Analytics. To do this, in the “Registration methods for uploading” section, tick the offline orders checkboxes; the information about which must be transferred to Google Analytics. Using the "Do not upload orders without products" checkbox, you can select whether orders without products will be uploaded.

For orders in which the Client ID is known, data is transferred to the Universal Analytics account every 2 hours. Offline transactions are uploaded only for those customers whose Client ID is recognised in the system, that is, the customer must have made at least one order or request before via the site.

This setting is useful in cases where orders are received not only via the site, but also to determine the effectiveness of advertising sources. This feature is especially useful when integrating the system with dynamic call tracking services such as CallTouch. Read more in the article "Interaction between CallTouch and Universal Analytics".


If bot request filtering in Google Analytics is enabled in the view settings, then data being uploaded from the system may be blocked. To successfully upload orders from the system to Googe Analytics, we recommend that you disable this filter. Also, if filtering has already been enabled, then after disabling it, the data that has already been sent will not appear in the view (only new orders will appear).

Additional information about the Client ID parameter and scenarios for its use

Client tags (Client ID)- this is service information that does not need to be specified manually. They are automatically generated on the user's computer and saved with all information in Universal Analytics. In this case, there may be the following use cases:

1.In conjunction with CallTouch. The order is created by phone, while CallTouch transfers data (Client ID, source) via its systems, which we send to Universal Analytics.

2.By an already known Client ID. For example, there is standard integration with Universal Analytics and a customer who placed an order on the site. In this case, the system has their Client ID obtained from Universal Analytics. After that, a new order of the same customer is created by phone, but as we now have the Client ID, we can send it to Universal Analytics, as if it was created on the site.

In the second case, it does not matter where the Client ID was obtained from - from GA or from the first case, although in the latter case the data will also be received from CallTouch.

If the Client ID doesn't come from Universal Analytics, but, for example, from CallTouch, then the next time the data is uploaded from Universal Analytics, the system will try to pull up the data for this customer.

For example, a customer visited the store and the visits were recorded in Universal Analytics. If they made an order by phone and the data was transferred to the system via CallTouch, then the visits should be pulled into the system.

Uploading to Universal Analytics retroactively

The setting allows you to specify how old records will be read when uploading in a shorter period. This is necessary for Universal Analytics accounts with heavy loads, where data arrives with a delay.

To enable this setting, you need to go to the Administration > Integration > Universal Analytics section. In the "Data queue time" field, set the required reading time.

Thank you for your feedback.
Was this article helpful?
  • Рекомендации не помогли
  • Нет ответа на мой вопрос
  • Текст трудно понять
  • Не нравится описанный функционал
Previous article
Step 3. Integration of Universal Analytics with RetailCRM
The article describes how data is uploaded from a store in Universal Analytics to your system and how to configure it so that all parameters are uploaded in full.