Zum Inhalt springen
NeuSo funktioniert es
Fehlerbehebung

Accurate Delivered numbers in campaign analytics

A campaign's Delivered figure and its “Contacts who delivered” list now always agree. The count you see on the card is exactly the set of contacts you get when you click into it.

Your campaign analytics should tell one consistent story — the number shown on a summary card and the list of contacts behind it have to match. We found and fixed a case where the Delivered figure and its drill-down disagreed, so you can trust both again.

What happened

On a campaign's analytics page, the Delivered card and the Contacts who delivered panel could show different totals. The discrepancy had two causes working independently.

First, the card and the drill-down were using different definitions of "delivered." The card counted every contact who received at least one non-bounced email using a broader signal, while the drill-down applied a stricter criteria — so clicking into the number produced a shorter list than the headline suggested. This was confusing in the best case and actively misleading in the worst: you might act on a delivered figure that the underlying contact list didn't support.

Second, a failed send attempt on a later step in a multi-step sequence could wrongly drop a contact from the delivered count, even if an earlier step had already been delivered successfully. A contact who received your first email cleanly could disappear from the delivered count if their third follow-up hit a transient error — making the count shrink as a campaign progressed rather than holding steady or growing.

What's fixed

Both views now use the same correct definition: a contact is counted as delivered when they have at least one sent email on record and no hard or soft bounce against them. A failed send attempt on a later step no longer erases an earlier successful delivery from the count. The card and the drill-down are reconciled at the contact level — the total on the card equals the exact number of contacts in the list, every time. The same reconciliation logic applies to the Bounced count for consistency.

Why accurate delivered numbers matter

Delivered count is the denominator for every downstream metric in campaign analytics. Open rate is opens divided by delivered. Reply rate is replies divided by delivered. Cost-per-meeting traces back to how many contacts were actually reached. When the delivered count is inflated, understated, or inconsistent between views, every ratio built on top of it is distorted — and decisions made from those ratios are built on shaky ground.

A campaign that looks like it has a 20% open rate might actually have a 28% open rate once the delivered count is corrected downward. The difference between those two numbers can change how you evaluate a subject line, how you allocate budget across campaigns, and whether you decide to scale a sequence or retire it.

With the reconciliation in place, the analytics you use to judge a campaign's health are grounded in the same consistent data across every view. The number on the card is the count of contacts in the list — no arithmetic required, no discrepancy to explain.

What you should do

Nothing. Your Delivered and Bounced counts are accurate going forward, and clicking any analytics card shows the exact set of contacts behind it. If you have been manually reconciling these numbers as a workaround, you can stop — the source of truth is now the same in both places.

Alle Neuigkeiten

Akquise, die weiterläuft, wenn du offline bist.Leads, E-Mails, Follow-ups und Antworten, erledigt.

Verbinde unbegrenzte Postfächer und lass KI-Agenten Leads finden, jede E-Mail schreiben und nachfassen. Oder sende deine eigenen Vorlagen im manuellen Modus. Ab $29/Monat.

$1 für 3 Tage · Jederzeit kündbar · Kein Vertrag

Mit KI installieren

Dein Coding-Agent richtet die FirstSales CLI und Skills für dich ein.

Prompt für Claude Code

I'm setting up FirstSales (https://firstsales.io), an AI outbound sales platform: campaigns, contacts, a reply inbox, deliverability and lead signals. Help me get my workspace sending real, good emails end to end, from Claude Code.

Read these first so you know how FirstSales works:
- Developer docs and API: https://developer.firstsales.io
- CLI: https://www.npmjs.com/package/@firstsales.io/cli
- Skills for coding agents: https://github.com/firstsalesio/firstsales-skills (read README.md and GUIDE.md)

Setup
1. Install the CLI: npm install -g @firstsales.io/cli
2. Install the FirstSales skills:
   claude plugin marketplace add firstsalesio/firstsales-skills
   claude plugin install firstsales@firstsales
3. Ask me if I already have a FirstSales account. If not, send me to https://app.firstsales.io to sign up.
4. Ask me to create an API key under Settings → API → API Keys, with only the scopes we need.
   Never ask me to paste the key into this chat. Tell me to run this in my own terminal, so the key stays hidden:
   read -rs FS_KEY && firstsales auth login --api-key "$FS_KEY"; unset FS_KEY
5. Run `firstsales whoami` and tell me which workspace and organisation we are connected to.

Then ask me about my business: what I sell, who I sell to (roles, company size, countries), my best customers, and what I use today for outbound (tools, lists, mailboxes). Walk me through:
1. Teaching FirstSales my business: website, offer, proof points and case studies in the knowledge base, so the AI writes like someone who knows the product.
2. Connecting my sending mailboxes and checking my sending domain: SPF, DKIM, DMARC and warm-up. If anything is unhealthy, tell me the exact DNS record to add.
3. Bringing in contacts: import my CSV or CRM export into a clean list, remove duplicates and bad emails, and block domains I must never email (customers, competitors, my own).
4. Building my first campaign: the right list, senders, steps and timing. Write the sequence with me, show me the drafts, and do not launch until I say yes.
5. Setting up Signals if it fits: find people engaging with LinkedIn posts about topics my buyers care about, and turn them into leads.
6. Inviting my team and giving each person the right access.

Once campaigns run, show me how to work the reply inbox from here: which replies need an answer, draft responses in my voice, and move good conversations into deals. If I use Cal.com, connect it so follow-ups can offer my booking link (not the first email).

Throughout, as you learn about my business, proactively suggest and help create:
- Reply templates for the questions and objections my prospects are likely to raise, based on my product, site and codebase if you can see them.
- Campaign ideas and segments worth testing, with the reason for each.

Safety rules:
- Show every change as a dry run (--dry-run) first and wait for my yes. Never send emails, launch campaigns or delete anything without my yes.
- Tell me before anything that spends credits, and how many.

Be opinionated. If the docs give a sensible default, just use it. Don't make me choose between five options.