# Core Concepts ### 1. **Triggers** A trigger launches the survey inside your mobile app or website, allowing you to ask users questions at the right moment in their product journey. * Triggers can be based on various user actions, such as: opening a specific screen, clicking a button, or completing an event. * For mobile apps, triggers must be defined in your codebase. However, web applications offer no-code trigger options. * You can add properties (e.g., screen\_name) to each trigger to provide context for each survey response. * When launching a survey, you can select the appropriate trigger from Blitzllama's dashboard. ### **2. Attributes** An attribute is a key-value pair that provides more context about each user. Pass the attribute data to Blitzllama via the SDK or from your analytics tools. Attributes are super useful to create targeted user cohorts. ### **3. Cohorts** A cohort is a segment of users that are created by filtering the user attributes. Use cohorts to precise target your micro-surveys. ### **4. Survey Frequency** **Wait period - t**his is the minimum number of days to wait before surveying the same user again. * The wait period applies across all of Blitzllama's surveys. * This feature ensures that users are not overwhelmed with frequent surveys. **Repeat frequency - y**ou can configure how often a user sees the same survey. * Options include setting limits based on: (i) number of times viewed (e.g., up to 3 times), (ii) response to the first question, (iii) completion of the entire survey. --- # Agent Instructions: Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter: ``` GET https://documentation.blitzllama.com/quickstart-guides/basics.md?ask= ``` The question should be specific, self-contained, and written in natural language. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.