Master precise targeting with conditions that catch exactly the reviews you want to handle
Triggers are the brain of your automation rules – they determine which reviews get automatic responses and which ones don’t. Think of them as smart filters that evaluate every incoming review against your criteria.
The secret to great automations: Start specific, then expand. It’s easier to broaden a narrow rule than to fix an overly broad one that’s responding to the wrong reviews.
Condition:is exactly 5 starsUse case: Thank users who love your app, potentially ask for referrals or feature requests.Risk level: ⭐ Low – Happy users appreciate acknowledgment
The Improvement Opportunity
Condition:is exactly 3 starsUse case: Users who like your app but have specific concerns worth addressing.Risk level: ⭐⭐ Medium – These users can often be converted to higher ratings
The Crisis Manager
Condition:is less than 3 starsUse case: All negative feedback requiring immediate, empathetic response.Risk level: ⭐⭐⭐ High – Frustrated users need careful, personalized handling
does not contain "free" → Avoid users only interested in free featuresdoes not contain "fake" → Skip suspected fake reviewsdoes not contain "competitor" → Ignore comparative reviewsdoes not contain "trial" → Focus on committed users
Target reviews that are highlighted or featured in app store listings.
Is Featured
Is Not Featured
“Featured review is” targets reviews currently shown as featured in the store listing.These reviews are the most visible to potential users browsing your app page. Create specific, well-crafted responses for them since they have an outsized impact on download decisions.Use case: Pair with AI-generated responses and detailed instructions to make sure your reply to a featured review is polished and addresses the reviewer’s points directly.
“Featured review is not” targets all non-featured reviews.Use this to apply different response strategies to regular reviews versus those highlighted by the store.
Featured reviews change over time as the app store rotates them. If a review loses its featured status after your automation already responded, the response remains in place.
Always test before going live! Create automations in disabled mode first, then check the Reviews Feed to see which reviews would have matched your conditions.
Remove one condition at a time to see which is limiting matches
Check for typos in keywords
Consider synonyms and alternative phrasings
Verify your apps are properly connected
Your conditions might be too broad:
Add exclusion keywords (does not contain)
Narrow the rating range
Add language or length restrictions
Split into multiple, more specific automations
Your conditions need refinement:
Review actual matched reviews in your feed
Add negative keywords to exclude unwanted matches
Use more specific keywords
Consider the context of keyword usage
Master these trigger conditions, and you’ll create automations that respond to exactly the right reviews at exactly the right time. Next, learn how to craft the perfect responses in the Actions guide.
Actions
Master template-based and AI-generated responses
Templates
Create response templates that power your automations