Tabellab

Revenue per Recipient by Flow: Email-Level RPR, Placed-Order Rate and a Five-Flow Scorecard with SUMIFS

Lesson 1 of 20Lab

All lessons
  1. Revenue per Recipient by Flow: Email-Level RPR, Placed-Order Rate and a Five-Flow Scorecard with SUMIFSLabFree
  2. The Welcome Series: First Orders per Email, Subscriber-to-Customer Rate and Revenue per Subscriber by Signup SourceLab Locked
  3. The Abandoned-Cart Flow: Reach Rate, Recovery Rate and Margin per Recipient After the DiscountLab Locked
  4. Browse Abandonment: RPR by Category, an Index Against the Flow Average and a Keep-or-Review Rule with UnsubscribesLab Locked
  5. The Post-Purchase Flow: Review Rate, 60-Day Repeat Rate, a Target per Product Type with XLOOKUP and a Status with IFSLab Locked
  6. Replenishment Reminders: Days of Supply, Run-Out Date, Reminder Date and a Send-Now Status with Date ArithmeticLab Locked
  7. Flow vs Campaign Share: Flow Share of Email Revenue, Email Share of Store Revenue and the RPR Gap in a Stacked ChartLab Locked
  8. Timing Tests: RPR per Send Delay, Lift Against the Current Timing with SUMIFS and the Winning Variant per FlowLab Locked
  9. Flow Entry Filters: Consent, Already Purchased, Cool-Down and Minimum Cart Value in One Send-or-Skip RuleLab Locked
  10. Time to Convert: Daily and Cumulative Share of Flow Orders and the Attribution Window That Covers 90%Lab Locked
  11. Is the Flow Revenue Incremental? Holdout Groups, Incremental RPR, Incremental Revenue and the Share That Would Have Come AnywayLab Locked
  12. Forecasting Flow Revenue from Trigger Volume: Revenue per New Subscriber, SLOPE, FORECAST.LINEAR and R²Lab Locked
  13. What-If Grid: Margin per 1,000 Cart-Flow Recipients for Every Discount and Recovery Rate, a Heat Map and the Break-Even RateLab Locked
  14. How Long Should a Flow Be? Net Value per Email After Unsubscribes, a Keep-or-Cut Rule and the Cumulative Revenue CurveLab Locked
  15. Flows by Customer Segment: an RPR Matrix with Two-Criteria SUMIFS, the Repeat-to-Prospect Ratio and Each Segment's Share of RecipientsLab Locked
  16. Discounts in Flows: Margin per Recipient With and Without a Code, the Gain per Email and the Emails Where the Code Loses MoneyLab Locked
  17. When Flows Collide: Emails per Subscriber in 7 Days, a Frequency Cap, the Share Over the Cap and the Emails to Hold BackLab Locked
  18. Replenishment Intervals from Real Reorder Gaps: Average vs Median per Product, the Reminder Day and Who Reorders Before ItLab Locked
  19. Prioritising the Flow Backlog: Incremental Revenue per Build Hour, a Rank, Cumulative Hours and a Build-or-Later DecisionLab Locked
  20. Final Project: the Annual Flow Dashboard with Revenue, RPR and Share per Flow, Flow Share of Email Revenue, a Flag Rule and a Combo ChartLab Locked

You are not signed in — the lab works, but your progress is not saved. Sign up

Lesson 1 of 20 is free. Unlock all 20 hands-on labs, the final exam and your certificate.

Buy course — $9.90
Loading the spreadsheet…

What an email automation flow is, and why it needs its own scorecard

Most email marketing reports are built around campaigns: the newsletter that went out on Tuesday, the sale announcement on Friday. Yet in many online shops a large part of the email revenue comes from messages that nobody sends by hand. A new subscriber receives a welcome email within minutes. A shopper who leaves a full cart gets a reminder an hour later. A customer whose tea is about to run out is nudged to reorder. These messages are automation flows: sequences of emails that a customer's own behaviour starts, one person at a time, every day of the year.

Flows are easy to set up and easy to forget. Once switched on, they run for months without anyone looking at them. A campaign that performs badly is noticed the next morning; a flow that performs badly simply keeps sending. That is why flows need their own scorecard: a small table that puts every flow on the same scale, shows which ones carry the programme and which ones only send volume, and can be rebuilt each month in a few minutes.

