How a publisher found $5,330 a day in missing ad revenue, with one question
This publisher sends 20 million emails a day. tinyEmail's MCP Server connects Claude or ChatGPT to its tinyEmail account. For the publisher, that meant seeing daily sends next to LiveIntent ad revenue, catching the gaps, and getting a summary leadership could act on before the next send.
21.4M emails sent, $38,520 in ad revenue, $1.80 per 1,000 emails.
Local Headlines went to 2.6M people with no ad tag. About $5,330 in revenue wasn't counted.
Two reports that never quite agree
The publisher sends six newsletters a day to more than 20 million people. Every email carries ads from LiveIntent, and those ads pay the bills. tinyEmail knows what was sent and to whom. LiveIntent knows how many ads were seen, clicked and paid for. Nobody could see both at once.
So every morning, someone on the ad team rebuilt the picture by hand. When a newsletter went out without its ad tag, the money it should have made simply didn't show up, and there was nothing in either report to say so.
- 7:30Export yesterday's sends from tinyEmail
- 7:50Download the LiveIntent revenue report
- 8:10Match campaign names across two spreadsheets, row by row
- 9:40Chase the rows that don't line up
- 10:45Write the update for leadership. The day's first send has already gone out.
They asked their assistant instead
Once the MCP Server is connected, Claude or ChatGPT works directly with the publisher's tinyEmail account: every campaign, newsletter, tag and send. The team asks one question in plain English, and the assistant puts sends and LiveIntent revenue side by side. Newsletter ad revenue reporting becomes a conversation.
“Compare yesterday's tinyEmail sends with LiveIntent impressions and revenue. Show volume, impressions, clicks, and revenue by newsletter, campaign, tag, and date. Work out revenue per 1,000 emails. Flag missing tags or numbers that don't match, then write a short summary for leadership with recommended actions.”
Every view the spreadsheet used to give, and a few it couldn't
Revenue per 1,000 emails is the number that ties sending to earning. It shows which newsletters pay their way and which ones quietly stopped.
| Newsletter | Emails sent | Impressions | Clicks | Revenue | Per 1,000 emails |
|---|---|---|---|---|---|
| Morning Brief | 6,200,000 | 4,650,000 | 13,020 | $14,260 | $2.30 |
| Evening Edition | 4,100,000 | 2,870,000 | 8,040 | $8,610 | $2.10 |
| Health & Living | 1,800,000 | 1,250,000 | 3,160 | $3,500 | $1.94 |
| Markets Close | 3,800,000 | 2,470,000 | 7,410 | $7,220 | $1.90 |
| Sports Daily | 2,900,000 | 1,740,000 | 5,570 | $4,930 | $1.70 |
| Local HeadlinesNo ad tag | 2,600,000 | 0 | 0 | $0 | $0.00 |
| All newsletters | 21,400,000 | 12,980,000 | 37,200 | $38,520 | $1.80 |
| Campaign | Emails sent | Impressions | Clicks | Revenue | Per 1,000 emails |
|---|---|---|---|---|---|
| Morning Brief · East | 3,400,000 | 2,570,000 | 7,210 | $7,890 | $2.32 |
| Morning Brief · West | 2,800,000 | 2,080,000 | 5,810 | $6,370 | $2.28 |
| Evening Edition · 9 PM | 4,100,000 | 2,870,000 | 8,040 | $8,610 | $2.10 |
| Health & Living · Daily | 1,800,000 | 1,250,000 | 3,160 | $3,500 | $1.94 |
| Markets Close · 4:30 PM | 3,800,000 | 2,470,000 | 7,410 | $7,220 | $1.90 |
| Sports Daily · Scores | 2,900,000 | 1,740,000 | 5,570 | $4,930 | $1.70 |
| Local Headlines · MetroNo ad tag | 1,500,000 | 0 | 0 | $0 | $0.00 |
| Local Headlines · SuburbsNo ad tag | 1,100,000 | 0 | 0 | $0 | $0.00 |
| All campaigns | 21,400,000 | 12,980,000 | 37,200 | $38,520 | $1.80 |
| Tag | Emails sent | Impressions | Clicks | Revenue | Per 1,000 emails |
|---|---|---|---|---|---|
| news | 10,300,000 | 7,520,000 | 21,060 | $22,870 | $2.22 |
| lifestyle | 1,800,000 | 1,250,000 | 3,160 | $3,500 | $1.94 |
| finance | 3,800,000 | 2,470,000 | 7,410 | $7,220 | $1.90 |
| sports | 2,900,000 | 1,740,000 | 5,570 | $4,930 | $1.70 |
| (no ad tag)Revenue not credited | 2,600,000 | 0 | 0 | $0 | $0.00 |
| All tags | 21,400,000 | 12,980,000 | 37,200 | $38,520 | $1.80 |
| Date | Emails sent | Impressions | Clicks | Revenue | Per 1,000 emails |
|---|---|---|---|---|---|
| Tue, Sep 22Tag missing | 21,400,000 | 12,980,000 | 37,200 | $38,520 | $1.80 |
| Mon, Sep 21Tag missing | 21,310,000 | 13,050,000 | 37,500 | $38,990 | $1.83 |
| Sun, Sep 20 | 20,870,000 | 14,420,000 | 42,900 | $43,410 | $2.08 |
| Sat, Sep 19 | 21,290,000 | 14,700,000 | 42,600 | $43,640 | $2.05 |
| Fri, Sep 18 | 21,020,000 | 14,500,000 | 41,800 | $42,460 | $2.02 |
| Thu, Sep 17 | 21,350,000 | 14,780,000 | 43,100 | $44,190 | $2.07 |
| Wed, Sep 16 | 21,180,000 | 14,610,000 | 42,300 | $43,210 | $2.04 |
| 7-day total | 148,420,000 | 99,040,000 | 287,400 | $294,420 | $1.98 |
Three gaps the spreadsheet never showed
The assistant checks every tinyEmail send against LiveIntent's numbers, so mismatches come to the top instead of hiding in row 4,000 of a spreadsheet.
Missing ad tag
Local Headlines went to 2.6 million people on Sep 21 and 22 with no LiveIntent tag, after a template update. None of its ad revenue could be credited. At the rate the other newsletters earn ($2.05 per 1,000), that's about $5,330 a day.
Reports close the day at different times
Evening Edition goes out at 9 PM Eastern. LiveIntent's report ends its day at 8 PM Eastern, so those ads landed on the next day's numbers. The assistant moved them back so each day's revenue matches that day's sends.
Revenue with no matching send
410,000 impressions in the LiveIntent report used a campaign name that doesn't exist in tinyEmail. It matches an old test newsletter, which suggests an outdated tag is still live in one template.
A leadership update, written before 8:05 AM
The same conversation ends with a summary the team can paste straight into Slack or email. No reformatting, no second pass.
We sent 21.4M emails and earned $38,520 in ad revenue, or $1.80 per 1,000 emails. That's 12% below last week's $2.05. Nearly all of the drop comes from one newsletter going out without its ad tag.
Morning Brief is our best earner at $2.30 per 1,000 emails. Evening Edition follows at $2.10.
- 1Add the ad tag back to Local Headlines before today's send. Recovers about $5,330 a day.
- 2Remove the old test tag from the template it's still in. $610 a day is landing against a newsletter we no longer send.
- 3Report both sources on Eastern Time. Evening Edition's revenue will stop appearing on the wrong day.
- 4Check every template for its ad tag after any design change. Ask the assistant for a tag check before sends go out.
Reporting went from a chore to a check-in
Before
- Two exports and a spreadsheet, every morning
- Campaign names matched by hand
- Missing tags found at month-end, if at all
- Leadership update ready mid-morning
With tinyEmail MCP
- One question in Claude or ChatGPT
- Sends and revenue lined up automatically
- Missing tags flagged the morning after
- Summary with actions ready in minutes
Questions publishers ask next
- Which newsletter earned the least per 1,000 emails this week, and why?
- Check every scheduled campaign for a missing LiveIntent tag before it sends.
- Compare this month's revenue per 1,000 emails with last month, by newsletter.
- Which tags drive the most ad clicks per email sent?
- Show every day this month where impressions dropped but sends didn't.
- Write this week's revenue summary for our leadership meeting.
Three steps, about five minutes
- 1
Get your API key
In tinyEmail, go to Account Settings › API Keys. It's the secure pass your assistant uses, and it's never stored.
- 2
Connect Claude or ChatGPT
Add tinyEmail in Claude Desktop or Claude Code with your API key. In ChatGPT, turn on Developer Mode and connect the tinyEmail app.
- 3
Just ask
Use the daily revenue report prompt above, or ask your own question in plain language. Your assistant does the rest.
tinyEmail MCP questions
Can't find your answer? Our team is here 24/7.
What can I ask about my newsletters?
Anything you'd normally pull a report for: how a campaign performed, which newsletter earns the most per 1,000 emails, which sends are missing a tag, or which audience to send to next. Your assistant answers from your live tinyEmail account.
Is my account secure?
Yes. Your API key goes straight from your assistant to tinyEmail. The MCP Server never stores or logs it.
Do I need a developer?
No. Setup is a one-time step in Claude or ChatGPT, and the tutorial walks you through it. After that, you ask questions in plain language.
Which assistants work with it?
Claude Desktop, Claude Code and ChatGPT.
Who can use the MCP Server?
It's available to tinyEmail Enterprise customers. Contact your account team or support through in-app chat to get started.
Find tomorrow's lost revenue this morning
If you haven't set up the tinyEmail MCP yet, watch the tutorial to connect it to ChatGPT or Claude Code and start using it today.