Back to cookbook

AI Prompt to Find Correlations and Trends Across Multiple Metrics in a Dataset

0 views Updated

Make this prompt yours

Share

This prompt is for analysts, marketers, and founders who need to find correlations and trends across multiple metrics in a dataset without writing statistical code themselves. It works well on spreadsheets or CSV exports that track several numeric columns over time, such as marketing spend, conversion rate, and revenue.

The prompt asks the model to identify which metrics move together, flag relationships worth investigating further, and explain findings in plain language rather than just reporting correlation coefficients. It also pushes the model to distinguish correlation from causation, since a model analyzing a small dataset can easily overstate how strong a relationship really is.

Because this kind of analysis is only as reliable as the data behind it, the prompt also asks the model to call out missing values or inconsistent formatting that could skew its findings, rather than silently working around them.

Prompt template

Make this prompt yours

prompt-template
232 tokens
Role: You are a data analyst who specializes in identifying patterns across business metrics. Context: - Dataset: [PASTE_DATA_OR_DESCRIBE_COLUMNS] - Metrics to analyze: [LIST_OF_METRIC_COLUMNS] - Time period covered: [TIME_PERIOD] - Business context: [BRIEF_DESCRIPTION_OF_WHAT_THESE_METRICS_MEASURE] Task: Analyze the relationships between the listed metrics and identify: 1. Which pairs of metrics show a notable positive or negative relationship 2. The approximate strength of each relationship (strong, moderate, weak) 3. A plain-language explanation of what the relationship might mean in this business context 4. Any relationship that looks correlated but is more likely coincidental or explained by a third factor Constraints: - Clearly label every finding as correlation, not causation, unless a controlled comparison is explicitly provided - Do not report relationships based on fewer than [MINIMUM_DATA_POINTS] data points - Flag any missing or inconsistent data that could affect the reliability of a finding Output format: A summary paragraph followed by a numbered list of relationships, each with strength, explanation, and a caution note where relevant.

Want it sharper? Optimize this prompt with Prompt Optimizer, check it with the Prompt Debugger or shorten it with the Token Optimizer.

Example input

example-input
75 tokens
Dataset: Weekly marketing spend, website visitors, email signups, and revenue for 12 weeks Metrics to analyze: marketing_spend, website_visitors, email_signups, revenue Time period: Jan 1 - Mar 23, 2026 (weekly) Business context: A direct-to-consumer brand tracking whether marketing spend translates into downstream signups and revenue

When to use it

  • You have a dataset with several numeric columns and want to know which ones move together before building a dashboard.
  • You're reviewing monthly or weekly performance metrics and want a plain-language summary of relationships, not just a correlation matrix.
  • You want a first pass at identifying what to investigate further before running formal statistical tests.
  • You're preparing a findings summary for stakeholders who won't read a raw statistics output.

Best practices

  • Paste the raw data, or a representative sample, rather than just describing it, so the model references actual values.
  • Ask explicitly for the model to flag correlation versus causation so findings aren't overstated.
  • Request a confidence or strength rating for each relationship so you can prioritize which ones to investigate further.
  • Break very large datasets into manageable chunks by date range or category rather than pasting everything at once.

Common mistakes

  • Treating every correlation the model reports as a causal relationship without further investigation.
  • Pasting in a dataset with inconsistent formatting, like mixed date formats or missing values, and expecting accurate correlations.
  • Asking for correlations across too many metrics at once, which produces a wall of weak, low-value pairings.
  • Not specifying the time period or data granularity, leading to correlations calculated across incompatible date ranges.

FAQs

How do I know if a correlation in my data is meaningful or just noise?

Look for a consistent pattern across many data points rather than one or two coincidental spikes, and be especially cautious with small datasets under 20-30 points, where random variation can look like a real relationship.

Can ChatGPT or Claude actually calculate correlation coefficients accurately?

A model can reason about directional relationships and estimate rough strength, but for precise statistical values it's safer to calculate correlation coefficients with a spreadsheet function or statistics library and have the model interpret those exact numbers.

What's the difference between correlation and causation in this kind of analysis?

Correlation means two metrics move together; causation means one metric's change directly produces the other's change. A model analyzing a dataset can confirm correlation but generally can't confirm causation without controlled testing or domain knowledge ruling out other explanations.

Which Cuelara tool helps if my dataset is too large to paste into this prompt?

Context Extractor — pulls just the relevant rows and columns from large spreadsheets or CSVs so the model works with focused data instead of a truncated or oversized paste.

Found this prompt useful? Share it.

Share

More in Data Analysis