In this free lesson you build that scorecard in a spreadsheet. The yardstick is revenue per recipient (RPR), the single most useful number for comparing automated emails. The example is Quillmoor Tea Co., a fictional online shop for loose-leaf tea, matcha and brewing gear. All flows, emails and numbers are invented for learning, and every benchmark mentioned is illustrative. You will work with the same 13 flow emails as in the lab above.

The five core flows on the customer lifecycle

Email tools offer dozens of flow templates. Five of them cover most of the customer lifecycle of a shop with repeat purchases, and they are the backbone of this course:

  • Welcome series. Triggered by a new subscription. Introduces the shop and aims at the first order while interest is fresh.
  • Browse abandonment. Triggered when an identified subscriber views a product and leaves without adding it to the cart. A weak signal with a large audience.
  • Abandoned cart. Triggered when a shopper starts the checkout and does not finish. A strong signal with a smaller audience.
  • Post-purchase. Triggered by an order. Helps the customer use the product, asks for a review and suggests what goes well with it.
  • Replenishment. Triggered by a calculated date: shortly before a consumable such as tea is expected to run out.

Five behaviour triggers, five flowsTime in the customer lifecycle: from first signup to repeat ordersSigns upWelcomeseriesViews a productBrowseabandonmentLeaves a cartAbandonedcartPlaces an orderPost-purchaseRuns lowReplenishmentTrigger (what the customer does)Flow (what is sent automatically)
Figure 1: Each flow is started by something the customer does. The trigger decides the timing, not the marketing calendar.

Flows send marketing email, so they need marketing consent just like campaigns, and every email needs a working unsubscribe link. Triggers should rely only on behaviour the customer has agreed to have tracked, such as products viewed or orders placed, and never on protected characteristics such as age, gender or health.

Revenue per recipient: one number for very different emails

How do you compare a welcome email that goes to thousands of brand-new subscribers with a replenishment reminder that goes to a few hundred loyal customers? Open rates and click rates do not help much: they describe attention, not sales, and they differ for reasons that have nothing to do with how good the email is. Revenue per recipient cuts through this. It is the revenue attributed to an email divided by the number of emails delivered:

RPR = attributed revenue ÷ recipients. The first cart reminder of Quillmoor Tea Co. was delivered 2,600 times in October and is credited with $10,816 of revenue, so its RPR is $10,816 ÷ 2,600 = $4.16. Every delivery of this email was worth $4.16 on average. The first browse-abandonment email went out 5,200 times and earned $2,852, an RPR of $0.55. One delivered cart reminder is worth about 7.6 deliveries of the browse email.

RPR is a compound number. Behind it sit the share of recipients who open, the share of those who click, the share of those who order and the size of the order. A shorter way to split it uses only two factors: RPR = placed-order rate × average order value, where the placed-order rate is orders ÷ recipients. For the first cart reminder that is 8.0% × $52.00 = $4.16. When an RPR changes from one month to the next, this split tells you whether fewer people ordered or whether they ordered less.

Use delivered emails as the denominator, not emails sent. Bounced emails never reached anyone, and including them makes a flow with a poor-quality list look worse for the wrong reason. Most tools report both numbers; pick one and keep it.

A fully worked example: Quillmoor Tea Co. in October 2026

Quillmoor Tea Co. runs five flows with 13 emails in total. The table shows what the email tool exports, one row per flow email, plus the two columns you calculate in the lab: revenue per recipient and the placed-order rate. Revenue is attributed to an email when the customer clicks it and orders within five days, an illustrative rule that lesson 10 of the course examines in detail.

FlowEmailRecipientsOrdersRevenueRPRPlaced-order rate
WelcomeW1 Welcome + first-order code4,200189$8,316$1.984.5%
WelcomeW2 How we source our tea3,95071$3,053$0.771.8%
WelcomeW3 Bestsellers3,70052$2,184$0.591.4%
Abandoned cartC1 Reminder after 1 hour2,600208$10,816$4.168.0%
Abandoned cartC2 Reminder after 24 hours2,25099$5,049$2.244.4%
Abandoned cartC3 Last call after 72 hours2,05053$2,597$1.272.6%
Browse abandonmentB1 Still looking?5,20062$2,852$0.551.2%
Browse abandonmentB2 Similar teas4,70033$1,485$0.320.7%
Post-purchaseP1 Brewing guide3,10037$1,517$0.491.2%
Post-purchaseP2 Review request2,90020$780$0.270.7%
Post-purchaseP3 Goes well with2,75066$2,838$1.032.4%
ReplenishmentR1 Running low?1,800153$5,967$3.318.5%
ReplenishmentR2 Second nudge1,45061$2,318$1.604.2%
All flows13 emails40,6501,104$49,772$1.222.7%

