# GPS data from experience group instead of device

**URL:** <https://forums.losant.com/t/gps-data-from-experience-group-instead-of-device/5506>\
**Category:** Help\
**Tags:** gps\
**Created:** [June 24, 2024, 9:37am UTC](https://forums.losant.com/t/gps-data-from-experience-group-instead-of-device/5506 "2024-06-24T09:37:54Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![Frank\_Krol](https://avatars.discourse-cdn.com/v4/letter/f/e56c9b/32.png) [@Frank\_Krol](https://forums.losant.com/u/Frank_Krol)\
**Post date:** [June 24, 2024, 9:37am UTC](https://forums.losant.com/t/gps-data-from-experience-group-instead-of-device/5506/1 "2024-06-24T09:37:54Z")

</div>

Hello,

I am working with the CPF template. I was wondering if it is possible to display the GPS data in a GPS history block that’s coming from a experience group tag instead of a device. This would make more sense than to have to create a ‘shadow’ device holding the same GPS data as the group to simulate a customer location.

---

<div class="post-metadata">

**Author:** ![Dylan\_Schuster](https://sea1.discourse-cdn.com/flex015/user_avatar/forums.losant.com/dylan_schuster/32/2850_2.png) [@Dylan\_Schuster](https://forums.losant.com/u/Dylan_Schuster)\
**Post date:** [June 24, 2024, 2:14pm UTC](https://forums.losant.com/t/gps-data-from-experience-group-instead-of-device/5506/2 "2024-06-24T14:14:24Z")

</div>

Yes; in the block, you can return devices matching an experience group ID using an [advanced query](https://docs.losant.com/dashboards/blocks/gps-history/#devices).

This will return data for all devices in the group as well as its child groups, assuming the devices also have the GPS attribute / tag you define as the [data source](https://docs.losant.com/dashboards/blocks/gps-history/#map-data-source-and-duration).

If you want to render a dynamic group from a context variable, you will need to create a [string variable](https://docs.losant.com/dashboards/context-variables/#strings) and [pass the group ID](https://docs.losant.com/experiences/views/#context-variables) to the page renderer - probably as a query param or a path param.

You will also want to verify, in the workflow that renders the dashboard page, that the user who is requesting the dashboard for that specific group ID actually should be allowed access to that group. The [Group: Verify Node](https://docs.losant.com/workflows/experience/verify-group/) is an easy way to do that.