„Calendly already shows where bookings came from.“
It does, well. It does not show which of those bookings paid, because it never sees a sale.
Für Calendly
Export your Calendly invitees, upload your closed sales beside them, and find out which bookings turned into money.
Kein API-Schlüssel Nichts in Calendly zu installierenNichts zu installieren Keine Karte nötigOhne Karte
CloseRev reads a Calendly export of scheduled events — the invitee's email, the meeting date and whatever UTM or routing information came with the booking — and matches those invitees against your closed-sales export. Calendly answers who booked a meeting and where they came from; this answers which of those meetings produced revenue, which no scheduling tool can see. Meetings that produced nothing simply do not appear in the revenue column.
Zuletzt am 24. September 2026 anhand der eigenen Dokumentation von Calendly geprüft.
Die Lücke
The calendar is full, which everyone treats as success. Nobody can say which of those meetings were worth having, or which advert produced them.
Was verkauft wurde, an wen und für wie viel.
Der Klick, das Keyword, der Anruf und was jedes davon gekostet hat.
Die Datei
Drei Dinge tragen die Zuordnung: wer, wie viel und wann. Alles andere ist optional und ändert nur, wie sich der Bericht aufschlüsseln lässt.
On the scheduled event. Calendly is email-first and this column is always populated, which makes it one of the cleanest lead files available.
When the meeting was booked, or when it was held. Booked date sits closer to the marketing that produced it.
Calendly carries the UTM parameters from the link that was clicked. This is the attribution and it is why the export is worth having.
Which meeting type was booked, and any qualifying question answered at booking. Both split a channel's bookings into ones worth having and ones not.
Schritt für Schritt
Geschrieben für alle, die Calendly im Nachbar-Tab geöffnet haben. Berichtsnamen unterscheiden sich je nach Edition, deshalb sagt jeder Schritt, wonach Sie suchen.
One row per booking with the invitee email, the date and whatever UTM or routing fields were captured. Those tracking fields are the whole value of this file.
They are bookings a channel produced and meetings nobody had. A channel with a high no-show rate is more expensive than its booking count suggests, and this is the only place that shows.
From the CRM, the ledger or the practice system — whatever holds the money. Customer email, amount, date.
The meeting comes first and the money later. How much later depends on what you sell, and the sales file should reach past it.
The join is the email, normalised on both sides, with bookings that produced nothing reported as exactly that.
Was zurückkommt
Umsatz nach Kanal, die Zahl der Verkäufe hinter jedem Wert und eine ehrliche Kategorie für alles, was niemand zuordnen konnte. Beispielzahlen aus dem durchgerechneten Beispiel der Seite B2B SaaS – nicht aus einem Calendly-Konto.
| Kanal | Anteil | Verkäufe | Umsatz |
|---|---|---|---|
| Google Ads | 18 | $720,000 | |
| LinkedIn Ads | 21 | $930,000 | |
| E‑Mail-Marketing | 12 | $420,000 | |
| Direkt / Unbekannt | 24 | $930,000 |
Nicht zugeordnete Verkäufe bleiben unter Direkt / Unbekannt. Sie werden nie auf die bezahlten Kanäle verteilt, damit die Summe besser aussieht.
Das Argument
Booked meetings are countable, immediate and satisfying. Every advertising platform will happily report them as conversions, and every team treats the calendar filling up as the campaign working.
The show rate and the close rate behind those bookings vary enormously by channel. A channel producing cheap bookings from people browsing at midnight and a channel producing fewer bookings from people with budget approval look identical on a calendar.
Ranking on closed revenue instead usually reorders the channels, and the reorder is largest exactly where the booking cost is lowest — which is the opposite of what the optimisation assumed.
Most lead capture loses the marketing context somewhere between the click and the record. Calendly keeps the UTM parameters from the link the invitee clicked and carries them onto the booking.
That makes its export an unusually clean lead file: an email address that is always present, a date, and a source that came from the link rather than from somebody's memory.
What it cannot do is look forward. It has no idea whether the meeting happened, how it went, or whether the invitee ever paid — those live in a different system entirely, which is the gap this closes.
Show rates differ by source in a consistent and explainable way. Somebody who booked after reading a case study shows up; somebody who booked from an interstitial advert at the end of an article frequently does not.
Because no-shows produce no revenue and no record anywhere except the calendar, they are invisible in every downstream report. The channel that produced them looks merely mediocre rather than expensive.
Including cancellations and no-shows in the export puts the cost back where it belongs. For teams paying per booking it is often the single largest correction the report makes.
Most teams add a question or two at booking — company size, budget, timeline, what prompted the enquiry. They are used to prioritise and they are rarely validated.
Putting the answer beside the revenue that invitee eventually produced tests it directly. Sometimes the question is doing real work; sometimes it is sorting meetings by nothing at all, and the team has been prioritising on noise for a year.
Berechtigte Fragen
It does, well. It does not show which of those bookings paid, because it never sees a sale.
Then split those out. Otherwise marketing is judged against meetings it never produced.
Then start — it costs nothing and it is the field that makes this export worth exporting. Until then the match still works on the email and the source is just coarser.
No. It reads a file you exported, so your calendar itself — who you are meeting and when — is never accessible to it.
Scheduled events with the invitee email, the date and whatever UTM or tracking fields were captured.
Yes. They are bookings a channel produced and revenue it did not, and they are invisible everywhere else.
Closed sales from wherever your money is recorded — CRM, ledger or practice system.
On the email address, normalised on both sides. Calendly always has one, which makes this a clean join.
Yes, where the export carries one. A demo and a discovery call convert very differently and are usually produced by different channels.
Yes, by putting the answers beside the revenue. It is a cheap way to find out whether a question predicts anything.
Past the booking file by whatever your sales cycle is, with room to spare.
The link is weaker and it is flagged for a person rather than counted automatically.
Yes. Any tool exporting an invitee email with a source works identically.
An email, a date and the tracking fields. No meeting notes, no recordings, no calendar contents, no answers you did not include. Encrypted in transit and at rest and deleted with the import.
Revenue by source from booked meetings, show and conversion rates by source, and everything unmatched kept visible.
Nach Branche
Wie der Bericht aussieht, sobald der Export drin ist – für jede Branche eigens geschrieben.
Andere Systeme
Mehrere Systeme im Einsatz oder im Vergleich? Die Methode ist dieselbe, die Spalten sind es nicht.
Calendly und die anderen Produktnamen und Logos auf dieser Seite gehören ihren Inhabern und dienen nur dazu, die Software zu kennzeichnen, aus der eine Datei stammt. CloseRev ist mit ihnen nicht verbunden oder von ihnen empfohlen und verbindet sich mit keinem davon: CloseRev liest eine Datei, die Sie exportieren.
Heute starten
Nichts in Calendly zu installieren, kein API-Schlüssel, und Sie müssen bisher nichts getrackt haben. Das Vorjahr funktioniert so gut wie dieser Monat.