header
Solved

How is the "Number of Times Used" metric in engagements calculated?

  • 4 February 2020
  • 2 replies
  • 89 views

Userlevel 3

We’re using engagements to help educate users who have had some experience with a particular module but have some questions about the targeting criteria. Here is the setup:

 

 

My questions is: What determines "Number of Times Used"? Is it:

  1. Number of pageviews associated with that module?
    1. In that case would simply refreshing 5 times trigger this engagement?
  2. Is it number of sessions?
    1. So the user would need to access the module in 5 different sessions to trigger?
  3. In the above case does any event within the module trigger it?
    1. If that module has click features within it, would that mean 5 clicks on anything in the module would trigger it?

Thanks!

icon

Best answer by link_black 5 February 2020, 03:46

Hi Adam,

 

Thanks for posting to PX Community!

 

I am wondering if this is a trick question based on your screenshot above. 🙂 Usually we see "Number of Times Used" for only a single “Feature” not by a “Module”, but in either case PX will calculate the "Number of Times Used" the same way.

 

A “Module” can have one or more “Features” … and even other “Sub-Modules” under it.  So, by including a “Module” being used “RIGHT NOW” in your Audience Logic, it will be “true” for any user that is using a mapped “Feature” (in our Product Mapper) under that “Module” … including “Sub-Module” Features too.

 

"Number of Times Used" for a “Module” would be the sum of all tracked user events that are mapped to any “Feature” underneath that “Module”.  And, "Number of Times Used" for a “Feature” would be the sum of all user events that are mapped to that “Feature”.  This should answer question # 3 above.

 

For context, “Features” can be mapped by URL (page views), CSS Selector (mouse/button/link clicks), or using Custom Events (extra PX code added in your application).

 

If the “Feature” is mapped using the URL method, then refreshing the page will generate a new event each time and increment "Number of Times Used" for both the “Feature” and all parent “Module(s)”. This should answer question #1 above.

 

If the “Features” are mapped using non-URL methods, this will apply…

 

If the “Feature” is mapped using a CSS selector, then clicking the mapped page section or button/link will increment "Number of Times Used" for both the “Feature” and all parent “Module(s)”.

 

If the “Feature” is mapped using a PX Custom Event, then refreshing the page (or clicking a mapped  page section or button/link) will likely generate a new PX Custom Event event call every time … unless your developer has done something special to prevent these “duplicates” within your code … and will increment "Number of Times Used" for both the “Feature” and all parent “Module(s)”. 

 

And lastly, the "Number of Times Used" is not PX Session dependent and is incremented with each tracked  “Feature” event whether in a single PX session or across multiple PX sessions.  This should answer question #2 above.

 

Try this yourself with one of your “Features” by simulating a the user’s activity, looking at the PX User Profile’s Recent Activity column,  and within PX Adoption Analytics.  

 

I hope this helps!

 

 

View original

2 replies

Userlevel 6
Badge

Hi Adam,

 

Thanks for posting to PX Community!

 

I am wondering if this is a trick question based on your screenshot above. :) Usually we see "Number of Times Used" for only a single “Feature” not by a “Module”, but in either case PX will calculate the "Number of Times Used" the same way.

 

A “Module” can have one or more “Features” … and even other “Sub-Modules” under it.  So, by including a “Module” being used “RIGHT NOW” in your Audience Logic, it will be “true” for any user that is using a mapped “Feature” (in our Product Mapper) under that “Module” … including “Sub-Module” Features too.

 

"Number of Times Used" for a “Module” would be the sum of all tracked user events that are mapped to any “Feature” underneath that “Module”.  And, "Number of Times Used" for a “Feature” would be the sum of all user events that are mapped to that “Feature”.  This should answer question # 3 above.

 

For context, “Features” can be mapped by URL (page views), CSS Selector (mouse/button/link clicks), or using Custom Events (extra PX code added in your application).

 

If the “Feature” is mapped using the URL method, then refreshing the page will generate a new event each time and increment "Number of Times Used" for both the “Feature” and all parent “Module(s)”. This should answer question #1 above.

 

If the “Features” are mapped using non-URL methods, this will apply…

 

If the “Feature” is mapped using a CSS selector, then clicking the mapped page section or button/link will increment "Number of Times Used" for both the “Feature” and all parent “Module(s)”.

 

If the “Feature” is mapped using a PX Custom Event, then refreshing the page (or clicking a mapped  page section or button/link) will likely generate a new PX Custom Event event call every time … unless your developer has done something special to prevent these “duplicates” within your code … and will increment "Number of Times Used" for both the “Feature” and all parent “Module(s)”. 

 

And lastly, the "Number of Times Used" is not PX Session dependent and is incremented with each tracked  “Feature” event whether in a single PX session or across multiple PX sessions.  This should answer question #2 above.

 

Try this yourself with one of your “Features” by simulating a the user’s activity, looking at the PX User Profile’s Recent Activity column,  and within PX Adoption Analytics.  

 

I hope this helps!

 

 

Userlevel 3

This is perfect! Thanks for not only a quick answer but a thorough one! It 100% answers my questions. Much appreciated!

Reply