How many times does a client visit a developer's website before calling?
Posted: Mon Dec 23, 2024 9:28 am
Content
Raw Metrics Data
Transferring call data to Metrica
Processing Metrica logs in BigQuery
There is a widespread belief among marketers that when buying real estate, a client spends a long time choosing an apartment: he visits the developers' websites many times, studies everything carefully, and only then calls. This is said about media platforms and "reach" resources: supposedly clients go from them to the developer's website, study the information, then return to the website, for example, by branded queries through search engines, and only then call. In reality, this is often not the case.
To assess how long it takes a client to make a decision telegram dating philippines about a call, I suggest finding in the raw Metrica data from which visit to the site clients call the developer.
Dynamic call tracking will be needed . In our case, this is CoMagic (UIS), raw data from Yandex.Metrica and Google BigQuery.
Raw Metrics Data
In the Metrica interface, data is aggregated, i.e. calculated for a specific group of visits. The basis for these calculations is raw data — records of individual visits or views. A table with these records is transmitted via the Logs API — a special interface for working with Metrica logs, with each record supplemented with information from Metrica.
Example of Logs API unloading. The first column is the unique visit ID, the second is the user ID, the third is what goals set in Metrica the user achieved during this visit.
Transferring call data to Metrica
With dynamic call tracking, each user session on the site gets its own phone number. For each such session, CoMagic determines clientIDMetrics via yaCounterXXXXXX.getClientID().
In the CoMagic interface, clientIDyou can find this in the Call List → Calls report:
Not displayed by default, select the "ClientID Yandex.Metrica" field in the report designer
CoMagic sends a CSV table to Metrica, which contains ClientIDthe date and time of the visit:
Metrica receives information about the call from CoMagic and, using ClientID, adds this data to the visitor's visit that preceded the call.
CoMagic and Metrica are synchronized once a day, and data is transferred for the previous day. On the 2nd, 7th, 14th, and 20th day, CoMagic resends data to Metrica if something has changed in the call information, for example, if tags have been added to the call.
In Metrika, calls are tracked using goals - a special goal is created when data is first transferred from CoMagic. It is displayed in the service, in the section Settings → Goals. The name and description of the goal can be arbitrary.
Raw Metrics Data
Transferring call data to Metrica
Processing Metrica logs in BigQuery
There is a widespread belief among marketers that when buying real estate, a client spends a long time choosing an apartment: he visits the developers' websites many times, studies everything carefully, and only then calls. This is said about media platforms and "reach" resources: supposedly clients go from them to the developer's website, study the information, then return to the website, for example, by branded queries through search engines, and only then call. In reality, this is often not the case.
To assess how long it takes a client to make a decision telegram dating philippines about a call, I suggest finding in the raw Metrica data from which visit to the site clients call the developer.
Dynamic call tracking will be needed . In our case, this is CoMagic (UIS), raw data from Yandex.Metrica and Google BigQuery.
Raw Metrics Data
In the Metrica interface, data is aggregated, i.e. calculated for a specific group of visits. The basis for these calculations is raw data — records of individual visits or views. A table with these records is transmitted via the Logs API — a special interface for working with Metrica logs, with each record supplemented with information from Metrica.
Example of Logs API unloading. The first column is the unique visit ID, the second is the user ID, the third is what goals set in Metrica the user achieved during this visit.
Transferring call data to Metrica
With dynamic call tracking, each user session on the site gets its own phone number. For each such session, CoMagic determines clientIDMetrics via yaCounterXXXXXX.getClientID().
In the CoMagic interface, clientIDyou can find this in the Call List → Calls report:
Not displayed by default, select the "ClientID Yandex.Metrica" field in the report designer
CoMagic sends a CSV table to Metrica, which contains ClientIDthe date and time of the visit:
Metrica receives information about the call from CoMagic and, using ClientID, adds this data to the visitor's visit that preceded the call.
CoMagic and Metrica are synchronized once a day, and data is transferred for the previous day. On the 2nd, 7th, 14th, and 20th day, CoMagic resends data to Metrica if something has changed in the call information, for example, if tags have been added to the call.
In Metrika, calls are tracked using goals - a special goal is created when data is first transferred from CoMagic. It is displayed in the service, in the section Settings → Goals. The name and description of the goal can be arbitrary.