Several campaigns at once
For authorsUpdated 4 min read
On the Publisher plan, Studio, Campaigns lets you pause, resume, close and export up to 25 campaigns at once, decide the requests of every campaign of a pen name in one queue, and create campaigns for several books from one template. Every campaign, request and book answers for itself on its row. The export is one CSV of the approved readers and their reviews; a held review exports as held only, and review text, readers' notes, match scores and e-mail addresses are never in it. During the beta every author tool is unlocked, this one included.
The short answer
What it does
Studio › Campaigns lists the campaigns of a pen name with a box on each row. Choose several, and a bar offers Pause, Resume, Close and Export reviews (CSV). Beside it, Studio › Applications is one queue of every request waiting across the pen name's campaigns, and Several books, one template sets up a campaign for each of several books at once.
Every action takes Up to 25 at a time. With more chosen, the bar says Up to 25 at a time. Choose 25 or fewer and run the rest in a second batch., and nothing runs until you do. You can run ten batches in a row, then six a minute; past that the answer is Too many batches at once. Wait a minute.
Each one answers for itself
A batch is never all or nothing. Each campaign, request or book is done on its own, and each row says what happened to it: Paused, Resumed, Closed, Approved, Declined, Created, or Refused with the reason. A heading counts the results, for example 2 paused, 1 refused. Nothing is skipped without a word, and a row that was not in the batch says so.
- Pause works on an open campaign, Resume on a paused one, and Close on either. A campaign in any other state is refused on its row, with the reason.
- Close asks first, because it cannot be undone: no new applications, and the campaign stops showing as open. Readers who already have the ARC keep it, keep their deadline, and can still post their reviews. A draft is not closed: the question names it, and its row says Left as it is: a draft has nothing to close.
One queue of requests
The queue shows the waiting requests of the pen name's campaigns together, grouped under each campaign with its spots left, and each reader with their record, their note and their match. Filter by campaign or by book, choose readers, and press Approve or Decline. Every reader is told, either way.
Requests are decided one at a time, in the order you chose them. When a campaign's spots are filled, each request for it still in the batch says No spots were left on this campaign, so this request was not approved., and requests for other campaigns go on. To approve more readers for that campaign, add spots in its settings.
Campaigns for several books from one template
Several books, one template takes three steps:
- Books: choose from the pen name's published and coming-soon books, up to 25.
- Template: the spots per book, the opening day, the review date, how readers get it (Read in the app, protected or Download the EPUB), how to launch them (As drafts, to open one by one, Schedule for June 14, or Open them now), and an optional note to readers. What is asked of readers is fixed: an honest review on Booklabria by the date.
- Review: a row per book, Ready or left out with the reason. Nothing is created until you confirm.
Only the book differs from one campaign to the next. Each campaign is made exactly as one made by hand, with the same checks, and each book says on its row whether it was created.
The export
Export reviews (CSV) downloads one file for all the chosen campaigns, one row for each approved reader, with these columns: campaign, book, reader name, reader username, request status, approval date, reading state, held until release, review rating, review title, review date, review link and cross-posts.
A review still held until release exports as held only: the row says so, and the rating, title, date, link and cross-posts stay empty until the book is out (Reviews held until launch).
Never in the file: the text of a review, a reader's note to you, the match score, the reason a reader set a book down, and any e-mail address.
When none of the chosen campaigns has an approved reader yet, the answer is No approved readers on these campaigns yet. and nothing is downloaded.
Who can do what
| Author, imprint owner, editor | Marketer | Analyst | |
|---|---|---|---|
| Pause, resume, close | yes | yes | no |
| Create from a template | yes | yes | no |
| Export reviews | yes | yes | no |
| Approve or decline requests | yes | no | no |
An analyst's rows say Your role on this imprint does not allow this. When somebody in the imprint acts for a pen name, the queue says so above the requests, each decision is made in the pen name's own name, and pausing, resuming, closing and deciding are kept in the imprint's activity trail (Your pen name inside an imprint).
The plan
Bulk campaign work is part of the Publisher plan. On any other plan, each campaign in a batch answers with the plan's sentence, for example Pro does not include bulk ARC operations. Publisher does., and nothing is changed. During the beta every author tool is unlocked on every account, this one included (Plans and the beta).
Where this lives
Related
- 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.
- Imprints and teams: An imprint is the Publisher plan's workspace, several pen names and people in one place with roles (owner, editor, marketer, analyst). It invites an existing author's pen name; the author accepts from Settings, Teams, keeps ownership of the pen and its public page, and can leave with one click. Members run campaigns on behalf of a pen, every action is in the imprint's audit trail, and nobody but the reader path ever downloads a campaign's file. A Publisher account uses the same support as everyone.
- Your pen name inside an imprint: An imprint can work on your pen name without owning it. An editor drafts and runs things, and every delivery, campaign and letter goes out under your pen name; a letter is sent only after you sign it, unless you allow the imprint's owner to sign for you, which you can take back. The imprint's activity trail records who ran its campaigns and letters, and you can leave at any time and keep everything.
- Plans, and what the beta unlocks: Readers never pay; there is no reader plan and never will be. Writing here is free forever: books, series, the Journal and followers are never limited on any plan. What the plans are for is the launch: advance-copy campaigns, the readers who come with them, and the people who help. Author (free) has one pen name and one small campaign at a time (up to 25 readers, no delivery links); Creator ($9 a month or $90 a year) runs 3 campaigns at a time with up to 100 readers each; Pro ($19 or $190) is unlimited with 5 pen names and 2 collaborators; Publisher ($59 or $590) is the imprint, billed yearly by invoice with 5 seats. A $12 campaign pass runs one campaign (up to 100 readers) without a plan, valid for 60 days from the day you buy it. The 14-day trial needs a card and starts with your first campaign or delivery link, not at signup. During the closed beta nothing is charged and every author feature is unlocked.
- What counts as a reader on your plan: A plan counts readers per campaign: an approval, a certified copy the reader took, a giveaway winner. A delivery link is the Deliver service, with its own limit per link, and its claims never use a campaign's readers. A sample for followers counts toward nothing. The count is per campaign, not per month, and closing a campaign does not give the places back.
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