Question

Count of unique url hits grouped by one specific query param

  • 14 November 2023
  • 6 replies
  • 35 views
C

I use URL query params for specific detail view of objects, which have ids like 12345. (example: mysite.com/somepage-withamap?objectid=12345)

Using metrics, I am able to count how many hits I had when the page was “mysite.com/somepage-withamap” and the query params included “objectid”.

I want to go one step further: I want unique hits for each object. I want to know how often each unique object’s detail view was seen - so if I have multiple visits of objectid=12345, I want to count that as only 1 hit.

How? :)

6 replies

lindsay
Rank
Userlevel 5
Badge

Hey @corker1994! Thanks so much for reaching out! 😊

So I understand exactly what you’re looking to do, I would love if you could please clarify or share an example to illustrate the user behaviour you’re trying to measure. Specifically, I would like to learn more about how multiple visits of objectid=12345 could translate to only 1 hit.

Once I have this information, I should be able to point you in a better direction here! 

 

 

Lindsay- Community Manager
C

Thanks for the reply @lindsay !

For us, a unique objectid represents always the same object, a pothole detection in our app. And we’re looking to know, of the possible universe of pothole detections we display (there’s thousands), how many are actually ever seen. If I can’t do uniques, then 100 hits on one pothole might make us think that customers are viewing 100 potholes, which is not true. Hope that makes sense!

D
Userlevel 1
Badge +1

Hi @corker1994

I’m taking a shot in the dark and I apologize if I don’t fully understand the ask but are these object ID’s distinct elements on a page (or pages)? If so - have you tried using “watch elements”? 

lindsay
Rank
Userlevel 5
Badge

Hey @corker1994! Thank you so much for sharing that context, that’s super helpful!

Thanks for sharing your suggestion, @drozo! I love the direction you’re thinking in for this, but since the ids are part of the URL query param, they would also have to be present within an element sector in order for watched elements to work. 

If you have thousands of pothole detections, then a metric wouldn’t be your best option since that will have a limit to the results it shows. If it were fewer than our limit, or, you’re ok with the results being limited, there may be a way to do this with a metric using the "Unique property" option. This would require you to configure that object ID to be sent in as either a custom event property or page property.

Having said that, in order to get full results with the possible amount of data you have and these particular requirements, you would need to use data exports and apply your own data analysis. Alas, data exports are only available on Advanced + Enterprise plans. 

Please let me know if you have any other questions! If you decide to try to setup that metric and would like help, please let me know and I can look into it further or create a support ticket on your behalf! 😊

Lindsay- Community Manager
C

Thanks everyone, think I get the gist! This isn’t critical so maybe I let it go for a while :)

lindsay
Rank
Userlevel 5
Badge

Sounds good, @corker1994! I’m happy to help whenever you decide to look into this! 😊

Lindsay- Community Manager

Reply


Terms & ConditionsCookie settings