You can choose how many times Google Analytics counts a key event if someone triggers it more than once in a session.
On this page
About counting methods
You can choose from these counting method options for a key event:
- Once per event (Recommended): Counts a key event every time it's triggered. This option is recommended because it reflects the behavior of users on your site or app, and allows you to distinguish between sessions where multiple key events occurred and sessions where only one key event occurred.
- Once per session (Legacy): Counts a key event only once within a particular session .
Example
If someone triggers a key event five times in a session, then:
- For Once per event, Google Analytics counts 5 key events.
- For Once per session, Google Analytics counts one key event.
Note for default counting method:
If you don't make a choice, Google Analytics will automatically use the default counting method. The default depends on how key events were created.
- Once per sessionis the default counting method for all key events that were created from Universal Analytics goals:
- In an automatically created Google Analytics property
- Using the goals migration tool in the Setup Assistant after April 2023
- Once per eventis the default counting method for all other key events.
Change the counting method
You can change the counting method setting at any time for any of your key events.
- Go to Events
within the Data displaymenu. Note: The previous link opens to the last Analytics property you accessed. You must be signed in to a Google Account to open the property. You can change the property using the property selector. You must be a Marketer or above at the property level to choose a counting method.
- In the "Key events" tab, click
to the far right of a key event row.
- Click Change counting method.
- Select your preferred counting method.
- Note: If you can't select an option, you don't have the necessary permissions.
- Click Save.
Note: Any changes to the counting method apply to future key events only, and won't apply to a key event's past data.

