AdWords is now Google Ads. Our new name reflects the full range of advertising options we offer across Search, Display, YouTube, and more. Learn more

Analytics
3.1K members online now
3.1K members online now
Dive into multiple domain (Cross/Sub) tracking, implementing Ecommerce and Enhanced Ecommerce, setting up Event tracking, and Universal Analytics code.
 
Guide Me
star_border
Reply

One property with specific devices

[ Edited ]
Visitor ✭ ✭ ✭
# 1
Visitor ✭ ✭ ✭

Hi all

 

We have an ongoing project which is basically a development of an in-store-navigator device. We have it already set up and working in one store. In that store we have 3 specific devices running the application and we can dynamically get info about the devices (it's location, name, id etc.).

 

We are planning to implement google analytics to it. Our main goal is to get device specific data, have a possibility to for example compare usage statistics between the devices etc.

 

What is the most sensible way to achieve that? We've done some research and thought of using named trackers but since we have no experience with that, we do not know if it will be up to our expectations.

 

Thank you!

1 Expert replyverified_user

Re: One property with specific devices

Top Contributor
# 2
Top Contributor
Hi Erik,

so the requirement is to have both specific device usage and an aggregate view of all devices?

Basically you could do:
1) Use one property and assign views based on a view filter which would filter by either a custom dimension or some other dimension which identifies the device
2) use 2 or more GA properties where on each device a separate tracking ID would be used - an option of a rollup property (combines data from multiple devices may be used as well)

There are some things you would probably need to consider though:
1) data volume - hit and sessions generated by a device which will in return give you a clear sign if multiple properties or single property are needed
2) session handling - as this is probably not a simple web behaviour but a public app implementation you should see when the session should be renewed so you do not skew data by multiple users behaving differently (it will make the averages in GA less useful)

Hope it helps!

Kind regards,
Zorin
Web analyst @ escapestudio.net