The two calculated columns need nothing more than a division, written once in row 4 and copied down to row 16:

  • Revenue per recipient (F4): =E4/C4. Revenue in column E divided by the recipients in column C.
  • Placed-order rate (G4): =D4/C4. Orders in column D divided by the recipients in column C. Format the column as a percentage.
  • Check: multiply the placed-order rate by the average order value (=E4/D4) and you get the RPR again.

Read a few rows before you move on. Inside every flow the RPR falls from email to email: the cart flow goes from $4.16 to $2.24 to $1.27, the welcome series from $1.98 to $0.77 to $0.59. That is normal. The people most ready to buy respond to the first email and leave the flow, so each later email reaches a less interested group. The exception in this table is the post-purchase flow, where the third email, the product suggestion, earns $1.03 while the review request earns only $0.27. The review request is not meant to sell; it has a different job, and lesson 5 measures it by the reviews it collects.

From emails to flows: the scorecard with SUMIFS

Thirteen rows are too many for a management summary, and decisions are usually taken per flow: keep it, extend it, rebuild it. The scorecard therefore needs one row per flow. SUMIFS does the roll-up. It adds the cells of a range for which a condition holds: =SUMIFS(sum_range, criteria_range, criterion). With the flow names listed in I4:I8, the recipients of the welcome flow are =SUMIFS($C$4:$C$16,$A$4:$A$16,I4): add the recipients in column C for every row whose flow in column A equals the name in I4.

The dollar signs make the two data ranges absolute, so they stay in place when the formula is copied down to the other flows, while I4 stays relative and moves to I5, I6 and so on. The revenue per flow uses the same pattern with column E as the sum range, and the flow RPR divides one by the other: =K4/J4.

FlowRecipients (J)Revenue (K)Flow RPR (L)Average of the email RPRs
Welcome11,850$13,553$1.14$1.11
Abandoned cart6,900$18,462$2.68$2.56
Browse abandonment9,900$4,337$0.44$0.43
Post-purchase8,750$5,135$0.59$0.60
Replenishment3,250$8,285$2.55$2.46
Total40,650$49,772$1.22

Revenue per recipient by flow, October 2026Abandoned cart$2.68Replenishment$2.55Welcome$1.14Post-purchase$0.59Browse abandonment$0.44All flows: $1.22Revenue per recipient in $ (attributed revenue ÷ delivered emails)
Figure 2: The scorecard from the lab as a chart. The cart and replenishment flows earn more than twice the all-flow average per delivered email.

The abandoned-cart flow leads with $2.68 per recipient, closely followed by replenishment with $2.55. Both are triggered by strong buying signals: a filled cart, or a product that is nearly used up. The welcome series sits near the all-flow average of $1.22. Browse abandonment ($0.44) and post-purchase ($0.59) earn the least per delivery, which fits their weaker triggers and, for post-purchase, the fact that two of its three emails are not sales emails at all.

Why you must not average the email RPRs

A tempting shortcut is to average the RPR column per flow. The last column of the scorecard table shows what that gives. For the abandoned-cart flow the plain average of the three email RPRs is $2.56, but the true flow RPR is $2.68. The average is too low because it gives the third email, which reaches only 2,050 people, the same weight as the first one with 2,600. For the post-purchase flow the error goes the other way: $0.60 instead of $0.59.

The differences look small here because the emails of a flow have similar audience sizes. They become large as soon as the sizes differ, for example when a fourth email goes only to a small segment, or when you average across flows: the plain average of the five flow RPRs is $1.48, far from the correct all-flow figure of $1.22. The rule is simple and applies to every rate in this course: add up the numerators, add up the denominators, then divide. A ratio of sums is always weighted correctly; an average of ratios almost never is.

RPR is efficiency, revenue is contribution

