Azimea Academy · Full walkthrough
Reports: understand every dashboard, chart and result
Explore all nine report tabs with extensive, clearly fictional historical data. Understand delivery, engagement, attribution, campaign comparisons, flow funnels, API email history, external journeys, audience growth, costs and feedback distributions. Inspect individual records and export responses.
The video could not load. Try again or read the guide below.
What you will see
- Explore all nine report tabs with extensive, clearly fictional historical data.
- Understand delivery, engagement, attribution, campaign comparisons, flow funnels, API email history, external journeys, audience growth, costs and feedback distributions.
- Inspect individual records and export responses.
Transcript
Welcome to a complete tour of reports. This fictional company has a substantial synthetic history prepared specifically for this
lesson. No emails were sent to create these results. We will explore every report tab, explain each chart, and follow the numbers into
campaign message and feedback details.
Start with the reporting period. Ninety days gives us a broad view of the demonstration history, including several campaign groups and
automated journeys. Apply the range before interpreting a result.
Most dashboard tabs use this window, while an individual campaign report explicitly shows its lifetime scope.
Comparison adds the previous equivalent period. The headline cards summarize the selected window with changes against that earlier
baseline. A rate moving from ten to twelve percent changes by two percentage points.
Volume and rate changes answer different questions, so read the label alongside the number.
Overview brings marketing email performance together. The value trend places attributed conversion value on a time axis, making peaks
and quieter periods visible. This is measured attribution, not proof that email alone caused the purchase.
Transactional API messages have their own report rather than being mixed into this marketing overview.
Delivered changes the trend to message volume. A spike can simply mean that a large campaign went out that day.
Compare the shape with value and engagement before deciding whether a busier sending day was also a more productive one.
Delivery confirms a provider outcome, not a guaranteed position in the inbox.
Opens changes the same chart to detected human opening activity. Known automated opens are excluded from the human measure.
Privacy protections and disabled tracking can still hide genuine reading, so an open is a useful signal, while a missing open does not
prove that someone ignored the message.
Clicks provides a stronger sign that someone followed a tracked destination.
Compare the peaks with delivered volume and the subsequent conversion trend.
Repeated clicks, unique people, and click rates are different measures.
Use the chart label and the detailed report to understand which one you are reviewing.
The top campaigns ranking helps identify which email campaigns contributed most to the selected result.
The bars make differences easy to scan, while the adjacent figures provide the actual scale.
A large result may come from a large audience, so compare efficiency as well as absolute contribution.
The source share chart divides attributed value between campaigns and flows.
Each segment represents a share of the displayed total rather than a conversion rate or a share of all company revenue.
Use it to understand the balance between scheduled marketing activity and ongoing automated journeys.
The reading heat map groups measured opens by day and hour. Darker cells identify concentrations of observed reading, which can suggest
times worth testing. Check the report time zone and remember that sending schedules influence the pattern.
A busy cell is evidence of activity, not a universal best time to send.
The expandable recommendations and AI activity area adds context beneath the main charts.
It highlights useful observations and shows where AI drafts are being used.
Treat these observations as starting points for investigation. The underlying delivery, engagement, and conversion reports provide the
evidence needed to judge a recommendation.
Campaigns provides a workspace for both the overall list and individual campaign results.
The campaign selector establishes the scope, while the email selector moves between the whole campaign and a particular message.
This is useful when one marketing initiative includes an introduction, a follow-up, and a final reminder.
We will inspect the autumn collection campaign. Its whole campaign summary combines the emails within this initiative and clearly
labels the lifetime scope. Sends are counted per email, so the same contact can contribute more than once.
These totals should not be interpreted as a unique audience count.
How fast people reacted aligns each message by the time elapsed after sending.
The cumulative open curve shows how the share of delivered emails grows over the following hours.
A steep early rise indicates a quick response. A flatter curve shows that relatively little additional measured opening happened later.
Switching to clicks keeps the same elapsed time perspective. It helps compare how quickly people acted rather than simply how many
messages were delivered on a calendar date. Compare similar audiences and message purposes because a lower curve can reflect different
intent as well as different creative performance.
The goal area compares the campaign result with its configured target.
The progress indicator shows achievement against that target, while budget and return figures provide financial context.
Check the chosen goal, the cost basis, and the reporting scope before treating a percentage above the target as a profitability
The Emails tab separates the messages that make up this campaign.
It lets us compare their delivery, engagement, and outcomes without losing the shared initiative context.
Use this breakdown to find whether one follow-up contributes meaningful additional value or simply repeats activity already generated
The campaign timeline places its messages in chronological order.
It explains when the introduction and later follow-ups occurred, which helps interpret changes in the charts.
The timeline describes the sequence of activity. The summary and email reports explain the measured outcome of each part.
Now we will open the introduction email. Its summary separates sent messages, delivery, human opens, clicks, conversions, and
attributed value. Additional metrics expose less frequent outcomes.
The comparison badges use the stated campaign benchmark, so read that reference rather than assuming every badge compares with the
The A/B table separates the original subject, its alternative, and the later winner rollout.
Review the sample size and outcomes for each version before interpreting the selected winner.
A small test can produce an apparent lead without strong evidence.
The displayed confidence and decision metric matter as much as the winner label.
The Activity tab follows measured email events over time. It helps connect the summary totals with when delivery, opening, and clicking
occurred. Use it to investigate an unusual burst or a delayed response, then narrow the investigation with the links or recipient-level
When it was read shows the distribution of measured reading for this specific email.
It helps distinguish an immediate response from activity spread over later hours.
Use this alongside the broader heat map. One explains this message, while the other summarizes a wider collection of marketing
Links provides the detailed destination breakdown. Compare the primary collection link with supporting content to see which paths
attracted attention. Check the destination and the distinction between total and unique activity before deciding whether a change in
link placement improved the message.
What people clicked ranks the tracked destinations in the email. It shows where measured attention went and helps connect the message's
visual hierarchy with actual navigation. A destination can receive repeated clicks, so do not automatically read its click count as the
Conversions follows the business outcomes attributed to this email.
These records connect the message with registered conversion events and any recorded value.
Attribution depends on the configured measurement rules. A reported conversion is not the same as an independently proven incremental
By conversion separates the outcomes attributed to this email by event type.
Our fictional data includes paid orders and completed registrations.
Some events carry monetary value, and others do not. Keeping them separate prevents a useful non-purchase action from being mistaken
Recipients brings the report down to individual delivery records.
It helps investigate why a particular fictional recipient delivered, bounced, or showed measured engagement.
Summary percentages are useful for spotting a pattern. Recipient details help explain the cases behind that pattern.
Sent email preserves the message associated with this historical send.
This lets you check the actual wording and destinations alongside its results.
The visible content here explicitly identifies synthetic demonstration history.
Reviewing the sent version avoids interpreting old performance against a template that may have changed later.
The email timeline restores the broader campaign sequence around this message.
It helps place its result alongside the other emails in the initiative.
Use this context when a later reminder appears to perform differently from an introduction sent to people at an earlier stage.
The follow-up email includes a holdout group. This report compares converters and value per person between the mailed group and
eligible people deliberately left out. The difference can be positive or negative.
Check the observation window, group sizes, and uncertainty before treating an apparent effect as reliable incremental value.
Compare brings campaign results together in one view. Select comparable campaigns and review both outcome and sample size.
The reaction comparison aligns elapsed time after sending, while the accompanying figures summarize performance.
Different audiences, budgets, and objectives can explain a difference even when the creative looks similar.
The reaction comparison overlays the campaigns after aligning their send times.
This makes response speed easier to compare than a calendar chart where the emails went out on different days.
Review the open and click views separately and consider both the size of the audience and the purpose of each campaign.
Flows ranks automated journeys by their measured results and entries.
These demonstration journeys retain historical data while remaining unpublished, which is why their status says they are not live.
Current publication status and historical performance answer different questions.
A stopped flow can still have a useful reporting history.
The selected flow funnel follows people through the recorded journey.
Its stages show where entrants continued, waited, received an email, or reached the measured business outcome.
The narrowing bars help identify drop-off, but a wait or an intentional branch should not automatically be diagnosed as an error.
Email engagement details expands the delivery stages into measured opening and clicking.
This separates reaching a recipient from attracting attention and producing an action.
Read the stage definitions before dividing one figure by another, especially when a flow can send several emails to the same person.
The holdout comparison contrasts eligible people who received the flow with a group deliberately excluded from sending.
It provides a stronger basis for estimating incremental impact than attribution alone.
Review group sizes and uncertainty. An apparent uplift from a small sample may not yet support a confident business decision.
API emails keeps transactional submissions separate from marketing campaigns and flows.
Accepted submissions count API requests, while recipients count the addresses within those requests.
One submission can include several recipients, so these headline numbers are not expected to match.
Sent and delivered describe later stages of those recipient messages.
More delivery metrics exposes additional outcomes without crowding the main summary.
Here we can review failures and engagement alongside the primary delivery figures.
Transactional messages may have tracking disabled or constrained by privacy protection, so zero opens or clicks cannot establish that a
receipt or account message went unread.
Daily Evolution plots a chosen API measure across the reporting window.
The current and previous series help identify changes in submission or delivery volume.
These are cohorts based on when requests were accepted, so later outcomes can update an earlier day's results rather than appearing as
Changing the metric to recipients reveals the effect of requests addressed to several people.
Compare this with accepted submissions to understand the workload behind the API traffic.
A stable request count can still produce more recipient messages when the composition of those requests changes.
History lists actual submission records with their status, recipients, and acceptance time.
It is the starting point for investigating one transactional request.
Pagination keeps the list manageable, while the summary remains useful for understanding the overall volume across the selected period.
Search and the advanced filters narrow the history by information such as sender, template, and tags.
We will search for the studio order messages. Applying filters changes the investigation scope.
Clear them before assuming that a smaller list represents all transactional activity in the account.
A submission detail connects its acceptance time, sender, and recorded metadata with the request.
Metadata can help match an email with an order or an application event.
These are fictional demonstration identifiers. In a real investigation, use the identifier to connect the report with the relevant
The recipient section separates outcomes within the submission and exposes the measured event history.
A request accepted successfully can still have different delivery results for its recipients.
Inspect this level when an application reports success, but a particular person did not receive the expected message.
External Campaigns follows activity that starts outside Azimea Email, such as a paid advertisement.
The comparison table uses configured event names and campaign identifiers.
Final outcomes are calculated from people whose observation window has completed, while newer entrants remain under observation rather
than being counted prematurely as failures.
The selected journey connects the configured stages, an advertisement view, a landing visit, registration, and a paid order in this
example. Each bar shows how many eligible people reached that step in order within the window.
The largest loss highlights a transition worth investigating rather than explaining its cause by itself.
Selecting another campaign updates the journey while preserving the same stage definitions.
Compare its completed observation cohort and final rate alongside its recorded cost.
The external campaign cost is useful context, but it is not automatically the same financial scope as the email profitability report.
Check report data exposes issues that can distort an external funnel, including overlapping campaign identifiers, missing links between
events, and late activity. Review these diagnostics before optimizing a campaign based on its apparent drop-off.
A measurement gap and a real customer abandonment can look similar in a chart.
Deliverability brings the health of sending into one view. The gauges summarize delivery and adverse outcomes such as bounces,
complaints, and unsubscribes. They help spot a problem quickly, while the detailed trends and provider breakdown explain where that
The bounce trend shows messages that failed delivery across the selected window.
Compare a spike with sending volume and the source campaigns before judging its severity.
The total count identifies scale, while the bounce rate relates that count to the number of attempted messages.
The complaint trend records messages reported as spam. Even a small count deserves attention because it describes a different problem
from an invalid address. Our synthetic data set includes examples, so the chart is visible.
Use the associated campaign and audience context to investigate permission and message expectations.
The mailbox provider table separates outcomes across recipient domain groups.
It helps identify whether a problem is broadly distributed or concentrated in one provider.
These provider results are fictional examples. Compare rates together with sample size.
A tiny group can produce a dramatic percentage from very few messages.
Audience groups contacts into engagement tiers. The stacked distribution makes the balance between more active and less active contacts
easy to see. These tiers describe observed activity under the report's rules.
They do not replace consent or establish that every contact is eligible for a particular campaign.
The growth chart places contacts gained and lost alongside one another over time.
Looking at both bars explains the net change better than a single total.
A growing database can still have substantial churn, while a quieter period can reflect fewer new subscriptions rather than a delivery
Conversions and value focuses on recorded business outcomes attributed to marketing email.
Its dates follow when conversions occurred, which can differ from the sending cohorts used elsewhere.
The headline cards connect event counts with any recorded monetary value.
They describe measured outcomes rather than all revenue across the company.
Count plots the number of conversion events and separates contributions from campaigns and flows.
This reveals changes in outcome volume without depending on the size of an order.
A registration and a paid order can both count as events, which is why filtering by conversion type matters.
Value changes the chart to recorded monetary amounts. It can rise even when event count is stable if the average value increases.
Check the currency and the event types included. An event without a value can still be meaningful, but it should not be interpreted as
Filtering to completed registrations isolates a non-monetary outcome.
The count remains useful while the interface explains the absence of recorded value.
Choose the event that matches your objective before comparing performance, so a successful registration journey is not judged solely by
Costs and return combines the recorded value with the configured cost basis and profit margin.
Return on spend and profit-based ROI are different calculations. Review which costs are included and whether the margin assumption is
appropriate before using the result to decide how much to invest.
The source contribution table shows which campaigns and flows produced the attributed conversions and value.
Average value, value per email, and share of the total answer different efficiency questions.
A source with the largest total is not necessarily the most efficient when its audience or sending volume is much larger.
The conversion type breakdown keeps paid orders and completed registrations visible together.
It explains what sits behind an aggregate conversion count. Use this table to confirm that the reported success corresponds to your
intended business action rather than combining several unlike events into one unexplained number.
Pages and feedback summarizes submitted answers across the selected sources.
Response count measures participation, positive ratings summarize the defined high scores, and NPS uses its own recommendation formula.
These measures describe different questions. The demonstration badge identifies the synthetic source rather than presenting its answers
Response volume shows when submissions arrived. It helps distinguish a steady feedback stream from a short burst following an
invitation. A higher volume does not necessarily indicate happier customers, so use the rating trend and the actual questions alongside
The positive rating trend shows the share of qualifying high scores over time.
It separates sentiment from participation volume. Compare the number of answers behind each day and keep the scale consistent.
A percentage based on very few responses can move sharply without representing a reliable broader change.
The source table identifies which pages collected the answers and provides a route into their details.
This matters when several flows ask different questions. Compare equivalent sources deliberately and use the page-specific report when
you need the exact wording, version, and response distribution.
Responses lists individual submissions across the selected feedback scope.
It lets us connect an aggregate pattern with the wording people supplied.
Filters help keep the review relevant. A memorable comment can explain a possible issue but should be considered alongside the
distribution rather than replacing it.
The delivery experience report keeps one source, its versions, and its active response scope together.
The summary distinguishes total responses from answers to the selected question.
Versions are important when wording or scales change because answers collected under different definitions should not be combined
without considering that difference.
Score over time plots daily scores for the selected question. Here, the question uses a five-point satisfaction scale, so the average
stays within that scale. This is different from the earlier positive share trend, which measures the proportion of high answers rather
The rating distribution shows how many answers fall into each score.
It reveals patterns that an average can hide, such as a mixture of very low and very high ratings.
Read both the counts and percentages and use a bar to inspect the responses behind a particular answer.
The multiple-choice distribution answers a different question: what should improve first?
Its bars compare options such as packaging and delivery speed. These categories are not points on a numerical scale, so the useful
comparison is their response share rather than a calculated average.
Selecting the recommendation question changes the report to NPS. Scores nine and ten are promoters, seven and eight are passive, and
zero through six are detractors. NPS subtracts the detractor percentage from the promoter percentage, producing a result from minus one
hundred to one hundred rather than an average out of ten.
Selecting packaging narrows the report to matching responses and makes the active answer filter visible.
This connects the distribution with the underlying comments. Remember that the totals now describe the filtered subset and clear the
filter before returning to the complete source report.
We will clear the answer filter and download the active responses as a CSV file.
Review the dates, version, and archive scope first. Archived responses are excluded from active charts and exports, so the exported
file should be interpreted using the same scope that was visible in the report.
We have explored every reports tab and followed the charts into their detailed records.
Begin with the scope, distinguish delivery from engagement and business outcomes, and investigate the distribution behind a headline
number. Use attribution to describe measured connections and hold out evidence when you need to assess incremental impact.