Skip to main content
Use Raw Data Export when you need to move from dashboard trends to precise, joinable event rows—enabling custom pivots, cohort retention, feature adoption deep-dives, and external BI modeling.

What You Can Answer

Which users & post types drove yesterday’s reaction surge?

Export Workflow

1

Select Date Range

Adjust widget timeframe (e.g., last 7 / 30 days). Smaller ranges export faster & reduce row truncation risk.
2

Open Widget Menu

In the target widget header (Daily Engagements, Post Types, Reach & Impressions) click the Download icon.
3

Confirm Email

Pre-filled from your account; update if you need to CC an alias that’s allowed.
4

Generate Snapshot

Click Generate to queue export—toast confirmation appears.
5

Retrieve Email Links

Email contains signed URLs for each CSV; links valid 24h.
6

Archive & Version

Store files with a date-stamped naming convention (e.g., posts_2025-08-17.csv).
7

Join & Analyze

Combine on shared keys (postId, user IDs, targetId) in your BI / spreadsheet tool.

Available Files

All files capped at 10,000 rows. Split large periods or narrow filters (community, post type) when approaching limit.

Column Reference

Common Core Fields

File Specific Highlights

Includes postText, postType, tag arrays, and deletion flags for content mining & classification.
Contains parentCommentId enabling thread reconstruction & depth analysis.
Lightweight engagement events; join to posts for reaction intensity per post type.
One row per post with full creator, timing, and type metadata for mix / composition trends.
Each row = post + day; reflects distinct viewer exposure irrespective of creation date.
Frequency dimension per post + day; compare with reach to compute repetition (Impressions/Reach).

Data Freshness & Snapshot Semantics

Governance & Limits

For larger ongoing pipelines plan migration to forthcoming API / warehouse sync instead of stitching multiple manual exports.

Joining & Derived Metrics

Troubleshooting

Best Practices

Export smallest viable slice; expand gradually to avoid hitting limits.
Use ISO date naming; store in a controlled folder for reproducibility.
Create small dimension tables (user roles, community metadata) and join post-import.
Prototype insights manually before investing in pipeline automation.
Use impressions.csv to build decay curves for evergreen content strategy.

FAQ

Can I exceed 10k rows? Not currently—split range or await API export. Are private communities included? Yes, if your role grants visibility. Scheduled exports? On roadmap—use calendar reminder interim. Historical text versions? Not stored—only latest edit at generation time.