A scorecard with only RPR would rank browse abandonment last and suggest switching it off. That would be a mistake. RPR measures how much each delivery earns, which is the efficiency of an email. The revenue column measures how much the flow adds to the month, its contribution. A flow with a low RPR and a very large audience can contribute more than a flow with a high RPR that hardly ever fires.

Share of flow emails vs share of flow revenueShare of recipientsShare of revenueWelcome29.2%27.2%Abandoned cart17.0%37.1%Browse abandonment24.4%8.7%Post-purchase21.5%10.3%Replenishment8.0%16.6%
Figure 3: Browse abandonment sends 24.4% of the flow emails and earns 8.7% of the revenue; the cart flow does the reverse.

At Quillmoor Tea Co. the cart flow sends 17.0% of the flow emails and earns 37.1% of the flow revenue. Browse abandonment sends 24.4% of the emails for 8.7% of the revenue. Both facts matter. The first says where an improvement of one percent is worth the most money; the second says where a subscriber's patience is being spent for little return, a question lesson 4 answers with unsubscribe rates.

One more distinction prevents confusion later. The RPR in this lesson is per delivered email. A subscriber who enters the welcome series receives up to three emails and is therefore counted up to three times in the recipients. If you divide the flow revenue by the number of people who entered the flow instead, you get revenue per entrant, which is higher and answers a different question: what is one new subscriber worth to the welcome series? Lesson 2 uses that view. Neither is wrong; just label the column clearly.

Step by step in Excel

  1. Export one row per flow email from your email tool with the flow name, the email name, delivered emails, orders and attributed revenue. Paste it so that the headers are in row 3 and the data starts in row 4.
  2. Click F4, type =E4/C4 and press Enter. Select F4 and double-click the small square at the bottom right corner of the cell to copy the formula down to the last row.
  3. Click G4, type =D4/C4, copy it down and format the column as a percentage with one decimal.
  4. List each flow name once in I4:I8. The spelling must match column A exactly, including spaces; a trailing blank is the most common reason for a SUMIFS result of zero.
  5. In J4 type =SUMIFS($C$4:$C$16,$A$4:$A$16,I4). Press F4 after selecting a range to add the dollar signs (Mac: Cmd + T). Copy the formula down to J8.
  6. In K4 type =SUMIFS($E$4:$E$16,$A$4:$A$16,I4) and copy it down.
  7. In L4 type =K4/J4 and copy it down. This is the flow RPR.
  8. Check the totals: =SUM(J4:J8) must equal =SUM(C4:C16) (40,650), and =SUM(K4:K8) must equal =SUM(E4:E16) ($49,772). If they differ, a flow name is misspelled or missing from the list.
The total check in the last step is worth keeping in the sheet permanently. When somebody adds a sixth flow to the email tool next spring, the export will contain rows that no line of your scorecard picks up, and the check is what tells you.

Common mistakes and how to spot them

  • Dividing by orders instead of recipients. =E4/D4 is the average order value, around $52 here. If every value in your RPR column is in the tens of dollars, you divided by the wrong column.
  • Upside-down ratio. =C4/E4 returns recipients per dollar. Values that rise when an email gets worse are the warning sign.
  • Averaging rates. AVERAGEIFS over the RPR column weights a small email like a large one. Use the ratio of two SUMIFS.
  • Unlocked ranges. =SUMIFS(C4:C16,A4:A16,I4) works in the first row and silently loses rows as it is copied down, because the ranges slide to C5:C17, C6:C18 and so on.
  • Mixing sent and delivered. If recipients are delivered emails in one month and sent emails in the next, the RPR moves although nothing changed.
  • Comparing across attribution rules. An RPR measured with a five-day click window cannot be compared with one from a tool that also credits orders after an open. Note the rule next to the table.

How to read the scorecard, and what it cannot tell you

A flow scorecard is a starting point for questions, not a ranking of winners and losers. A high RPR says that the people who receive this email often buy afterwards. It does not say that they buy because of the email. Somebody who leaves a cart with three teas in it is quite likely to come back on their own; the reminder may only be standing in the doorway when they return. How much of the attributed revenue is truly caused by a flow can only be measured with a holdout group, the subject of lesson 11.

  • Is the trigger volume as expected? 4,200 first welcome emails mean roughly 4,200 new subscribers in the month. A sudden drop usually points to a broken signup form, not to a weak email.
  • How steep is the fall inside the flow? If the second email earns almost nothing, its timing or content is worth a test (lesson 8). If the last email still earns well, the flow may be too short (lesson 14).
  • Which flow has room to grow? The cart flow can only reach shoppers whose address is known. Raising that reach is often worth more than polishing the copy (lesson 3).
  • What does it cost? Revenue is not margin, and a flow that owes its RPR to a discount code may earn less than it seems (lesson 16).
