Action names

This document explains action names that are used to describe user-initiated events when integrating reCAPTCHA on mobile applications.

You specify action names in the action parameter of grecaptcha.enterprise.execute() when integrating reCAPTCHA. We recommend using action names that are unique, meaningful, and not specific to users. Action names are not case-sensitive and they can only contain alphanumeric characters, slashes, and underscores. If you have a page with multiple applicable actions, you can concatenate multiple action strings together (for example, cart_view_payment).

Action names help you gain better visibility into how your users are using your site through reCAPTCHA dashboards in the Google Cloud console.

The following table lists some recommended action names and examples of corresponding events. Using the recommended action names also allows reCAPTCHA to associate user actions to page types, and improves the ability to monitor for different forms of attacks, such as attackers attempting to falsify or duplicate actions.

Action name User initiated event
registration or signup Register or sign up on the mobile application.
login Log in to the mobile application.
password_reset Request to reset the password.
get_price Fetch price for an item.
cart_add Add items to the cart.
cart_view View the contents of the cart.
payment_add Add or update payment information (e.g. card details or address).
checkout Check out from the mobile application.
transaction_confirmed Confirmation that a transaction was processed.
play_song Play a song from a list.

What's next