What the campaign funnel shows, cross-posts included
For authorsUpdated 1 min read
Studio, Analytics, Campaign funnel counts every stage of a campaign: Applications, Approved, Downloaded (an approval, a delivery-link claim or a certified send each count as one reader), Reviewed, Cross-posted (as readers mark them, with a line per site), Kept following, with lines for DNF and held reviews. Counts, never names, each with its definition on the page. A giveaway has no funnel.
The short answer
The stages
Studio › Analytics › Campaign funnel, per campaign and across all of them:
- Applications: everyone who requested.
- Approved: the applications you accepted.
- Downloaded: every reader who fetched the copy (opened it on a read-on-Booklabria campaign). An approval, a delivery-link claim and a certified send each count as one reader, and that is also what counts toward your plan's readers per campaign.
- Reviewed: reviews posted, with a DNF line for readers who said so, and a held line for reviews waiting for the release day on a coming-soon book.
- Cross-posted: readers who marked a cross-post from My requests, on campaigns that list the requirement, with a line per site under it (8 on Amazon · 3 on Goodreads · 1 elsewhere). Booklabria does not check the other site; the mark is the reader's, and you see it beside their record (cross-posted {n} times), never in their reliability score.
- Kept following: reviewers who follow your pen name after the campaign.
A giveaway has no funnel: its entries and wins show on the campaign's Activity and in the Reader spots block (Giveaway campaigns).
Where else it shows
- Each Applications row carries one chip per site the reader marked, Cross-posted · {site}, with the link behind it; a row with a review waiting for launch reads Reviewed, held, and a held chip beside the funnel counts them.
- The book page shows {n} reviews held until {date}, never their text, until the release day.
Every column names its definition on the page; when there is not enough to say something honestly, the screen says so rather than guessing.
Where this lives
Related
- Understanding your analytics: Studio, Analytics answers one question per chart in plain words: followers (exact and current), monthly readers (people who took a reading action in the last 30 days), monthly reach (people who saw your profile or posts), the campaign funnel, posting cadence and what lands. Audience shows recent followers, the tastes they chose to make public, and your e-mail list with its export history. Aggregated nightly; no sales figures, nothing faked.
- ARC delivery and tracking: You choose per campaign how readers receive the book: Read on Booklabria (the file stays on the server, readers open it on the site or in the app, and the Reading tab shows progress by chapter, who finished and where readers stop, as counts) or Download a protected copy (signed links that expire after fifteen minutes, five downloads per approval, every EPUB watermarked). Upload the EPUB or PDF on the Delivery tab; reading on Booklabria needs the EPUB. The Activity tab notes approvals, downloads and reviews as they happen; the analytics funnel shows how many downloads became reviews.
- Cross-posting your review, and telling the author: Some campaigns ask you to cross-post your review to a retailer or review site. Once you have, mark it from My requests: pick the site (Amazon, Goodreads, BookBub, or another) and paste the link. Booklabria does not check the other site; the mark is yours, and the campaign owner sees it beside your record and in their funnel. Cross-posts never move your ARC reliability score.
- Reviews held until launch: On a coming-soon book, a review written from an ARC is held and published on the release day, together with every other held review. The reader is told the date when they post and again when it goes live; the author's Applications count them as held and the book page shows how many are waiting, never the text. Nothing is read by anyone but the reviewer before that day.
- Running an ARC campaign: Studio, Campaigns, New campaign walks through the book, dates and reader spots, ideal readers (genres, tropes, languages, regions, requirements), delivery (formats, files, your message) and how to launch (draft, scheduled, or now). Applications gather under Applications with each reader's match and reliability; approve or decline one by one or in batches, and every decision notifies the reader.
Was this helpful?
Still stuck?
Still stuck? Ask Booklabria AI
It reads this article and the ones around it, and cites its source.
Write to a person
Support reads every note, with this article attached so the team knows what you already read.
Contact support