There is no universal "good" RPR. It depends on prices, margins, the product category, the attribution window and how often customers buy. Compare a flow with its own past, with the other flows in the same account and with a holdout group, and treat published benchmarks as illustrative.

Quick reference: functions in this lesson

FunctionWhat it does hereExample
DivisionRevenue per recipient of one email=E4/C4
DivisionPlaced-order rate of one email=D4/C4
SUMIFSRecipients of all emails of a flow=SUMIFS($C$4:$C$16,$A$4:$A$16,I4)
SUMIFSRevenue of all emails of a flow=SUMIFS($E$4:$E$16,$A$4:$A$16,I4)
Ratio of sumsFlow RPR, weighted correctly=K4/J4
SUMTotals for the all-flow average=SUM(E4:E16)/SUM(C4:C16)
$ (absolute reference)Keeps the data ranges fixed when the formula is copied down$A$4:$A$16

Real-world uses

  • Monthly flow review. Paste the new export, let the formulas recalculate and compare each flow RPR with the previous month. Ten minutes are enough to notice a flow that has quietly stopped working.
  • Deciding what to improve first. Multiply a realistic RPR improvement by the flow's recipients: ten cents more on 9,900 browse emails is about $990 a month, ten cents more on 3,250 replenishment emails only $325.
  • Reporting to management. Five rows with recipients, revenue and RPR fit on one slide and can be explained in a minute.
  • Agency and freelance work. The same scorecard, built from a client's export, is a fast first audit of an email account before any flow is touched.

What you will build in the rest of this course

Lesson 1 gives you the scorecard. The other nineteen labs take each flow apart, test it and put the pieces back together into an annual dashboard. Each lab has its own data set from Quillmoor Tea Co. and every cell is checked as you type.

  • The five flows in depth (lessons 2 to 6). Subscriber-to-customer rate of the welcome series by signup source; reach rate, recovery rate and margin per recipient of the cart flow; a keep-or-review rule for browse abandonment with unsubscribes; review and repeat rates after the first order with XLOOKUP and IFS; run-out and reminder dates for replenishment.
  • Share and timing (lessons 7 and 8). Flow share of email revenue and of store revenue over twelve months in a stacked chart, then timing tests: revenue per recipient for three send delays per email and the lift against the current timing.
  • Quality and measurement (lessons 9 to 11). Entry filters for consent, purchases and cool-downs; the attribution window that covers 90% of the orders; holdout groups and the share of flow revenue that is truly incremental.
  • Planning and what-ifs (lessons 12 to 14). Forecasting flow revenue from trigger volume with SLOPE and FORECAST.LINEAR; a discount-by-recovery-rate grid with a heat map; the net value of each extra email once unsubscribes are counted.
  • Segments, discounts and overlap (lessons 15 to 17). An RPR matrix by flow and customer segment; margin per recipient with and without a code; emails per subscriber per week against a frequency cap.
  • Intervals, priorities and the final project (lessons 18 to 20). Replenishment intervals from real reorder gaps with the median; ranking a backlog of flow ideas by incremental revenue per build hour; an annual flow dashboard with a flag rule and a combo chart.

Summary

Automation flows are emails that customer behaviour triggers, and they deserve a scorecard of their own. Revenue per recipient, =E4/C4, puts every flow email on one scale; the placed-order rate, =D4/C4, explains part of it. SUMIFS rolls the emails up into flows, and the flow RPR is the ratio of the two sums, never the average of the email RPRs. At Quillmoor Tea Co. the abandoned-cart flow earns $2.68 per recipient and browse abandonment $0.44, while all 13 emails together earn $1.22. Read efficiency and contribution side by side, write down the attribution rule, and keep in mind that attributed revenue is not yet incremental revenue. Try the lab above: the Coach checks each formula as you enter it.

Frequently asked questions

What is an email automation flow?

A flow is a sequence of emails that is triggered by something a customer does, such as subscribing, leaving a cart, viewing a product or placing an order, or by a calculated date such as an expected run-out. Unlike a campaign it is sent to one person at a time, automatically, whenever the trigger occurs.

