What a raw data export contains
A raw data export gives you records instead of totals. A typical install export has one row per attributed install with fields like install time, platform, network, campaign, ad set, creative, country, and whether the install was organic, paid or re-attributed. An event export has one row per in-app event with the event name, time, user and revenue.
A worked example of why rows matter: the dashboard says a campaign drove 3,000 installs. Your finance team wants to know how many of those users placed an order above $20 within 14 days. Only row-level data joined with your order table can answer that, because the dashboard does not know your order values.
Export methods
- CSV exports. A file for a date range, built on request. Simple and good for one-off analysis.
- Cloud and warehouse delivery. Scheduled files or tables in BigQuery, Redshift or Snowflake. Best for teams with a data stack.
- Pull APIs. Query attributed users or reports on demand from your own code.
- Webhooks. Each new install or sign-up is pushed to your server in near real time.
Most teams combine two: a warehouse feed for analysis and webhooks for real-time workflows like CRM updates.
Common uses
- Joining attribution with revenue, orders or credit data in your own warehouse.
- Building custom LTV and payback models by campaign.
- Feeding BI dashboards that combine marketing and product data.
- Auditing ad network invoices and fraud disputes.
- Building audiences to upload to ad platforms.
Raw data in Linkrunner
Linkrunner's CSV exports cover campaigns and users. Self-serve exports cover up to 3 calendar months per request (custom ranges on request) and arrive by email as an attachment, zipped above 10 MB, or as a 72-hour download link when the zipped file is over 25 MB. Webhooks push install and sign-up events with attribution data, the Data APIs return attributed users and attribution lookups, and warehouse delivery to BigQuery, Redshift or Snowflake is available on request. See APIs and webhooks.