Hello,
we have just posted a new Acoustic Experience Analytics (Tealeaf) on Cloud course on the Acoustic Academy.
Widgets – Geo Analytics Report
In this course you'll find:
- Use cases for creating Geo Analytics reports
- How to navigate to and configure a Geo Analytics report
- Adding thresholds to Geo Analytics reports
- An overview of the Geo Analytics Summary Card
- An overview of the available data views
Please use this forum for any course-specific questions and discussions.
-
I skimmed through the videos from Tania Flagg as well, didn't find the below info - I'm sure that I wouldn't be the first to ask this Q
Does Geo gets labeled based on the IP only, OR consider the firewall connectivity as well..? because I see users from 1 state regardless users geo loc.
-
Geolocation data is obtained using the standard W3C Geolocation API of the user's browser.
Geolocation capture must be first enabled in the UI Capture configuration in the modules section (note, it is disabled by default).
"modules": {
//...
"geolocation": {
"enabled": true,
"triggers": [
{
"event": "load"
}
]
}
//...
}When you enable Geolocation, you enable capturing the device's geolocation information. Data is captured only if the user gives the application permission to use geolocation data. If the user does not give permission to use geolocation data, no data is captured, even if you enable Geolocation.
When collected, the returned location data is provided by the user's browser itself.
Best. Alek.
Please sign in to leave a comment.
Comments