SlateoAPI Reference

Building and Sharing Reports

Learn how to turn queries into dashboards, schedule reports, and share insights with stakeholders using Slateo. This guide covers the full workflow from query to stakeholder.

Overview

Reports transform ad-hoc queries into repeatable insights. Instead of running the same query manually, you can:

  • Save queries as reports
  • Combine multiple queries into dashboards
  • Schedule automatic updates
  • Share results with stakeholders
  • Track metrics over time

This guide walks through building a complete reporting workflow.

From query to report

Start with a useful query from your ad-hoc exploration.

Identifying report-worthy queries

Good candidates for reports:

  • Regularly needed - You or others run this query weekly or more
  • Clear metric - Answers a specific business question
  • Stakeholder interest - Someone outside your team wants to see this data
  • Trend tracking - Useful to monitor over time

Converting a query to a report

Once you have a useful query:

  1. Click Save Query in the query editor
  2. Name it clearly - "Weekly Active Users - Mobile App"
  3. Add description - Explain what the report shows and why it matters
  4. Tag it - Add tags like "product", "weekly", "executive"
  5. Set default parameters - Configure time ranges and filters

Reports use the same SQL as your original query but can be re-run with fresh data.

Parameterizing reports

Make reports flexible with parameters:

-- Instead of hardcoding dates:
SELECT COUNT(DISTINCT user_id) 
FROM events 
WHERE event_date >= '2025-03-01'

-- Use parameters:
SELECT COUNT(DISTINCT user_id) 
FROM events 
WHERE event_date >= {{start_date}}

Users can adjust parameters when running the report:

  • Change date ranges
  • Filter by region or product
  • Adjust thresholds

Creating dashboards

Dashboards combine multiple reports into a single view.

Planning your dashboard

Before building, decide:

  • Audience - Who will use this dashboard?
  • Purpose - What decisions does it support?
  • Metrics - Which 3-5 key metrics matter most?
  • Frequency - How often will it be viewed?

Dashboard structure

Organize dashboards with a clear hierarchy:

Top section - Key metrics at a glance

  • Total revenue
  • Active users
  • Conversion rate

Middle section - Trends over time

  • Daily/weekly/monthly charts
  • Year-over-year comparisons
  • Growth rates

Bottom section - Detailed breakdowns

  • By region, product, or segment
  • Top performers and underperformers
  • Detailed tables for drill-down

Adding visualizations

Choose the right chart type for each metric:

  • Line charts - Trends over time
  • Bar charts - Comparisons across categories
  • Tables - Detailed data with multiple dimensions
  • Single value - Key metrics like total revenue

Keep dashboards focused. If you need more than 8 visualizations, consider splitting into multiple dashboards.

Example dashboard: Product metrics

A product team dashboard might include:

  1. Daily Active Users (line chart)
  2. Weekly Retention (line chart)
  3. Feature Adoption (bar chart)
  4. Top User Actions (table)
  5. Error Rate (single value with trend)

Scheduling reports

Automate report delivery so stakeholders get updates without asking.

Setting up a schedule

For any saved report:

  1. Open the report in Slateo
  2. Click Schedule in the top right
  3. Choose frequency:
    • Daily at 9am
    • Weekly on Monday morning
    • Monthly on the 1st
  4. Select delivery method:
    • Email to specific addresses
    • Slack channel post
    • Both
  5. Configure format:
    • Inline results
    • CSV attachment
    • Link to live report

Schedule examples

Daily standup metrics

  • Frequency: Every weekday at 8am
  • Delivery: #team-standup Slack channel
  • Format: Inline table with key metrics

Weekly executive summary

  • Frequency: Monday at 9am
  • Delivery: Email to exec team
  • Format: Dashboard link + CSV attachment

Monthly business review

  • Frequency: 1st of each month at 6am
  • Delivery: Email to stakeholders
  • Format: PDF dashboard export

Scheduled reports run with the latest data, so recipients always see current information.

Sharing with stakeholders

Different stakeholders need different levels of access.

Sharing options

Direct link - Share a URL to the report

  • Recipients need Slateo access
  • They see live, up-to-date data
  • Best for team members and regular users

Email - Send results via email

  • No Slateo access required
  • Static snapshot of data
  • Best for external stakeholders

Slack - Post to a channel

  • Keeps data in team communication flow
  • Can include inline results or links
  • Best for team updates and discussions

Export - Download as CSV or PDF

  • For presentations or offline analysis
  • Static data at time of export
  • Best for board meetings or reports

Permission considerations

When sharing reports, consider:

  • Data sensitivity - Does this contain PII or confidential metrics?
  • Access level - Should recipients be able to modify the query?
  • Refresh frequency - Do they need real-time data or periodic updates?

For sensitive data:

  • Use email or Slack instead of public links
  • Set expiration dates on shared links
  • Limit access to specific users

Best practices

Follow these guidelines for effective reporting.

Design principles

Keep it simple

  • Focus on 3-5 key metrics per dashboard
  • Use clear, descriptive titles
  • Avoid jargon in metric names

Make it actionable

  • Include context: "20% increase vs. last month"
  • Add thresholds: "Target: 10,000 users"
  • Highlight anomalies: "Sales dropped 15% this week"

Ensure accuracy

  • Document data sources and definitions
  • Add "Last updated" timestamps
  • Include data quality notes if relevant

Maintenance

Regular reviews

  • Audit reports quarterly
  • Remove unused reports
  • Update queries as schemas change

Version control

  • Note major changes in report descriptions
  • Keep old versions for reference
  • Communicate updates to stakeholders

Performance

  • Optimize slow queries
  • Use materialized views for complex reports
  • Cache results when appropriate

Stakeholder communication

Set expectations

  • Explain what the report shows and doesn't show
  • Define metric calculations clearly
  • Specify data freshness (real-time vs. daily)

Gather feedback

  • Ask if reports answer their questions
  • Adjust based on how they're used
  • Add new metrics as needs evolve

Educate users

  • Show stakeholders how to run reports themselves
  • Explain parameters and filters
  • Encourage self-service when possible

What's next?

Now that you can build and share reports, explore:

Was this page helpful?

Was this page helpful?