Zum Inhalt springen
NeuSo funktioniert es
Fehlerbehebung

Open, click, and unsubscribe tracking restored

Open and click tracking — and one-click unsubscribe — are reliable again for every campaign, including those on our shared tracking domain. We've also added always-on monitoring so any future hiccup is caught within minutes.

Accurate engagement data is the backbone of good outreach — it tells you what's landing, drives reply detection, and powers Self Learning AI. We found and fixed an issue that could leave some of that data under-reported, and added monitoring so it can't slip by unnoticed again.

What happened

Campaigns using our shared tracking domain — the default for workspaces that haven't configured a custom tracking subdomain — could intermittently fail to record opens and clicks. One-click unsubscribe links on those emails could also fail to load. Campaigns running on a verified custom tracking domain were unaffected; their certificates were already in place and working correctly.

The failure was silent from your side: campaigns kept sending, and the analytics page kept showing numbers — just numbers that were lower than they should have been. Opens that happened weren't recorded. Clicks that were real went unlogged. For campaigns relying on open and click signals to trigger follow-up steps or feed Self Learning AI, that missing data meant the system was making decisions on an incomplete picture.

What's fixed

The root cause was a certificate and TLS handshake gap on the shared tracking host. It's resolved: the shared host now provisions and serves a valid certificate, and we verified end to end that the tracking pixel, click redirects, and unsubscribe links all respond correctly over HTTPS.

Engagement that occurred during the affected window can't be backfilled, but everything sent from the fix forward is captured normally — your reporting reflects real activity again.

If you use a custom tracking domain, you can confirm its health any time under Tracking Domains — a fully verified domain shows green CNAME, SSL, and HTTPS checks. If any check shows amber or red, that's your signal to investigate before the next campaign send.

What's new: always-on monitoring

Fixes that only correct a known failure leave you exposed to the next unknown one. So alongside the certificate fix, we added synthetic health checks that probe the tracking endpoint continuously from multiple regions. If the tracking host ever degrades again — a certificate renewal gap, a routing issue, a provider hiccup — it's detected within minutes and the self-healing process kicks in automatically.

This is a material change in how tracking reliability is managed. Previously, a degradation could persist undetected until enough data was missing to notice in analytics. Now, the monitoring catches it before it affects more than a handful of sends.

Why tracking data matters beyond the dashboard

Open and click data isn't just a reporting metric. It feeds reply detection — which determines when a contact exits a sequence because they responded — and for AI Autopilot campaigns, it's part of the signal that Self Learning AI uses to continuously improve your copy. Gaps in that data slow down learning and make your campaign analytics harder to act on. A week of under-reported opens doesn't just affect your open rate; it affects every ratio and decision built on top of it.

What you should do

Nothing is required. Tracking works across all campaigns going forward. For the strongest deliverability and fully branded tracking links, consider adding a custom tracking domain under Tracking Domains — it's a single CNAME record and gives you a dedicated certificate and full independence from shared infrastructure.

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.