Storage
Stay organized with collections
Save and categorize content based on your preferences.
To better customize a user's experience with your Action, you can save data
between turns of a conversation or across multiple conversations with that user.
Saved data can provide helpful reprompts in a single conversation, store game
scores across sessions, or remember small pieces of information for a user.
Data can be stored in multiple ways during a conversation. In a single
conversation, you can use types to annotate training phrases in intents or
to store information from the user during slot filling.
You can also have your Action store values using your webhook with the following
storage methods:
- Session storage
- User storage
- Home storage
Use these storage methods in combination with each other to best match how you
want to persist information within or between invocations of your Action.
Session storage
Use session storage when you want to persist a value for a single
conversation, but not from one conversation to another. During a conversation,
any data collected using types is stored in session storage.
User storage
Use user storage when you want to persist a value across conversations for a
single verified user. For example, a game can save a user's high score in user
storage and present the high score in the welcome message each time the user
starts a new conversation.
Home storage
Use home storage when you want to persist a value across conversations for
devices in a single household (based on Home Graph). Home storage isn't
specific to any particular user, so any user in the household can contribute
towards it. When using home storage, Google additionally presents a notification
once to verified users, and on each invocation by guest users (up to once per 10
minutes).
Except as otherwise noted, the content of this page is licensed under the Creative Commons Attribution 4.0 License, and code samples are licensed under the Apache 2.0 License. For details, see the Google Developers Site Policies. Java is a registered trademark of Oracle and/or its affiliates.
Last updated 2024-09-18 UTC.
[[["Easy to understand","easyToUnderstand","thumb-up"],["Solved my problem","solvedMyProblem","thumb-up"],["Other","otherUp","thumb-up"]],[["Missing the information I need","missingTheInformationINeed","thumb-down"],["Too complicated / too many steps","tooComplicatedTooManySteps","thumb-down"],["Out of date","outOfDate","thumb-down"],["Samples / code issue","samplesCodeIssue","thumb-down"],["Other","otherDown","thumb-down"]],["Last updated 2024-09-18 UTC."],[[["\u003cp\u003eActions on Google can save data to customize user experiences, enabling features like reprompts and storing information across conversations.\u003c/p\u003e\n"],["\u003cp\u003eData can be saved within a single conversation using types or across conversations with session, user, or home storage, depending on the desired persistence.\u003c/p\u003e\n"],["\u003cp\u003eSession storage retains data for a single conversation, user storage saves data for a specific user across conversations, and home storage persists data for all users on devices in a household.\u003c/p\u003e\n"]]],["Data in user interactions can be saved within single or multiple conversations to enhance user experience. Data can be stored through types in intents or via webhook storage methods: session storage for single conversation data, user storage for data across conversations of a specific user, and home storage for data across conversations for all users in a household. These methods can be used in conjunction to manage how information persists.\n"],null,["To better customize a user's experience with your Action, you can save data\nbetween turns of a conversation or across multiple conversations with that user.\nSaved data can provide helpful reprompts in a single conversation, store game\nscores across sessions, or remember small pieces of information for a user.\n\nData can be stored in multiple ways during a conversation. In a single\nconversation, you can use [types](/assistant/conversational/types) to annotate training phrases in intents or\nto store information from the user during slot filling.\n\nYou can also have your Action store values using your webhook with the following\nstorage methods:\n\n- Session storage\n- User storage\n- Home storage\n\nUse these storage methods in combination with each other to best match how you\nwant to persist information within or between invocations of your Action.\n\nSession storage\n\nUse [session storage](/assistant/conversational/storage-session) when you want to persist a value for a single\nconversation, but not from one conversation to another. During a conversation,\nany data collected using [types](/assistant/conversational/types) is stored in session storage.\n\nUser storage\n\nUse [user storage](/assistant/conversational/storage-user) when you want to persist a value across conversations for a\nsingle verified user. For example, a game can save a user's high score in user\nstorage and present the high score in the welcome message each time the user\nstarts a new conversation.\n\nHome storage\n\nUse [home storage](/assistant/conversational/storage-home) when you want to persist a value across conversations for\ndevices in a single household (based on [Home Graph](/assistant/smarthome/concepts/homegraph)). Home storage isn't\nspecific to any particular user, so any user in the household can contribute\ntowards it. When using home storage, Google additionally presents a notification\nonce to verified users, and on each invocation by guest users (up to once per 10\nminutes)."]]
