15 TemplatesCopy & Paste

Best Data Analysis Prompts for Gemini (2026)

Copy proven data analysis prompt templates optimized for Google Gemini. Each prompt helps you extract insights, create reports, and communicate findings effectively.

Why Gemini Works for Data Analysis

Google Gemini brings specific strengths to data analysis tasks that complement traditional BI tools and statistical software. Understanding these strengths helps you use Gemini effectively in your data workflow.

Pattern Recognition

Gemini excels at identifying patterns, trends, and anomalies in data that might not be immediately obvious from summary statistics alone.

Narrative Generation

Transform dry numbers into compelling narratives. Gemini writes executive summaries, chart annotations, and data stories that communicate effectively to stakeholders.

Structured Analysis

Complex analysis frameworks (cohort analysis, root cause investigation, hypothesis testing) benefit from Gemini's ability to follow multi-step processes consistently.

Documentation

Metric definitions, report templates, and dashboard specifications all require clear, structured documentation—an area where Gemini is particularly reliable.

Best Practice: Combine Gemini with data tools

Use SQL, Python, or your BI tool for precise calculations and data extraction. Use Gemini for interpretation, narrative, and hypothesis generation. For custom analysis prompts tailored to your data, try the Gemini prompt generator.

Top 15 Data Analysis Prompt Templates for Gemini (Copy & Paste)

Each template is ready to use—just paste your data and replace placeholder values. Click Copy to grab the prompt, then paste into Gemini along with your dataset.

CSV Data AnalysisData Analysis

Analyze structured data to extract patterns and insights.

Analyze this dataset and provide comprehensive insights.

Dataset

{paste your CSV data here - include headers and a representative sample}

Dataset Context

  • What this data represents: {description}
  • Time period: {date range}
  • Source: {where data comes from}
  • Known issues: {any data quality notes}

Analysis Request

1. Data Overview

  • Number of records (visible in sample)
  • Column descriptions and data types
  • Missing values or anomalies observed

2. Summary Statistics

For numerical columns:

ColumnMinMaxMeanMedianObservations

For categorical columns:

ColumnUnique ValuesTop 3 ValuesDistribution Notes

3. Pattern Analysis

Identify:

  • Trends: Direction and magnitude of changes over time
  • Correlations: Relationships between variables
  • Segments: Natural groupings in the data
  • Outliers: Unusual values with possible explanations

4. Key Insights

List 5-7 actionable insights:

#InsightEvidenceImplication

5. Data Quality Notes

Issues that affect analysis reliability:

  • Missing data patterns
  • Potential data entry errors
  • Sampling considerations

6. Recommended Next Steps

  • Additional analysis to perform
  • Questions to investigate
  • Data to collect
Insight Extraction & PrioritizationInsights

Extract and rank insights from analysis results.

Extract and prioritize actionable insights from this data/analysis.

Data/Analysis Results

{paste your data, charts, or analysis output}

Business Context

  • Decision to inform: {what decision this analysis supports}
  • Stakeholders: {who will use these insights}
  • Constraints: {budget, time, resources}
  • Success metrics: {how we measure good outcomes}

Insight Extraction

1. Raw Findings

List all observations from the data:

FindingData PointConfidence

2. Insight Development

Transform findings into insights:

FindingSo What?Now What?Impact

3. Insight Prioritization Matrix

Rank insights by impact and actionability:

InsightBusiness ImpactEase of ActionPriority Score
(Use scale 1-5 for each dimension)

4. Top 5 Insights (Detailed)

For each priority insight:

Insight 1: [Title]

  • What the data shows:
  • Why it matters:
  • Recommended action:
  • Expected outcome:
  • Risk if ignored:

{Repeat for insights 2-5}

5. Supporting vs. Contradicting Evidence

InsightSupporting DataContradicting DataNet Confidence

6. Quick Wins vs. Strategic Initiatives

Quick Wins (implement immediately):

Strategic Initiatives (require planning):

7. Insight Communication

How to present each insight to stakeholders:

InsightHeadlineKey VisualOne-line Summary
Anomaly Detection AnalysisQuality

Identify unusual patterns and outliers in data.

Analyze this data for anomalies and unusual patterns.

Data to Analyze

{paste your data}

