When using our javascript integration to replace numbers dynamically (more on number attribution here), you will find on rare occasions situations where a number is not replaced as intended. There could be a number of reasons for this, for example issues with loading cookies, timing problems loading your website at times, and other edge cases where our implementation simply can't replace a number where it needed to.
One way to prevent data loss and ensure all calls from customers still come via Kaisa numbers (and to have all your data centralised in Kaisa and avoid discrepancies) is to use a Static number as a Fallback Number.
What is a fallback number?
When we talk about fallback numbers we refer to Kaisa static numbers that are found by our javascript integration when scanning your page for numbers, and are replaced the same way as an allowed number.
Wait, what is an allowed number?
An allowed number in Kaisa terminology is the real telephone number in your website that our javascript is looking for and tries to replace. You can add your telephone number in our system to indicate our javascript solution that this is the number it needs to replace each time it finds it. You can read more about allowed numbers here.
How does this work?
Static numbers created in Kaisa will connect to a real number, set up when the Static number was created. This destination is what we call the end number. Our javascript solution will scan your website when it loads, and it will look for numbers that match the Allowed numbers it's looking for. When our script detects a Static number, it will compare the end number the static number connects to with the Allowed numbers it's looking for, and if they match it will replace the Kaisa Static number as if it were the Allowed number.
If the destination for a static number is also an allowed number as well, the static number can be added in your website and our javascript will replace it as if it was the allowed number directly.
If you have any questions at al or would like to know more about this setup with your current implementation, feel free to reach out to us on support@kaisa.io
Comments
0 comments
Please sign in to leave a comment.