# of events per user | Community
Skip to main content
G
GusRubio
Level 2
December 21, 2020
Solved

# of events per user

  • December 21, 2020
  • 1 reply
  • 1515 views

Hi all

 

I want to run a report to analyze the number of times users did a specific action/event.

See below more clear example. I want to create a table for a specific time range, where I can see the following information:

 

  • 1 Purchase - 1000 app users
  • 2 Purchases - 800 app users
  • 3 Purchases - 500 app users
  • >3 Purchase - 350 app users

 

How can I do it?

Thanks

This post is no longer active and is closed to new replies. Need help? Start a new post to ask your question.
Best answer by yuhuisg

A quick but repetitive way would be to use Segments.

E.g.

"Visitors with 1 purchase"

  • Visitor scope:
  • Transactions equals 1

"Visitors with 2 purchases"

  • Visitor scope:
  • Transactions equals 2

etc.

Then create a table with your segments as the dimension and Unique Visitors as the metric (assuming that your report suite records app data only).

1 reply

yuhuisg
Community Advisor
yuhuisgCommunity AdvisorAccepted solution
Community Advisor
December 22, 2020

A quick but repetitive way would be to use Segments.

E.g.

"Visitors with 1 purchase"

  • Visitor scope:
  • Transactions equals 1

"Visitors with 2 purchases"

  • Visitor scope:
  • Transactions equals 2

etc.

Then create a table with your segments as the dimension and Unique Visitors as the metric (assuming that your report suite records app data only).

    G
    GusRubioAuthor
    Level 2
    December 22, 2020

    Hi Yuhuisg

    Thanks for your answer.

     

    To be sure I follow you. In segment builder I take the metric Transaction, right?

    In my example I wanted to use orders because I thought it was a clear example for everyone, but in fact I want to measure the number of times a user complete a task in our app (complete a tutorial, use a feature, etc).

    If those tasks doesn't exist as a metric, can I find another way to run the same analysis?

     

    Thank you

    Terms & ConditionsAccessibility statement

    Loading footer...