How do I calculate revenue per recipient?

Divide the revenue attributed to an email by the number of emails delivered. In a spreadsheet with revenue in column E and recipients in column C the formula is =E4/C4. For a whole flow, add up revenue and recipients of all its emails first and then divide.

Why should I not average the RPR of the emails in a flow?

The emails of a flow reach different numbers of people. A plain average gives a small email the same weight as a large one and distorts the result. Dividing the summed revenue by the summed recipients weights every email by its real size.

Which flow usually has the highest revenue per recipient?

Flows triggered by strong buying intent, such as abandoned-cart and replenishment reminders, usually earn the most per delivered email. In the fictional example of this lesson they earn $2.68 and $2.55 per recipient. Actual values depend on the shop, the prices and the attribution rule.

Is flow revenue the same as incremental revenue?

No. Attributed revenue counts orders that followed an email. Some of those customers would have ordered without it. Only a comparison with a holdout group that receives no flow emails shows how much revenue the flow really caused.

What is the difference between RPR per email and revenue per person entering a flow?

RPR per email divides by delivered emails, so a person who receives three emails is counted three times. Revenue per entrant divides the flow revenue by the people who entered the flow once. The second number is higher and answers what one triggered person is worth.

Keep going: Email Automation Flows: Welcome Series, Abandoned Cart, Browse Abandonment, Post-Purchase & Replenishment, Revenue per Recipient, Timing Tests & Flow Share

This free lab is lesson 1 of 20. Unlock the other 19 hands-on labs, the final exam and your certificate for a one-time $9.90.

  1. The Welcome Series: First Orders per Email, Subscriber-to-Customer Rate and Revenue per Subscriber by Signup Source
  2. The Abandoned-Cart Flow: Reach Rate, Recovery Rate and Margin per Recipient After the Discount
  3. Browse Abandonment: RPR by Category, an Index Against the Flow Average and a Keep-or-Review Rule with Unsubscribes
  4. The Post-Purchase Flow: Review Rate, 60-Day Repeat Rate, a Target per Product Type with XLOOKUP and a Status with IFS
  5. Replenishment Reminders: Days of Supply, Run-Out Date, Reminder Date and a Send-Now Status with Date Arithmetic
  6. Flow vs Campaign Share: Flow Share of Email Revenue, Email Share of Store Revenue and the RPR Gap in a Stacked Chart
  7. Timing Tests: RPR per Send Delay, Lift Against the Current Timing with SUMIFS and the Winning Variant per Flow
  8. Flow Entry Filters: Consent, Already Purchased, Cool-Down and Minimum Cart Value in One Send-or-Skip Rule
  9. Time to Convert: Daily and Cumulative Share of Flow Orders and the Attribution Window That Covers 90%
  10. Is the Flow Revenue Incremental? Holdout Groups, Incremental RPR, Incremental Revenue and the Share That Would Have Come Anyway
  11. Forecasting Flow Revenue from Trigger Volume: Revenue per New Subscriber, SLOPE, FORECAST.LINEAR and R²
  12. What-If Grid: Margin per 1,000 Cart-Flow Recipients for Every Discount and Recovery Rate, a Heat Map and the Break-Even Rate
  13. How Long Should a Flow Be? Net Value per Email After Unsubscribes, a Keep-or-Cut Rule and the Cumulative Revenue Curve
  14. Flows by Customer Segment: an RPR Matrix with Two-Criteria SUMIFS, the Repeat-to-Prospect Ratio and Each Segment's Share of Recipients
  15. Discounts in Flows: Margin per Recipient With and Without a Code, the Gain per Email and the Emails Where the Code Loses Money
  16. When Flows Collide: Emails per Subscriber in 7 Days, a Frequency Cap, the Share Over the Cap and the Emails to Hold Back
  17. Replenishment Intervals from Real Reorder Gaps: Average vs Median per Product, the Reminder Day and Who Reorders Before It
  18. Prioritising the Flow Backlog: Incremental Revenue per Build Hour, a Rank, Cumulative Hours and a Build-or-Later Decision
  19. Final Project: the Annual Flow Dashboard with Revenue, RPR and Share per Flow, Flow Share of Email Revenue, a Flag Rule and a Combo Chart

Buy course — $9.90 See the full course