Beyond selecting prompts and models, Microscope.ai offers several configuration options to customize how your analyses run. Understanding these options helps you optimize your monitoring strategy.
Analysis Settings Overview
Configuration options typically include:
- Basic information (name, description)
- Execution timing and scheduling
- Priority and importance levels
- Notification preferences
- Advanced execution parameters
Basic Configuration
Analysis Name
- Required field
- Use descriptive, meaningful names
- Include purpose, timeframe, or focus area
- Example: "Monthly Brand Baseline - January 2024"
Analysis Description
- Optional but recommended
- Document the analysis objective
- Note target metrics or goals
- Useful for team collaboration
- Helps when reviewing historical analyses
Execution Timing
Run Immediately
Execute the analysis as soon as it's created:
- Best for: One-time checks, urgent audits, immediate insights
- Execution begins within minutes
- Results available in 10-20 minutes (depending on size)
- Good for testing new configurations
Schedule for Later
Set a future date and time for execution:
- Best for: Coordinating with campaigns, regular intervals, off-peak execution
- Specify exact date and time
- Time zone considerations apply
- Can be edited before execution
Recurring Analyses
Set up analyses to run automatically on a schedule.
Frequency Options
Daily
- Execute every day at a specified time
- Best for: High-frequency monitoring, critical metrics, competitive tracking
- Considerations: Uses quota rapidly, may be excessive for most use cases
Weekly
- Execute once per week on a chosen day
- Best for: Regular monitoring, balanced frequency, trend tracking
- Recommended: Most common frequency for ongoing monitoring
Monthly
- Execute once per month on a chosen date
- Best for: Long-term trends, executive reporting
- Considerations: May miss short-term changes
Recurrence Settings
- Start date - When recurring execution begins
- End date (optional) - When to stop recurring execution
- Day/time - Specific execution schedule
- Skip execution if quota exceeded - Safety setting
Weekly analyses on the same day and time provide consistent data for meaningful trend comparisons.
Priority Settings
Some plans offer priority levels for analyses:
Priority Levels
High Priority
- Executes first when multiple analyses are queued
- Faster processing
- Best for time-sensitive monitoring
Normal Priority
- Standard execution queue
- Typical processing time
- Suitable for most analyses
- Default setting
Low Priority
- Executes when resources available
- May take longer to complete
- Good for large exploratory analyses
Execution Context
Brand Context
- Which brand information to include with prompts
- Product catalog scope
- Target audience details
Cost and Quota Management
Quota Considerations
- Each execution consumes quota
- More prompts = more quota used
- More AI models = higher cost
- Monitor remaining quota before scheduling
Execution Limits
- Per analysis - Maximum prompts or models
- Per month - Total executions allowed
- Concurrent - How many can run at once
Editing Analysis Configuration
Before Execution
- All settings can be modified
- Changes take effect immediately
- No impact on previous executions
After Execution
- Can edit for future executions
- Historical executions remain unchanged
- Name and description can always be updated
Recurring Analyses
- Changes apply to future executions
- Can pause, resume, or stop recurrence
- Can change frequency or schedule
Configuration Best Practices
Naming Conventions
- Include date or period: "Q1 2024 Brand Baseline"
- Note focus: "Product Launch - Widget X"
- Indicate frequency: "Weekly Competitive Analysis"
Description Guidelines
- State the objective clearly
- Document any special configuration
- Note who requested it (if applicable)
- Include success criteria or KPIs
Scheduling Strategy
- Daily - Only for critical, fast-changing metrics
- Weekly - Best for most ongoing monitoring
- Monthly - For long-term trends and reports
- Choose consistent times for comparability
Notification Strategy
- Enable for one-time critical analyses
- Use "significant changes" for recurring
- Disable for frequent recurring analyses
- Configure team notifications for shared analyses
Common Configuration Scenarios
Campaign Launch Monitoring
- Frequency: Daily during campaign, weekly after
- Priority: High during launch phase
- Notifications: Enabled with daily digest
- Duration: Set end date after campaign
Ongoing Brand Monitoring
- Frequency: Weekly
- Priority: Normal
- Notifications: Significant changes only
- Duration: Indefinite recurrence
Quarterly Executive Report
- Frequency: Monthly on last day of month
- Priority: High
- Notifications: Email with summary
- Scope: All categories, all models
Competitive Intelligence
- Frequency: Weekly
- Priority: Normal or High
- Notifications: Enabled
- Focus: Comparison prompts only
Troubleshooting Configuration Issues
Analysis Won't Save
- Check all required fields are filled
- Verify at least one prompt selected
- Ensure at least one model selected
- Check quota availability
Scheduled Analysis Didn't Run
- Verify execution history for errors
- Check quota wasn't exceeded
- Confirm analysis wasn't paused
- Review notification logs
Recurring Analysis Stopped
- Check if end date was reached
- Verify quota availability
- Review account status
- Check for manual pause
Next Steps
With configuration mastered, you're ready to:
- Learn prompt and model selection strategies
- Run your first configured analysis
- Set up recurring monitoring
- Optimize based on execution results