Post by account_disabled on Jan 25, 2024 9:10:02 GMT
Do not rush to get scared - this is not about riddles and mysticism. This seemingly incomprehensible name hides ample opportunities. A tracked entity allows you to add an additional parameter to the call tracking data and transfer it to another system. Read how it works in practice and how it is useful when integrating with other systems. Reading time: 5 minutes What is a tracked entity Benefits of Tracked Entities conclusions What is a tracked entity A tracked entity is a functionality that allows call tracking to “pull” an additional parameter from your website and associate it with a user session. The obtained data can be transferred to other systems.
Typically, Google Fax Lists identifies a user by assigning an identifier to his device - client ID . Ringostat can intercept this parameter and associate it with a specific customer visit and call when it occurs. Thanks to this, dynamic call tracking for the site functions. This is described in more detail in the article “What is call tracking and how it works . ” Increase the effectiveness of advertising with Ringostat call tracking Find out which sources bring calls - right down to the keyword in contextual advertising Test for free However, tracked entities allow you to expand these capabilities. Here are two examples of situations in which tracked entities would be particularly useful.
Let’s imagine that the site has not only call tracking and Google Analytics code installed, but also another conventional “system”. It independently generates and assigns the visitor its own, additional identification parameter. For example, when a user registers on a site. In this case, the tracked entity would work like this: A visitor visits the site. Google's tracking code assigns it a client ID. The “System”, in turn, assigns its own identifier - User 123. The call tracking system issues a replacement number to the visitor. After the call, Ringostat “pulls out” a bunch of data: client ID + User 123 + phone number. And links it to the visitor in Ringostat. tracked entities ringostat, call tracking - call analytics The second case when tracked entities will be useful is if Ringostat and another system with which we do not have ready integration are used.
Typically, Google Fax Lists identifies a user by assigning an identifier to his device - client ID . Ringostat can intercept this parameter and associate it with a specific customer visit and call when it occurs. Thanks to this, dynamic call tracking for the site functions. This is described in more detail in the article “What is call tracking and how it works . ” Increase the effectiveness of advertising with Ringostat call tracking Find out which sources bring calls - right down to the keyword in contextual advertising Test for free However, tracked entities allow you to expand these capabilities. Here are two examples of situations in which tracked entities would be particularly useful.
Let’s imagine that the site has not only call tracking and Google Analytics code installed, but also another conventional “system”. It independently generates and assigns the visitor its own, additional identification parameter. For example, when a user registers on a site. In this case, the tracked entity would work like this: A visitor visits the site. Google's tracking code assigns it a client ID. The “System”, in turn, assigns its own identifier - User 123. The call tracking system issues a replacement number to the visitor. After the call, Ringostat “pulls out” a bunch of data: client ID + User 123 + phone number. And links it to the visitor in Ringostat. tracked entities ringostat, call tracking - call analytics The second case when tracked entities will be useful is if Ringostat and another system with which we do not have ready integration are used.