Context

  • What's being measured: {metric/process}
  • Normal range: {expected values or historical benchmarks}
  • Time period: {when data was collected}
  • Known events: {anything that might explain anomalies}

Anomaly Analysis

1. Statistical Anomalies

Values outside expected ranges:

Data PointValueExpected RangeDeviationSeverity

2. Pattern Anomalies

Unusual sequences or behaviors:

PatternLocationDescriptionTypical PatternDifference

3. Temporal Anomalies

Time-based irregularities:

Time PeriodAnomalyComparison PeriodChange %

4. Anomaly Classification

AnomalyTypeLikely CauseInvestigation Needed
Data entry error
System issue
Genuine outlier
Process change
External factor

5. False Positive Assessment

Anomalies that might be explainable:

AnomalyPossible ExplanationProbability of Real Issue

6. Impact Analysis

AnomalyIf IgnoredIf False AlarmRecommended Action

7. Monitoring Recommendations

Rules to catch similar anomalies in future:

MetricThresholdAlert Condition
Executive Summary GeneratorReporting

Create C-level summaries from detailed analysis.

Create an executive summary of this data analysis for senior leadership.

Detailed Analysis/Data

{paste your analysis, findings, or data}

Executive Context

  • Audience: {CEO / CFO / Board / Department head}
  • Decision being made: {what this informs}
  • Time for review: {30 seconds / 2 minutes / 5 minutes}
  • Preferred format: {bullet points / narrative / visual}

Executive Summary

1. The Bottom Line (30 seconds)

One paragraph that answers: What should the executive know and do?

2. Key Metrics Dashboard

MetricCurrentPreviousChangeStatus
{Traffic light status: 🟢 🟡 🔴}

3. What's Working

Top 3 positive findings:

  1. [Finding] → [Business impact]
  2. [Finding] → [Business impact]
  3. [Finding] → [Business impact]

4. What Needs Attention

Top 3 concerns:

  1. [Issue] → [Risk if not addressed] → [Recommended action]
  2. [Issue] → [Risk if not addressed] → [Recommended action]
  3. [Issue] → [Risk if not addressed] → [Recommended action]

5. Recommendation

Primary recommendation:

  • Action:
  • Timeline:
  • Investment required:
  • Expected ROI:

Alternative options:

OptionProsConsInvestment

6. Next Steps

Immediate actions (next 7 days):

  • Action 1
  • Action 2
  • Action 3

7. Appendix Reference

Where to find supporting details:

  • Full analysis: [location]
  • Raw data: [location]
  • Methodology: [location]
Chart & Visualization NarrationVisualization

Write compelling narratives for data visualizations.

Write a narrative description and insights for this chart/visualization.

Chart Description

  • Chart type: {line / bar / pie / scatter / other}
  • X-axis: {what it represents}
  • Y-axis: {what it represents}
  • Data series: {what lines/bars represent}
  • Time period: {dates covered}

Chart Data

{paste the data shown in the chart or describe key data points}

Visualization Context

  • Where it will appear: {report / presentation / dashboard}
  • Audience: {who will see this}
  • Key message: {what should they take away}

Chart Narration

1. Chart Title Options (5)

Titles that communicate the key insight: 1. 2. 3. 4. 5.

2. One-Sentence Summary

The main takeaway in one clear sentence:

3. Narrative Description (100-150 words)

Full description of what the chart shows:

4. Key Data Points to Highlight

Data PointValueWhy It Matters

5. Trend Analysis

  • Overall direction: {up / down / stable / volatile}
  • Rate of change: {description}
  • Notable inflection points: {where trends changed}
  • Seasonality: {if applicable}

6. Annotation Suggestions

Location on ChartAnnotation TextPurpose

7. Comparison Context

How this compares to:

  • Previous period:
  • Industry benchmark:
  • Target/goal:

8. So What? Statement

What action should this chart prompt:

9. Caveats

Important limitations or context:

Metric Definition & DocumentationDocumentation

Define metrics with calculation logic and context.

Create comprehensive metric definitions and documentation.

Metrics to Define

{list the metrics you need documented}

Business Context

  • Domain: {e.g., marketing, sales, product, finance}
  • Use case: {how these metrics are used}
  • Audience: {who needs to understand them}

Metric Documentation

For Each Metric:


Metric Name: [Name]

