Export the evidence without losing the meaning.
Advanced Subscriber Intelligence treats export as part of the reporting chain, not a button that throws raw rows into a spreadsheet and leaves the operator to reconstruct the story.
Campaign, Event Stream, Recipient Drilldown, link, bounce, subscriber, provider, and human-confidence evidence can be scoped before export so the resulting files reflect the same question reviewed inside Reports Builder.
The file format may change. The reporting truth should not. ASI keeps SQL-owned evidence, selected filters, reason context, and recipient fields aligned so exported data remains useful after it leaves the platform.
Scoped Before Export
Reason Evidence Included
Client-Controlled Data
An export should answer the same question as the report that created it.
If an operator selects one campaign, one link, one confidence threshold, one recipient scope, and a specific set of columns, the exported file should preserve that scope instead of quietly returning a broader or independently recalculated dataset.
Why ordinary exports create work instead of removing it
A raw database dump may contain rows. It rarely contains a usable explanation.
Scope disappears
The exported file may not show which filters, confidence level, campaign, link, audience, or date range created it.
Columns lose meaning
Fields such as delivered, clicked, human, bounced, held, or suppressed can become misleading when the calculation and reason evidence are absent.
Automated activity travels as engagement
Scanner and bot clicks can appear beside genuine recipient activity with no warning that the signals mean different things.
Spreadsheet surgery begins
Teams spend hours deduplicating rows, renaming columns, rebuilding context, and trying to decide which parts of the file can be trusted.
Reports Builder defines the data. The export carries it.
Advanced Data Exports remains downstream of the protected reporting rails. It does not create a parallel interpretation of campaign or recipient evidence.
SQL Core truth
Subscriber, campaign, consent, suppression, queue, sending, event, bounce, and evidence state remain authoritative in SQL.
Reports Builder scope
The selected campaign, audience, events, confidence, time, link, recipient columns, and output sections define the reporting contract.
Event Stream evidence
Event rows preserve activity type, time, recipient, link, domain, device, confidence, bounce, provider, and reason evidence.
Recipient Drilldown context
Recipient-level exports can carry the identity and campaign context required for review without creating a new subscriber truth outside Core.
Different evidence for different operational questions.
ASI allows the operator to choose the evidence required for the task rather than exporting the whole platform because one spreadsheet is needed.
Campaign evidence
Export selected campaign totals, queue states, accepted transport evidence, delivered estimates, engagement, bounces, complaints, unsubscribes, links, and provider outcomes.
Event Stream rows
Export scoped open, click, bounce, unsubscribe, complaint, provider, and other event evidence with the requested filters and context.
Recipient Drilldown
Export recipients matching the selected campaign, behaviour, confidence, link, event, provider, or other permitted reporting scope.
Link evidence
Export all tracked links or one specific link with recipients, timestamps, confidence, device, domain, reason evidence, and campaign context.
Human-confidence evidence
Filter by the continuous 0% to 92% confidence score or an operational threshold while retaining reason codes and relevant event context.
Bounce and rejection evidence
Export SMTP code, diagnostic, bounce class, campaign, queue, message, subscriber, provider, source, and available raw response context.
Subscriber and audience data
Export selected identity, list membership, validation, suppression, jurisdiction, consent, source, and status fields where the operator has permission and a legitimate operational need.
Compliance and audit evidence
Export the relevant approval, suppression, recipient-exit, complaint, campaign, or operational evidence required for review without exporting unrelated data by default.
Useful context without exporting the kitchen sink.
ASI can include selected identity and business fields alongside the evidence required for the report, follow-up list, audit review, or handover.
Identity fields
Name, email, canonical subscriber identifier, campaign identifier, list or audience, batch, and row context can support traceability.
Commercial fields
Company, title, phone, website, LinkedIn, and other permitted fields can support sales or account follow-up where the source data contains them.
Evidence fields
Event time, link, confidence, reason, device, browser, provider, SMTP response, bounce class, complaint, unsubscribe, and related activity can explain why the row exists.
Scope fields
Campaign, report mode, confidence threshold, selected link, time range, audience scope, and export creation context help preserve the meaning of the file.
The export should contain enough context to remain useful, but not unrelated personal or operational data merely because the database happens to hold it.
Large exports should arrive as organised evidence, not one exhausted spreadsheet.
ASI can package selected Event Stream and recipient evidence into branded ZIP outputs with bounded file sizes so the data remains easier to open, review, share, and archive.
Bounded row packages
Operators can use selected package sizes such as 25, 50, or 100 rows per file where that format suits the review or handover workflow.
Consistent headers
Each file keeps the selected columns and ordering so recipients, events, campaign context, and evidence can be compared without manual restructuring.
Batch and row traceability
Batch, package, and row context helps reviewers understand where each exported record sits within the wider scoped result.
Cleaner client handover
Branded packaging gives agencies and internal teams a controlled output that can be handed over without presenting an anonymous database dump.
Different export modes should remain clearly labelled.
A raw click file and an 86% human-confidence follow-up list answer different questions. ASI should never allow those outputs to be confused merely because both contain email addresses and links.
Preserve everything recorded
Useful for forensic review, scanner analysis, provider behaviour, automation patterns, evidence development, and understanding the unfiltered event stream.
Apply the selected report rules
Useful when the operator needs a defined event, link, provider, bounce, recipient, time, campaign, or audience scope.
Export stronger evidence of human intent
Useful for commercial follow-up and analysis where the chosen confidence threshold, reason evidence, and uncertainty remain visible.
Scope, review, generate, hand over.
Export should follow the reporting review, not replace it.
Define the purpose
Decide whether the file is for campaign review, sales follow-up, compliance evidence, migration, client handover, audit, archive, or another legitimate task.
Choose the scope and columns
Select the campaign, events, confidence, link, recipient, time, audience, provider, bounce, and fields required for that purpose.
Review the report first
Confirm that the report view answers the intended question before creating a file that may be shared or acted upon outside ASI.
Generate and control the handover
Create the selected CSV or package, record the export action, and share it only with the people who need the data for the stated purpose.
The protection boundary changes when the file leaves ASI.
ASI can control the scope, generation, and evidence inside the export workflow. The client remains responsible for where the file goes, who can access it, how long it is retained, and when it is deleted.
Client-controlled purpose
The client determines why the export is required and remains responsible for lawful, appropriate, and proportionate use of the data.
Access control
Files containing subscriber, campaign, or recipient evidence should be shared only with authorised people and protected according to the client’s security requirements.
Retention and deletion
Exported files should not remain indefinitely in downloads folders, inboxes, shared drives, or client packs after the operational purpose has ended.
ASI does not own the file
ASI provides the protected export mechanism. It does not become the owner or independent controller of the client’s exported subscriber and campaign data.
An export is not the same thing as a governed archive.
Operational CSVs support review and handover. Long-term audit history requires controlled packaging, integrity checking, encryption, retention rules, and a recoverable relationship to ASI Core truth.
Operational export
A working file created for immediate review, analysis, follow-up, evidence handover, or another bounded business task.
Historical evidence package
A governed package of older campaign and operational evidence stored on designated archive infrastructure rather than left as unlimited hot data.
Minimised where appropriate
Historical packages can reduce or remove direct identifiers where operational and legal requirements allow, while retaining recovery through canonical ASI identifiers.
Client-governed retention
The client’s retention, deletion, legal, audit, and source-data rules determine how long exported and archived evidence should remain available.
Convenience should not quietly weaken the evidence.
ASI exports are designed to remain useful without creating false certainty, duplicated truth, or uncontrolled data sprawl.
No independent recalculation
The export layer should not calculate a different delivered estimate, click classification, recipient scope, or campaign total from Reports Builder.
No automatic lead claim
A recipient appearing in a human-confidence export is not proof that the person wants a sales call, will buy, or has authorised a new marketing purpose.
No suppression bypass
Exporting a suppressed or unsubscribed record for evidence does not make that recipient eligible for future sending.
No uncontrolled database copy
Advanced export does not mean every operator should receive every subscriber, campaign, event, compliance, and infrastructure field in one file.
A usable piece of the evidence.
The file is scoped, labelled, structured, reviewable, traceable, proportionate, and understandable by somebody who was not standing beside the operator when it was created.
A fresh spreadsheet problem.
The scope is unclear, bot activity looks human, columns lack definitions, duplicate rows multiply, personal data travels too widely, and the team spends the afternoon rebuilding context that existed before the export.
Explore the surrounding ASI rails
Continue into Campaign Reports & Insights, Bot Clicks vs Human Click Detection, List Health & Validation, Subscriber Validation Pipeline, Email Compliance, and Migration & Merger Tools.
The evidence should still make sense after the CSV opens.
Request a private Sender Review to examine your current campaign exports, recipient handovers, bot-click handling, confidence fields, audit evidence, data-minimisation controls, client reporting, archive process, and the amount of spreadsheet repair your existing platform quietly creates.