Data Analysis

AI Prompt to Standardize Inconsistent Date Formats Across a Dataset

This AI prompt for standardizing date formats helps analysts, ops teams, and anyone who inherits spreadsheets from multiple sources turn a c…

ROLE: You are a meticulous data cleaning assistant specializing in date normalization.

CONTEXT:
I have a dataset with a column of dates in inconsistent formats. The source systems use these locale conventions: [LIST SOURCE FORMATS, e.g., US month/day/year from System A, European day/month/year from System B]. Here is the raw data:
[PASTE DATE VALUES OR ROWS HERE]

TASK:
1. Identify the format of each date value.
2. Convert every date to this exact target format: [TARGET FORMAT, e.g., YYYY-MM-DD].
3. For any date you cannot confidently parse (ambiguous day/month, missing year, invalid date, etc.), do NOT guess — list it separately under "Needs manual review" with a note on why it's ambiguous.

CONSTRAINTS:
- Do not alter values that are already in the target format.
- Treat two-digit years as [YOUR RULE, e.g., 20XX unless clearly 19XX].
- Preserve the original row order.

OUTPUT FORMAT:
Return a table with three columns: Original Value | Converted Value | Status (Converted / Needs manual review). After the table, list the total count of each status.

Make this prompt yours

Data Analysis

AI Prompt to Merge and Reconcile Two Datasets With Mismatched Columns

This AI prompt is for anyone who needs to merge two datasets that don't line up cleanly — different column names, inconsistent formatting, o…

You are a data integration specialist merging two datasets that use inconsistent structures.

Context:
- Dataset A description: [WHAT DATASET A CONTAINS AND ITS SOURCE]
- Dataset A columns: [LIST COLUMN NAMES]
- Dataset B description: [WHAT DATASET B CONTAINS AND ITS SOURCE]
- Dataset B columns: [LIST COLUMN NAMES]
- Field(s) that should uniquely identify a matching record: [E.G. EMAIL, CUSTOMER ID, OR NAME + DATE OF BIRTH]
- Dataset A sample: [PASTE DATA HERE]
- Dataset B sample: [PASTE DATA HERE]

Task:
1. Propose a column mapping between dataset A and dataset B, noting any column in either dataset with no clear equivalent in the other.
2. Normalize formatting differences (dates, currency, capitalization, abbreviations) so matching fields can be compared fairly.
3. Match records between the two datasets using the specified key, and merge matched records into a single row per entity.
4. List any records that could not be confidently matched, along with the reason (missing key, near-duplicate, conflicting data).
5. Flag any records where the same key appears to have conflicting values across the two datasets.

Constraints:
- Do not force a match when the key fields don't align; list it as unmatched instead
- Preserve all original column data in the merged output rather than dropping fields that don't map directly
- [ADD ANY DOMAIN-SPECIFIC RULES, E.G. "TREAT 'INC' AND 'INCORPORATED' AS THE SAME COMPANY SUFFIX"]

Output format:
- A proposed column mapping table (Dataset A column, Dataset B column, Notes)
- A merged table of matched records
- A separate list of unmatched or conflicting records with the reason for each

Make this prompt yours

Data Analysis

AI Prompt to Audit a Notion Database for Data Quality Issues via Notion's MCP Server

This Notion MCP prompt is for operations, data, and RevOps teams who keep a working database in Notion (a CRM tracker, inventory log, projec…

You are a data quality analyst reviewing a live database retrieved via an MCP connection to Notion.

Context:
- Database name: [DATABASE_NAME]
- Approximate number of records: [RECORD_COUNT]
- Required properties that must always be filled in: [REQUIRED_PROPERTIES]
- Properties with a fixed set of intended values (e.g. Status should only be one of a known list): [CONTROLLED_PROPERTIES_AND_VALUES]

Task:
Retrieve the records in this database and check them for the following issues:
1. Missing values in required properties
2. Duplicate records (same entity represented more than once)
3. Inconsistent formatting or casing in controlled properties
4. Broken or empty relation fields
5. Date fields that are empty, in the past when they shouldn't be, or otherwise clearly incorrect

Constraints:
- Only flag issues you can verify from the retrieved data; do not guess at values you cannot see
- Group findings by issue type, then by severity (Blocking, Needs Review, Cosmetic)
- Include the page title or unique identifier for every flagged record so it can be located in Notion

Output format:
Return a structured report with one section per issue type. Each section should list affected records as a short table: [Record Name | Issue Description | Suggested Fix]. End with a one-paragraph summary of total issues found and the top priority to address first.

Make this prompt yours