Also known as: [Alternative names/abbreviations]

Definition: [Clear, unambiguous definition in plain language]

Calculation:

Formula: [Mathematical formula]
Example: [Worked example with numbers]

Data Sources:

SourceTable/FieldNotes

Dimensions:

DimensionDescriptionValues
TimeDaily/Weekly/Monthly
Segment
Product

Interpretation Guide:

  • Good: [value range and what it means]
  • Warning: [value range and what it means]
  • Critical: [value range and what it means]

Common Misinterpretations:

  • Pitfall 1: [what people get wrong]
  • Pitfall 2: [what people get wrong]

Related Metrics:

MetricRelationship

Update Frequency: [How often this metric is calculated]

Owner: [Team/person responsible]


{Repeat for each metric}

Metric Relationships

How these metrics connect: [Diagram or description of relationships]

Trend Analysis & ForecastingForecasting

Analyze trends and project future patterns.

Analyze trends in this data and provide forward-looking insights.

Historical Data

{paste time-series data}

Analysis Parameters

  • Time period covered: {dates}
  • Granularity: {daily / weekly / monthly / quarterly}
  • Metric being analyzed: {what we're measuring}
  • Known influencing factors: {events, seasonality, etc.}

Trend Analysis

1. Overall Trend Assessment

MetricDirectionStrengthConfidence

2. Trend Decomposition

Break down into components:

  • Long-term trend: {description}
  • Seasonal patterns: {description}
  • Cyclical patterns: {description}
  • Irregular variations: {description}

3. Rate of Change Analysis

PeriodGrowth RateAccelerationNotes

4. Inflection Points

When and why trends changed:

Date/PeriodWhat ChangedLikely CauseImpact

5. Seasonality Patterns

Season/PeriodTypical PatternMagnitudeConfidence

6. Leading Indicators

What predicts changes in this metric:

IndicatorLead TimeCorrelationCurrent Signal

7. Projection Scenarios

ScenarioAssumptionProjectionConfidence
Base case
Optimistic
Pessimistic

8. Risks to Projections

RiskProbabilityImpactMitigation

9. Monitoring Plan

What to watch going forward:

SignalThresholdAction if Triggered
Comparison & Benchmarking AnalysisComparison

Compare performance across segments, periods, or competitors.

Perform a comparison analysis across these groups/periods.

Comparison Data

{paste data for comparison}

Comparison Type

  • Comparing: {segments / time periods / competitors / products}
  • Metrics: {what measurements to compare}
  • Purpose: {what decision this informs}

Comparison Analysis

1. Overview Comparison Matrix

EntityMetric 1Metric 2Metric 3Overall

2. Performance Rankings

For each metric:

RankEntityValuevs Averagevs Best

3. Gap Analysis

Where are the biggest differences:

MetricLeaderLaggardGapGap %

4. Strengths & Weaknesses Matrix

EntityTop StrengthTop WeaknessNet Assessment

5. Statistical Significance

Are differences meaningful:

ComparisonDifferenceSignificant?Confidence

6. Contextual Factors

Factors that affect fair comparison:

EntityUnique FactorsHow It Affects Comparison

7. Best Practices Identified

What leaders do differently:

LeaderBest PracticeApplicable to Others?

8. Recommendations by Entity

EntityPriority ImprovementActionExpected Impact

9. Tracking Plan

How to monitor progress on gaps:

GapCurrentTargetTimelineCheck-in
Cohort AnalysisAnalysis

Analyze behavior and performance by cohort groups.

Perform a cohort analysis on this data.

Cohort Data

{paste your data with cohort identifiers}

Cohort Parameters

  • Cohort definition: {what defines a cohort - signup month, acquisition source, etc.}
  • Observation period: {how long we track each cohort}
  • Key metric: {what we're measuring - retention, revenue, engagement}
  • Cohorts to compare: {list specific cohorts}

Cohort Analysis

1. Cohort Summary Table

CohortSizeMetric at Month 1Month 3Month 6Month 12

2. Retention/Progression Curves

CohortM0M1M2M3M4M5M6
(show retention or metric value over time for each cohort)

3. Cohort Comparison

CohortBest PerformanceWorst PerformanceKey Difference

4. Trend Across Cohorts

Are newer cohorts performing better or worse than older ones?

Time PeriodCohort PerformanceTrend DirectionSignificance

5. Cohort Quality Indicators

Early signals that predict long-term performance:

IndicatorMeasured AtCorrelation with LTVCurrent Cohort Value

6. Cohort-Specific Insights

For each cohort, what's unique:

Cohort: [Name]

  • Defining characteristics:
  • Performance highlights:
  • Key differences from average:
  • Hypotheses for behavior:

7. Predictive Patterns

Based on early behavior, predict long-term outcomes:

CohortMonth 1 MetricPredicted Month 12Confidence

8. Actionable Insights

InsightApplicable CohortsRecommended Action
Root Cause AnalysisInvestigation

Investigate why metrics changed or targets were missed.

Perform root cause analysis on this metric change/problem.

The Problem

  • Metric affected: {metric name}
  • Expected value: {what it should have been}
  • Actual value: {what it was}
  • Variance: {difference / percentage}
  • Time period: {when this occurred}

Available Data

{paste relevant data for investigation}

Root Cause Analysis

1. Problem Statement

Clear description of what went wrong:

2. Timeline of Events

Date/TimeEventMetric Impact

3. Decomposition Analysis

Break down the metric into components:

ComponentExpectedActualVarianceContribution to Problem

4. Hypothesis Generation

Possible causes ranked by likelihood:

#HypothesisEvidence ForEvidence AgainstLikelihood

5. 5 Whys Analysis

For top hypothesis:

  1. Why did [problem] happen? → [Answer 1]
  2. Why did [Answer 1] happen? → [Answer 2]
  3. Why did [Answer 2] happen? → [Answer 3]
  4. Why did [Answer 3] happen? → [Answer 4]
  5. Why did [Answer 4] happen? → [Root Cause]

6. Fishbone Diagram Categories

Categorize contributing factors:

CategoryContributing Factors
People
Process
Technology
Data
External

7. Root Cause Confirmation

Root CauseConfirming EvidenceConfidence Level

8. Impact Assessment

Root CauseDirect ImpactIndirect ImpactTotal Impact

9. Remediation Plan

Root CauseShort-term FixLong-term FixOwnerTimeline

10. Prevention Measures

How to prevent recurrence:

MeasureTypeImplementation EffortPriority
Data Quality AssessmentQuality

Assess data quality and identify issues.

Assess the quality of this dataset and identify issues.

Dataset to Assess

{paste sample data or data profile}

Data Context

  • Source system: {where data comes from}
  • Expected records: {how many should there be}
  • Critical fields: {most important columns}
  • Update frequency: {how often data refreshes}

Data Quality Assessment

1. Completeness Check

ColumnRecordsNon-NullNullCompleteness %Acceptable?

2. Accuracy Check

ColumnValid ValuesInvalid ValuesAccuracy %Examples of Invalid

3. Consistency Check

RuleDescriptionPassingFailingExamples of Failures

4. Timeliness Check

MetricExpectedActualStatus
Data freshness
Processing lag
Update gaps

5. Uniqueness Check

Key Column(s)Total RecordsUniqueDuplicatesDuplicate %

6. Data Quality Score

DimensionWeightScore (1-100)Weighted Score
Completeness
Accuracy
Consistency
Timeliness
Uniqueness
Overall100%

7. Critical Issues

IssueSeverityAffected RecordsBusiness Impact

8. Remediation Priority

IssueFix ComplexityBusiness ValuePriority Rank

9. Recommendations

CategoryRecommendationOwnerTimeline
Immediate fixes
Process changes
Monitoring
Automated Report TemplateReporting

Create repeatable report structure with data placeholders.

Create a repeatable report template for this type of analysis.

Report Requirements

  • Report name: {what this report is called}
  • Frequency: {daily / weekly / monthly / quarterly}
  • Audience: {who reads this report}
  • Purpose: {what decisions it informs}
  • Key metrics: {list the metrics to include}

Report Template

1. Report Header

Report Title: [Name] Report — [Period] Generated: [Date/Time] Author: [Name/System] Distribution: [Recipients]

2. Executive Summary Section

[2-3 sentences summarizing the period's performance]

Key Numbers:

MetricThis PeriodPrevious PeriodChangeStatus
[Metric 1]{value}{value}{%}🟢/🟡/🔴
[Metric 2]{value}{value}{%}🟢/🟡/🔴
[Metric 3]{value}{value}{%}🟢/🟡/🔴

3. Performance Detail Sections

Section: [Area 1]

  • Metric 1: {value} ({context})
  • Metric 2: {value} ({context})
  • Key insight: {observation}
  • Action needed: {if any}

Section: [Area 2]

  • Metric 1: {value} ({context})
  • Metric 2: {value} ({context})
  • Key insight: {observation}
  • Action needed: {if any}

4. Trend Charts

[Placeholder for Chart 1: Description] [Placeholder for Chart 2: Description]

5. Highlights & Lowlights

What went well:

  • {Highlight 1}
  • {Highlight 2}

What needs attention:

  • {Issue 1}
  • {Issue 2}

6. Actions & Follow-ups

ActionOwnerDue DateStatus

7. Appendix

  • Data sources
  • Methodology notes
  • Glossary of terms

Report Automation Notes

ElementData SourceCalculationRefresh
[Metric 1]
[Metric 2]
Hypothesis Testing FrameworkAnalysis

Structure data analysis as hypothesis tests.

Structure a hypothesis test for this business question.

Business Question

{state the question you're trying to answer with data}

Available Data

{describe or paste the data you have}

Hypothesis Framework

1. Hypothesis Formulation

Null Hypothesis (H0): {The default assumption - what we'd believe without evidence}

Alternative Hypothesis (H1): {What we're testing for - the effect we suspect exists}

One-tailed or Two-tailed: {Direction of test and why}

2. Variables

VariableTypeMeasurementRole
Independent/DependentScale/UnitTreatment/Outcome

3. Test Selection

Recommended test: {test name} Justification: {why this test fits} Assumptions: {what must be true for test to be valid}

4. Sample Analysis

GroupSample SizeMeanStd DevNotes

5. Test Execution

Test statistic: {calculated value} P-value: {result} Confidence level: {95% / 99%} Effect size: {measure}

6. Results Interpretation

OutcomeMeaningConfidence
If p < 0.05
If p >= 0.05

7. Practical Significance

Beyond statistical significance:

  • Effect size interpretation:
  • Business impact:
  • Confidence in real-world application:

8. Limitations & Caveats

LimitationImpact on ConclusionsMitigation

9. Recommendations

Based on results:

  • If hypothesis supported:
  • If hypothesis not supported:
  • Regardless of outcome:

10. Follow-up Questions

What additional analysis would strengthen conclusions:

Dashboard Design SpecificationVisualization

Design data dashboards with metrics and visualizations.

Design a dashboard for this use case.

Dashboard Purpose

  • Name: {dashboard name}
  • Primary user: {role/team}
  • Key decisions supported: {what users will decide based on this}
  • Refresh frequency: {how often data updates}
  • Access level: {who can view}

Dashboard Design

1. Key Performance Indicators (Top-level)

KPIDefinitionTargetVisualizationPosition
Number cardTop left
Number cardTop center
Number cardTop right

2. Main Visualizations

Chart #TypeData ShownInsight It ProvidesPosition
1
2
3
4

3. Filters & Controls

FilterTypeDefault ValueAffects
Date rangeDropdownLast 30 daysAll charts

4. Drill-down Capabilities

ChartDrill IntoShows

5. Layout Wireframe

+------------------+------------------+------------------+
|     KPI 1        |     KPI 2        |     KPI 3        |
+------------------+------------------+------------------+
|                                                        |
|                    Chart 1 (wide)                      |
|                                                        |
+---------------------------+----------------------------+
|                           |                            |
|     Chart 2               |     Chart 3                |
|                           |                            |
+---------------------------+----------------------------+
|                                                        |
|                    Chart 4 / Table                     |
|                                                        |
+-------------------------------------------------------+

6. Data Requirements

Metric/FieldSource TableCalculationRefresh

7. Alert Conditions

MetricConditionAlert TypeRecipients

8. User Interaction Flows

User ActionExpected ResultNavigation

9. Mobile Considerations

Priority metrics for mobile view: 1. 2. 3.

Survey Results AnalysisResearch

Analyze and summarize survey response data.

Analyze these survey results and provide actionable insights.

Survey Data

{paste survey results or summary}

Survey Context

  • Survey purpose: {why this survey was conducted}
  • Target population: {who was surveyed}
  • Sample size: {number of responses}
  • Response rate: {if known}
  • Collection period: {when}

Survey Analysis

1. Response Overview

MetricValue
Total responses
Complete responses
Partial responses
Response rate
Confidence level

2. Demographic Breakdown

SegmentCount% of TotalNotes

3. Question-by-Question Analysis

Question: [Question text]

Response OptionCountPercentageInsight

Key finding:

{Repeat for each question}

4. Cross-tabulation Insights

SegmentQuestionNotable DifferenceSignificance

5. Open-Ended Response Themes

ThemeFrequencyExample QuotesSentiment

6. Key Findings Summary

#FindingData SupportImplications
1
2
3

7. Sentiment Analysis

TopicPositiveNeutralNegativeNet Score

8. Recommendations

PriorityRecommendationBased OnExpected Impact

9. Limitations

LimitationImpact on FindingsMitigation

10. Follow-up Research

Questions raised that need further investigation:

How to Customize These Prompts

These templates work best when you provide clean data and specific context about what decisions the analysis should inform. Here's how to get the best results:

1. Format Your Data Clearly

Use CSV format with headers, or markdown tables for smaller datasets. For large datasets, paste a representative sample (50-100 rows) plus summary statistics.

2. Provide Business Context

“Analyze this data” produces generic output. “Analyze this sales data to help decide whether to expand into the enterprise segment” focuses the analysis on actionable insights.

3. Include Benchmarks

When available, include targets, historical averages, or industry benchmarks. This helps Gemini assess whether values are good, bad, or unusual.

4. Verify Critical Numbers

Use Gemini for interpretation and narrative, but verify exact calculations (averages, percentages, statistical tests) with code or spreadsheets for important decisions.

Frequently Asked Questions

Can Gemini actually analyze data files like CSV?

Gemini can analyze data when you paste it into the prompt. For small datasets (a few hundred rows), paste the data directly. For larger datasets, paste a representative sample or summary statistics. Gemini is excellent at interpreting data and finding patterns, but the analysis happens on the data you provide in the prompt.

What's the best format to paste data into Gemini?

CSV format works well—paste rows with comma separation. For small tables, markdown tables are clearer. For larger datasets, paste the first 50-100 rows as a sample plus any summary statistics. Always include column headers so Gemini understands the data structure.

How accurate is Gemini for data analysis compared to code?

Gemini is excellent for pattern recognition, generating hypotheses, and creating narratives around data. For precise calculations (exact averages, standard deviations), verify with code or spreadsheets. Use Gemini for interpretation and insight generation, not as a calculator for critical numbers.

Can Gemini create visualizations from data?

Gemini can't create actual charts, but it can recommend visualization types, write chart titles and annotations, create data narratives for charts, and even generate code to create visualizations in Python/matplotlib or JavaScript/D3. Use these prompts to get the analysis and narrative, then visualize separately.

What's the best way to get actionable insights from data?

Provide context about what decisions the analysis should inform. 'Analyze this sales data' produces generic output. 'Analyze this sales data to help decide which product lines to prioritize for Q2' focuses the analysis on actionable recommendations.

How do I use Gemini for anomaly detection?

Provide the data with context about what 'normal' looks like. Include historical benchmarks, expected ranges, or comparison periods. Ask Gemini to identify values that fall outside expected patterns and explain why they might be anomalous. Always verify flagged anomalies with domain knowledge.

Can Gemini help me build dashboards?

Gemini can help design dashboards by recommending metrics to include, suggesting visualizations for each metric, writing metric definitions, and creating the narrative structure. It can also write code for dashboard components in frameworks like Streamlit, Dash, or React charting libraries.

How do I get Gemini to explain data to non-technical stakeholders?

Specify your audience in the prompt: 'Explain these findings for a marketing executive who doesn't have a technical background.' Ask for analogies, avoid jargon, and request the 'so what'—why should they care about each finding? The executive summary prompt in this collection is designed for this use case.

Need a Custom Data Analysis Prompt?

Our Gemini prompt generator creates tailored prompts for your specific datasets, metrics, and analysis requirements.

25 assistant requests/month. No credit card required.