Campaign reporting should explain the evidence, not merely display the totals.
Advanced Subscriber Intelligence preserves the operational evidence beneath every campaign so operators can review what was attempted, accepted, estimated as delivered, opened, clicked, bounced, unsubscribed, complained, held, or classified as automated activity.
Reports Builder, Event Stream, Recipient Drilldown, link analysis, domain behaviour, CSV exports, and PDF outputs work from the same protected reporting truth. The aim is to keep each view aligned with the question the operator asked.
ASI reporting is designed to provide up to 92% accurate operational data. It does not pretend every open or click proves human intent, and it does not hide uncertainty behind a large colourful number.
Event-Level Evidence
Recipient Drilldown
Up to 92% Operational Accuracy
A number without the evidence beneath it is dashboard decoration.
ASI reporting is built so campaign summaries, filtered views, CSV exports, PDF outputs, recipient evidence, and event-level activity can be traced back to the same protected operational record.
Three reporting layers, three different questions
Raw activity, filtered evidence, and human-confidence reporting should not be collapsed into one unexplained click total.
What activity was recorded?
Raw reporting preserves the events seen by the platform, including opens, clicks, provider responses, automated activity, suspicious patterns, and the evidence required for later classification.
What remains after the selected rules?
Filtered reporting applies the requested event, confidence, recipient, link, domain, time, bounce, campaign, or audience scope without rebuilding a different version of the underlying truth.
How strong is the evidence of human intent?
ASI evaluates timing, navigation, browser, device, sequence, honeypot, scanner, and later-event evidence to estimate confidence rather than declaring every recorded click human.
Reports Builder is the reporting truth. Other views consume it.
ASI protects the reporting contracts so a PDF, CSV, filtered page, or recipient view does not quietly invent a different answer to the same scoped question.
Reports Builder
The CSV-first reporting rail defines the selected campaign scope, evidence filters, totals, event rows, recipient fields, and output contract.
Event Stream
The event-level activity beneath the report remains visible for review by event type, time, recipient, domain, link, bounce class, confidence, device, and related evidence.
Recipient Drilldown
Recipient-level review brings identity, activity, links, events, delivery, bounce, confidence, and campaign context together without pretending uncertainty has vanished.
PDF Control
PDFs provide the visual presentation layer. They consume the scoped reporting truth rather than recalculating campaign meaning independently.
From queue movement to recipient evidence.
Reporting begins with the operational send record and follows the evidence through provider response, delivery estimates, recipient activity, suppression, and campaign outcomes.
Send and queue totals
Review eligible, queued, attempted, accepted by the MTA, held, suppressed, failed, and other operational campaign states.
Delivered estimate
ASI distinguishes accepted transport evidence from the delivered estimate used in campaign reporting instead of presenting the two as the same event.
Bounce and rejection evidence
Hard bounces, soft bounces, provider reputation responses, diagnostics, SMTP codes, classifications, and campaign impact remain available for analysis.
Unsubscribes and complaints
Recipient exits, complaints, abuse evidence, feedback identifiers, and resulting suppression decisions remain part of the campaign story.
Opens and clicks
Raw and classified engagement can be compared without allowing privacy systems, scanners, or repeated automation to masquerade as simple human totals.
Links and specific-link scope
Review tracked links, unique recipients, timing, domains, confidence, and one selected link when the commercial question is narrower than the whole campaign.
Domain and provider behaviour
Compare provider or destination-domain outcomes, including attempts, acceptance, bounces, deferrals, engagement, complaints, and abnormal changes.
Time-series behaviour
Hourly and daily views help show when sending, provider response, engagement, complaints, and other campaign activity changed.
Clicks are evidence. They are not automatically proof of a person.
ASI evaluates thirty-eight signals across a 72-hour evidence window and assigns a continuous confidence score from 0% to 92%.
Timing evidence
Events occurring unrealistically soon after delivery can indicate scanning or prefetch behaviour rather than ordinary human action.
Navigation and browser evidence
Browser, operating-system, navigation, sequence, and later-event evidence can strengthen a human interpretation after the timing evidence supports it.
Automation and honeypot evidence
Security scanners, bots, hidden-link interaction, machine fingerprints, repeated patterns, and suspicious sequences can lower or remove human confidence.
Evidence can evolve
A suspicious early event may later gain stronger human evidence. ASI can reclassify the interpretation as the 72-hour evidence window develops.
Common operational milestones appear around 68%, 86%, and 92%, but ASI preserves the continuous score and reason evidence rather than forcing every recipient into a simplistic yes-or-no box.
Build the question before exporting the answer.
ASI reporting is scoped before the report is generated so the operator can define which evidence, recipients, fields, links, confidence levels, and sections belong in the output.
Choose the scope
Select the campaign, audience, event types, confidence threshold, time range, recipient fields, report sections, and any specific-link focus.
Build the report view
Reports Builder applies the protected reporting contract and produces the totals, tables, events, recipients, links, and evidence for the selected scope.
Review the evidence
Check campaign totals, Event Stream, Recipient Drilldown, provider behaviour, time series, links, and reason evidence before drawing the conclusion.
Export or share
Create CSVs, branded reporting packages, or PDFs that retain the same scope and meaning used in the reviewed report.
The output format can change. The evidence contract should not.
ASI keeps CSV-first truth at the centre so visual and operational outputs can remain aligned instead of drifting into separate reporting products.
CSV exports
Export Event Stream, recipient, link, campaign, and selected subscriber fields for operational review, analysis, and controlled downstream use.
Branded packages
Large CSV outputs can be packaged into structured branded files with bounded row sizes while preserving batch, row, identity, and campaign context.
PDF preview and delivery
PDFs can be previewed, downloaded, or delivered through the reporting workflow while retaining the selected report scope.
No independent recalculation
PDF and display layers should not rebuild campaign meaning from raw events when Reports Builder has already defined the authoritative scoped result.
Campaign anomalies need a timeline, not a shrug.
ASI can correlate campaign, content, operator, provider, queue, and outcome evidence to identify the most plausible explanation for unusual behaviour without pretending correlation proves absolute causation.
Content evidence
Draft Content Review warnings, subject and copy evidence, ignored suggestions, later changes, and the final sent version can be compared.
Operator actions
Resaves, reruns, approvals, exclusions, queue actions, holds, releases, and other operational decisions belong on the same timeline.
Provider and queue outcomes
Acceptance, deferrals, rejection, Google MX behaviour, queue composition, pacing, bounce classes, and the point at which behaviour changed remain visible.
Evidence-led explanation
The report can surface the strongest operational explanation while clearly marking what is known, inferred, uncertain, or still unproven.
The useful report is the one that improves the next decision.
ASI reporting is designed to reduce noisy activity into evidence that campaign, account, and sales teams can review before deciding who deserves attention.
Cleaner call lists
Confidence, recipient, link, time, device, company, title, phone, and other permitted fields can support a more useful follow-up export.
Less automated noise
Scanner and bot activity can be separated from stronger human evidence instead of sending a sales team after every machine-generated click.
Stronger campaign learning
Operators can compare subjects, content, providers, links, timing, audiences, complaints, bounces, and confidence evidence before repeating the same campaign pattern.
Defensible client reporting
Agencies and internal teams can explain how the report was scoped, which evidence was included, and where the remaining uncertainty sits.
Preserves and interprets operational evidence.
It aligns campaign totals, events, recipients, links, provider behaviour, exports, PDFs, confidence evidence, and traceability around the same scoped reporting truth.
Pretend uncertainty has disappeared.
ASI does not claim every delivered estimate is a mailbox receipt, every open is a person, every click proves intent, or every campaign anomaly has one certain cause.
Explore the surrounding ASI rails
Continue into Bot Clicks vs Human Click Detection, Advanced Data Exports, Sending Engine & Queue Control, Google MX Protection, List Health & Validation, and Email Compliance.
Better campaign decisions begin with evidence that survives the dashboard.
Request a private Sender Review to examine your current campaign reporting, raw-versus-human activity, exports, recipient drilldown, provider evidence, sales follow-up process, and whether your existing platform can explain the numbers it displays.