Loading tutorials…
Loading tutorials…
Claude can analyze CSVs, run statistical reasoning, and write the explanation in plain English. For marketers without a data analyst, this is the closest thing to having one on-call.
Who this is forMarketers and operators who need to analyze data (campaigns, customers, behavior, financials) without learning Python or hiring a data analyst.
What you'll need
Step 1
CSV or Excel. Clean headers, no merged cells, one row per record. Garbage in = garbage out.
Open your data in Google Sheets or Excel.
Headers: clean, descriptive, no spaces or special chars. "customer_email" not "Customer Email (verified)."
No merged cells. Each row = one record, each column = one field.
Remove sensitive PII if possible: anonymize email IDs, mask phone numbers.
Export as CSV (preferred for clean parsing) or Excel.
File should be under 30MB for Claude to handle efficiently.
Step 2
New Claude chat → upload file via paperclip → Claude confirms columns + sample rows.
Open a new Claude chat. Click the paperclip icon to upload the file.
Claude processes the file and confirms: "I have analyzed the file. It has X rows, Y columns. Columns are: [list]. Here are 3 sample rows: [shows]."
Verify the parsing: column names correct? Data types right (numbers as numbers, dates as dates)?
If parsing is wrong: tell Claude. "Re-parse the date column as datetime. It is currently being read as string."
Step 3
Specific questions get specific answers. Start with what you actually want to know.
Example for ad spend data: "What is the average CPA by campaign? Identify the top 3 most efficient campaigns and the top 3 least efficient by CPA. Cite specific numbers."
Example for customer data: "What is the LTV distribution? What percent of customers drive 80% of revenue? Cite specific numbers and customer IDs."
Example for behavior data: "Group sessions by traffic source. Average session duration by source. Identify sources with abnormally short sessions or high bounce rates."
Claude reasons through the data and produces written analysis.
Verify the answer: do the numbers match your spot-checks of the source data?
Step 4
Claude can generate SVG charts or Mermaid diagrams via Artifacts. Visual analysis catches patterns text misses.
After getting a text answer, prompt: "Generate an SVG bar chart of the top 10 campaigns by CPA, sorted ascending."
Claude generates an Artifact with the chart.
For time-series: "Generate a line chart of monthly revenue over the last 12 months. Highlight the highest and lowest months."
For distributions: "Generate a histogram of customer LTV. Show median + 90th percentile."
Export: download the SVG from the Artifact panel. Embed in reports or share via screenshot.
Step 5
Claude is strong at narrative analysis — describe what is happening over time and why.
For cohort analysis: "Split customers into cohorts by signup month. For each cohort, calculate average revenue per customer at 30/60/90 days. Is retention improving or declining over cohorts?"
Claude analyzes and writes narrative + numbers.
For trend analysis: "Looking at the last 12 months, identify the top 3 trends in [metric]. For each: describe the trend, quantify it, suggest the most likely cause based on the data."
Narrative analysis is where Claude shines vs ChatGPT — output reads like an analyst wrote it.
Step 6
AI analysis can be wrong in non-obvious ways. Always validate against what you know.
For every finding, ask: "Does this match what I already know about the business?"
If Claude says "Campaign X has highest ROAS" but you know Campaign X had a tracking issue last month, the analysis is wrong.
Validation tactics: cross-check 1-2 numbers manually in source data. Compare against last period's known values. Run the same analysis in a different tool (Excel, Looker) and compare.
AI analysis is a starting point, not the final answer. Validate before acting on findings.
Step 7
Ask Claude to format the analysis as a shareable report. Markdown for Notion, plain text for Slack.
After analysis is complete: "Summarize the top 5 findings as a shareable report. Format: executive summary (3-5 sentences) → key findings (5 numbered, with numbers) → recommended actions (3-5). Markdown format."
Claude formats the output. Copy to Notion/Google Docs.
For team sharing: "Format as a Slack message. 3-5 bullet findings with key numbers. Under 500 chars."
Reuse the chat as audit trail — anyone questioning the analysis can see prompts and responses.
Common mistakes
Trying to analyze huge datasets in Claude
What goes wrong: You upload a 50K-row CSV. Claude struggles to reason about it (no Python execution). Output is incomplete or hallucinated.
How to avoid: For datasets over 10K rows, use ChatGPT Code Interpreter instead. Claude is best for narrative analysis on smaller datasets (under 10K rows).
Vague questions
What goes wrong: 'Analyze my data' returns generic averages that tell you nothing useful. Output is correct but not actionable.
How to avoid: Ask specific, actionable questions. "Which campaign has highest CPA?" "Top 10 customers by LTV?" Specific questions = specific answers.
Not validating findings
What goes wrong: Claude confidently produces wrong analyses (hallucinated patterns, math errors on edge cases). You make decisions on faulty data. Real money lost.
How to avoid: Validate every meaningful finding. Cross-check numbers in source data. If critical, run analysis in Excel/Looker as second source.
Asking for charts on irrelevant data
What goes wrong: Pretty charts of meaningless metrics. Look impressive in reports but do not drive decisions.
How to avoid: Only chart what is actionable. Does the chart change a decision? If no, skip the chart.
No documentation of the analysis methodology
What goes wrong: Someone questions the finding in a meeting. You cannot remember which prompts produced which numbers. Lose credibility.
How to avoid: Save the Claude chat as the audit trail. Note: "Analysis run on [date] using [data file]. See full chat at [link]." Reproducibility builds trust.
Recap
Done — what's next
How to use Claude for research synthesis
Read the next tutorial
Hand it off
Data analysis with Claude is fast but requires validation skill. A content creator who knows analytics will run analyses and translate findings into actionable insights. From $14-16/hr — most ongoing analysis engagements land at $400-1,200/mo.
See specialist rates
ChatGPT for computational analysis (Code Interpreter runs Python on large datasets). Claude for narrative analysis (better written summaries, deeper reasoning on patterns). Many marketers use both — ChatGPT for crunching numbers, Claude for explaining.
CSV, Excel (.xlsx), PDF (text extraction), plain text, JSON. For images and charts: limited — Claude can describe what it sees but cannot extract data from images precisely.
The narrative reasoning is accurate when the data is clean and the question is specific. Hallucinations can happen on edge cases or with messy data. Always validate critical findings against source data.
Pro plan: may train on data by default (opt-out in settings). Team and Enterprise: training off by default. For PII analysis, use Team or Enterprise. Or anonymize the data before upload.
Note: 'Analysis performed using Claude Sonnet 4.7 on [date] with [data source]. Methodology validated against [source spot-checks].' Transparency about AI use builds trust with leadership and auditors.
Claude for Marketing
Claude's 200K-token context window is the killer feature for research. Paste 20 customer interviews and ask for themes. Paste 10 competitor pieces and ask for gaps. The synthesis quality is unmatched.
Claude for Marketing
Claude Projects are how you stop re-explaining your brand voice every conversation. Set up once, every chat in the project starts with full context. The leverage move for serious Claude users.
ChatGPT for Marketing
ChatGPT Code Interpreter (Advanced Data Analysis) can analyze 50-row spreadsheets or 50,000-row exports. Plus browsing makes it a competitive research engine. This is the workflow.
Claude for Marketing
Claude Code is the terminal-based agent that writes + runs code on your behalf. For marketers comfortable with light technical work, it is the closest thing to a junior developer on-call.