Overview
This reference lists the confirmed filters, widgets, and reporting pages available in the tenant reporting area.
Use it when you need a quick reminder of what can be filtered, what the dashboard can show, and which dedicated reporting pages exist for deeper follow-up work.
Reporting model at a glance
Altrinum reporting is generally split into two layers:
- Dashboard: for broad operational visibility, comparison, and trend review
- Dedicated reporting pages: for narrower, more exact review work such as finance, compliance, audience health, or campaign analysis
This distinction is useful because a team may start with a broad dashboard view and then move into a specific report once the next action is clear.
Dashboard filters
The dashboard supports these filters:
- date preset
- start date
- end date
- period
- included sources
- adjustments
- event
- program
- giving form
- designation
- attribution interaction type
- tracking source
- tracking subsource
Filter usage notes
These filters affect how widgets and charts should be interpreted.
In practice, this means:
- the same widget may show very different results depending on the selected scope
- two staff members may appear to be looking at conflicting numbers when they are actually using different filter sets
- export decisions should usually be made only after the team confirms the dashboard scope
Common filter patterns
Teams may commonly use filters like these:
- a broad monthly or quarterly view for leadership check-ins
- a single event filter for event review
- a giving-form or designation filter for fundraising analysis
- a tracking source filter to understand attribution patterns
- a fiscal or campaign-period window before export work
Confirmed dashboard widgets
The current widget set includes:
- KPI overview
- donation KPIs
- event KPIs
- program KPIs
- email KPIs
- collected revenue chart
- activity trends chart
- operational funnel overview
- attribution overview
- top tracking sources
- top entities
Widget interpretation notes
These widgets are generally most useful when teams are asking comparative or directional questions, such as:
- What appears to be moving up or down?
- Which area is driving the most visible activity?
- Which source seems strongest in the selected period?
- Are results aligned across giving, events, programs, and email?
Widgets are usually not the right final tool when staff need an exact operational export.
Reporting pages
The following reporting pages are confirmed:
Email PerformanceEmail Audience HealthEvent Tax ReportReceipting Compliance Report
AI ask optimization attribution data
Donation records can now carry ai_ask_optimization_attribution_json when AI Ask Optimization was applied during the public donation flow.
This field is meant to support reporting-oriented follow-up such as:
- separating optimized donations from non-optimized donations
- grouping optimized gifts by strategy or confidence
- comparing optimized gift outcomes by giving form or tracking source
The field is only populated when optimization was actually applied, so blank values should be interpreted as no stored optimization attribution for that donation.
AI Ask Optimization donation reporting
The donation reporting surface now exposes AI Ask Optimization as completed-donation attribution reporting.
Confirmed reporting filters include:
AI Ask AppliedAI Ask StrategyAI Ask ConfidenceGiving FormTracking Source
Confirmed attribution summary metrics include:
AI Ask Optimized GiftsAI Ask Optimization RevenueStandard Gift CountStandard RevenueAverage Optimized GiftAverage Standard Gift
Confirmed breakdowns include:
- revenue by giving form
- revenue by tracking source
- filtering by paid date range
- drill-down links from AI Ask summary stats into the filtered
Donationslist - quick widget actions that open optimized or standard completed gifts in the filtered
Donationslist
Confirmed donation list and export follow-up includes:
- an
AI Askbadge on donation rows and donation detail pages - export columns for
AI Ask Attribution,AI Ask Strategy,AI Ask Confidence, andAI Ask Reason Codes
Important interpretation note:
- This reporting is derived only from completed donations with persisted attribution.
- It does not measure who saw an optimized ask and did not donate.
- It should be treated as donation-attribution reporting, not exposure or impression analytics.
Reporting page usage guidance
Email Performance
Use this page when the question is specifically about email campaign results rather than broad tenant-level comparison.
Email Audience Health
Use this page when staff need to review the condition or readiness of the audience before sending, or when investigating audience-related delivery or eligibility concerns.
Event Tax Report
Use this page when the work is event-specific and requires exact tax-related review or export.
Receipting Compliance Report
Use this page when finance or compliance staff need a precise receipting-focused review tied to a fiscal or custom reporting window.
Recommended workflow
A common and healthy workflow is:
- start with the dashboard
- set the reporting window and scope
- identify patterns or questions
- narrow to one area if needed
- open a dedicated reporting page when precise follow-up or export is required
This helps teams use the right screen for the right job.
Notes
- Widget visibility may depend on enabled modules and available data.
- Some reporting pages are broadly useful across the tenant, while others are especially relevant to finance, compliance, or email operations.
- Dashboard interpretation always depends on the active filters.
- Dedicated reporting pages are usually the better choice when the task requires exactness, export, or downstream operational handling.
Example role-based usage
A campaign manager may spend most of their time in:
- dashboard views
Email Performance
A finance lead may rely more heavily on:
Event Tax ReportReceipting Compliance Report
An executive or director may primarily use:
- dashboard KPIs
- trend charts
- top-source or top-entity views
These are not strict boundaries, but they help explain why both dashboard and dedicated reporting layers exist.