Targeting Essentials
Last updated
Last updated
You can show the survey only to users who belong to or do not belong to a specific cohort. The cohort dropdown will list all the cohorts in your projects.
Note: To create or update cohorts, follow these steps:
Go to the dashboard’s homepage and navigate to the Users & Cohorts tab.
Click the Create User Cohort button to create a new cohort. You can create cohorts in the following ways:
Uploading a list of user IDs:
Select Create User Cohort > Upload CSV.
Syncing cohorts from other tools like Amplitude, Mixpanel, or Segment:
Refer to the documentation here for integration details.
Segmenting users by their attributes:
Select Create User Cohort > Create using conditions.
You can use "in" or "not in" to decide whether to show or not show the survey to specific user cohorts.
Further refine your targeting using user attributes passed to Blitzllama. User attributes are persistent properties that define a user.
Default Attributes: Blitzllama provides a set of default user attributes like user ID and user creation date.
Custom Attributes: You can define custom attributes by:
Uploading a CSV file with user IDs and attributes:
Navigate to Users & Cohorts > Create User Cohort > Upload CSV with user IDs and attributes.
To view all defined user attributes, go to Users & Cohorts > All Attributes.
For example, define user attributes such as "user type," "subscription plan," or demographic details to effortlessly segment and reach out to the right users. All the user attributes and event properties will be available for download along with the users' responses.
Blitzllama uses an event-based architecture to trigger surveys at the right moment as users browse the app or website.
From the dashboard:
Choose the event to trigger the survey using the Event Dropdown.
Note: Ensure all events are already defined in the codebase for mobile and web integrations. For web integrations, Blitzllama offers a no-code tracker setup.
Features:
Triggering on Multiple Events:
If multiple events are selected, the survey is shown at the first event the user encounters.
Event Properties:
Use event properties to filter users further. For example:
Event: "tournament page"
Properties: "games played" or "result."
Example: Show the survey only to users who land on the tournament page and have played specific games (e.g., X or Y).
Event Performed Filter:
Show the survey to users who have performed the event n times or fewer.
Use funnel-based targeting to address drop-offs in conversions or improve user journey understanding.
Example Use Case: If the user:
Adds items to their shopping cart.
Lands on the shopping cart page.
Does not click "Buy Now."
You can trigger a survey immediately after they drop off at this stage.
How to Configure:
Create event sequences directly on the events configuration.
Define which events should be performed or not performed - these are the qualifying events.
Define the event at which the user should get the survey.
Optionally delay the survey by n seconds to make it less jarring.
Example: If a user lands on the pricing page but performs no action for 10 seconds, trigger the survey after the delay.
If multiple surveys are configured for the same event or trigger point, you can prioritize which survey should be displayed first.
To avoid oversurveying users, Blitzllama offers Survey Frequency controls with two components:
1. First-Time Frequency
Define the cooldown period between surveys for a user who has not seen any Blitzllama survey recently.
Example: If the first-time frequency is set to 7 days, a user who sees a survey on Day 1 will not see another survey until Day 7.
2. Repeat Frequency
Control how often users should see a survey with these configurations:
Option
Description
Display Only Once
The user sees the survey only once, regardless of their response.
Display Survey Until User Responds
Retry every X days until the user answers any survey question. Set the maximum number of views with Max Views.
Display Until Every Question Is Answered
Retry every X days until all survey questions are answered.
Recurring Survey
Users can retake the survey every X days, even if they’ve responded. Control the total views per user.
Response Limits:
Set a cap on the total number of survey responses (up to 100,000).
Example: Stop showing the survey to new users once 50,000 responses are recorded.
Daily Limits:
Control the number of responses recorded per day.
Example: Collect up to 50 responses daily. The survey will pause for the rest of the day and resume the following day.
