A SaaS email can reach several people at one company while producing one paid account. If the report treats every recipient as a separate purchase opportunity, the result may answer a different question from the one the team intended to ask.
Use Migma to prepare the next lifecycle message after the measurement owner agrees on its job. For account-level upgrades, the important question is which eligible accounts completed the accepted outcome. Individual replies and clicks remain useful evidence, but they should not quietly become additional paid accounts.
Start with a small fictional example
Imagine an onboarding campaign reaches people attached to three trial workspaces. Cedar has three recipients, Elm has one, and Oak has two. During the agreed period, Cedar becomes paid, Elm remains on trial, and Oak closes its workspace without upgrading.
This fictional example contains six recipients and one upgraded account. It does not contain three conversions because three Cedar teammates received the email. Nor does it establish that the email caused Cedar to upgrade. It describes a business outcome after an email was delivered.
Loops’ email KPI guide distinguishes recipient and account reporting and advises keeping attribution separate from causal evidence. The example here uses a different small cohort to show how the creative team can recognize a reporting-unit mistake before changing a campaign.
Declare the reporting unit in the title
Label a report “eligible account upgrade rate” when that is what it measures. Name the account identifier, what makes an account eligible, the accepted upgrade event, and the measurement window. A heading like “email conversions” leaves all four open to interpretation.
For the fictional cohort, three eligible trial accounts and one accepted upgrade would give an account rate of one out of three. That arithmetic is illustrative, not a benchmark or a claim about campaign effectiveness. A recipient-level rate would need its own recipient-level outcome definition; it cannot reuse the account numerator without explanation.
Keep monetary value separate from the count of upgraded accounts. One account can change plan several times, have several transactions, or receive a refund. Ask the billing owner which event and revenue treatment your report accepts.
Test people who belong to several workspaces
Now make the example less tidy. Suppose one person administers both Cedar and Elm. A click associated with that person’s email address does not identify which account later upgraded unless the authenticated product journey establishes the relationship.
The analyst should explain the person-to-account join. The marketer should understand enough of that rule to avoid claiming that a message reached the right decision maker solely because it reached a known address. Use stable internal identifiers in the analysis system, while keeping private identifiers and personal information out of public links and creative copy.
Also inspect timing. If someone changes workspaces during the measurement period, decide whether the report uses the relationship at delivery, at the outcome, or another accepted rule. Record the choice rather than letting the join behavior decide the story accidentally.
Distinguish delivery, action, and attribution
An account may have several teammates receive a message, one teammate click, and a different administrator upgrade. Those are separate events. A report can show them together without pretending they are the same action.
| Evidence | Question it helps answer |
|---|---|
| Delivered messages | Who had an opportunity to receive the communication? |
| Authenticated product actions | Which person performed which action in which account? |
| Accepted billing outcome | Which eligible account actually became paid? |
| Attribution rule | Which messages receive reporting credit? |
Do not sum overlapping campaign assists as unique upgrades. If several messages preceded one account outcome, use the measurement owner’s accepted rule and label the result clearly. To estimate additional outcomes caused by email, use an appropriate causal study design rather than renaming an attribution report.
Turn the accepted result into a better brief
Migma creates editable email campaigns and series that wait for review. Give it one accepted finding and a reader-focused hypothesis. For example, a team might review whether an administrator needs clearer setup instructions, while keeping the audience and offer unchanged for a controlled creative comparison.
Avoid asking Migma to “increase account conversions” without saying what the reader should understand or do. Specify the action, the approved account terminology, and the destination. If different roles need different explanations, prepare separate reviewed versions and have the sending owner verify eligibility.
Run Email Preflight on the creative. Separately check the final populated destination message and the authenticated link path. Preflight does not validate your account join or billing outcome.
Save a report someone else can reproduce
Keep the cohort definition, identity rule, event definition, time window, creative version, and reporting owner together. Recalculate the fictional cases first whenever the measurement logic changes. They make duplication and relationship errors easier to spot than a large aggregate number.
Use the accepted account result to choose the next Migma revision. A small, understandable report gives the team a stronger basis for action than a larger conversion total whose people and accounts cannot be separated.
Frequently Asked Questions
Do three teammates upgrading one account count as three conversions?
For an account-upgrade measure, count the accepted account outcome once. Recipient actions can be reported separately using their own definition.
Can one recipient belong to several reporting accounts?
Yes. Define and verify the person-to-account relationship and its timing. An email address alone may not identify the account involved in a later product action.
Does an upgrade after delivery prove email caused it?
No. That is an observed sequence. Use an appropriate causal measurement design if the question is how many additional upgrades email produced.
What should the creative team receive from the analyst?
Provide the accepted cohort, reporting unit, outcome, window, identity rule, and one bounded finding. Use that evidence to write a specific Migma brief.