Protected content

Login Get access

Google UA

Embedded Analytics
To use Embedded Analytics you must first disable Google UA.

What will UA integration give you
Universal Analytics is the new generation of Google Analytics and it was designed to go beyond the Web. With UA we can now send "hits" that represent any object, resource, process and so on. In the Door Tablet context, we send hits which reflect your resource utilization at three milestones:

1. At the beginning of a meeting
2. At the end of a meeting
3. At the end of the day

1. What percentage of the time a resource is used
2. How many meetings get aborted
3. What kind of length meetings you have, i.e. short ones, long ones
4. When do meetings tend to start and end
5. Which area of resources perform better than others
6. In which city or building do meeting spaces get better used
7. Which country performs better
8. How does utilization compare month on month, year on year
9. Measure behavior during summer periods versus winter periods
10. Which resources exceed targets, which fall behind

• Door Tablet "sees" meetings that have been accessed by the various client displays. If you have an active meeting space or resource that is not accessed by a Door Tablet client its meeting will not be monitored
• When evaluating Door Tablet, UA functionality will be available for 30 days from the first day you enable the UA functions for the first time. After 30 days no more hits will be collected

1. Allow outbound access from the Door Tablet server to one of the UA destinations. Your firewall ports will need to be opened outbound for this purpose
2. Create UA property as a part of your Google Analytics account, or create a new account for this dedicated purpose
3. Define custom dimensions and custom metrics which are required by the Door Tablet hits. You need to do this before you enable the service in Door Tablet
4. Configure Door Tablet to use your UA property by specifying the Property ID. Optionally, you can use the Door Tablet simulator and for this you will need a simulation ID, which is created just like the standard Property ID
5. Restart the Door Tablet Add-in. This will normally start automatically for you, and will be refreshed every now and then

1. After a meeting starts - when a meeting starts Door Tablet ensures that a few minutes have passed which will allow for the cases where meetings are cancelled. The hit is sent around ten minutes after the actual start. The hit is sent as an "event" and its value is 0.
2. After a meeting ends - Door Tablet ensures that the hit is sent after a meeting was extended or actively terminated. The hit is sent around ten minutes after the actual end. The hit is sent as an "event" and its value is the length of the meeting in minutes. For a meeting where there was no check-in, and thus was cancelled by the server, the event value will become 0 and the event will fall into the category of "No Check-in".
3. At the end of the day - Door Tablet will perform this work at 2AM and use all the data from the previous day to report on the total time consumed in reservations. The application collects all the minutes used in reservations and posts this as a "pageview" hit.

1. Each resource, a meeting space, has its own ID and is tracked as a "user"
2. Each resource is also identified as "page" to allow you to see it clearly in report
3. We use the bookable hours for a resource to define the portion of usage time versus the available time. If you do not specify the duration in resources we will assume it's 10 hours per day (8AM to 6PM), five days a week. The working week is defaulted to Monday through Friday but you can easily change this