Users don't need to install anything to invoke your Actions on the Assistant. However, all Actions projects must be submitted and approved before users can discover and invoke them. Once approved, your users can invoke and discover your Actions in a variety of ways, and we provide metrics for you to track and analyze how your Actions are being used to better serve your users.
How users invoke and discover Actions
How users discover and invoke your Actions is very important in its long term success. You have control over these variables by defining your own invocation name and Action phrases. To better understand how this works, the following examples show how users might invoke and discover an imaginary Actions project called GeekNum.
- By invocation name
- Users can explicitly invoke your Actions by saying things like "Ok Google, talk to Geek Num" or "Ok Google, speak to Geek Num".
- By invocation name and action phrase
- Users can explicitly invoke your Actions with an Action phrase by saying things like "Ok Google, talk to Geek Num to learn about the number 42"
- By Action phrase
- Users discover your Actions by saying things like "Ok Google, learn about the number 42". The Assistant knows you can handle this action and says "For that, try saying 'Ok Google, let me talk to Geek Num'". Action phrases give you an easy and powerful way to increase usage of your Actions by supporting specific and differentiated tasks that your Actions excel at handling.
- Actions Directory
- Users can browse and discover Actions that they might want to use on the Actions directory. Your Actions project listing shows a description of your Actions, the surfaces they're available on, sample invocations, ratings, and more.
- On your website
- You can provide a link to the web or mobile version of your Action project's listing in our directory, so you can promote your Actions and drive usage. You should write good descriptions and provide great images on what your Action's experience is like to increase traffic and ranking.
- Action links
- You can generate a link to a specific Action in your project. When a user clicks on your link on a web or mobile browser, they will be directed to the Assistant and your Action will be invoked.
You set the capabilities your Actions require in the Actions console, which determines what surfaces your Actions can be invoked on. In addition, you can deliver different responses or conversations based on devices by checking the current surface's runtime capabilities.
Submitting your Actions project for approval
The Actions on Google console is where you start your development process by creating an Actions project that will contain your Actions. You also use the Actions console throughout development, to access the Actions Simulator to test your Actions.
And, when you're ready to deploy and submit your Actions for approval, you submit your project for approval and manage that in the Actions console (make sure your fulfillment is working!). Here, you'll specify things such as your invocation name and pronunciation and the surfaces that your Actions can appear on.
When you submit your Actions project, our reviewers use and test it to find issues, bugs, or policy violations. To ensure a quick approval, we provide a launch checklist that you should go through before submitting your project for approval.
Viewing Action analytics
The Actions console shows analytics for usage, health, and discovery after your actions have been in production. View stats such as the amount of conversations, length of conversations abort rate, error rates, and more, to analyze ways to increase engagement.