Blocks
Five blocks, each with a distinct job — four on a WooCommerce site, where the Account block is not registered. All appear in the editor’s Widgets category.
Paywall
fabrica-monetization-kit/paywall
Marks where the free preview ends and the wall begins. Everything after it is withheld from readers who have not paid.
It shows whichever wall the post’s access level calls for: a paywall at paid, or a registration wall at registration, or at metered for a reader who is logged out. A logged-in reader who has spent their metered quota sees the paywall. You do not need a separate block for each.
Content below the block is not sent to the browser at all, so it cannot be read from the page source.
Where the site is set to gate only posts with a Paywall block, this block is also what marks a post as gated. In the other restriction modes the post is already gated and the block just positions the wall — without it, the wall goes after the preview length.
Placement. Put it after enough content to be worth reading. A wall directly under the headline converts badly, and search engines see the preview, not the rest.
Membership
fabrica-monetization-kit/membership
Offers subscriptions on any page, without gating anything. Use it for a “support us” or “subscribe” page.
It shows the subscription products you pick as Membership tiers in the Tiers card under Monetization → Memberships. To run more than one scheme – reader tiers on one page, a Friends scheme on another – untick the tiers a block shouldn’t offer under Tiers in its sidebar. While every box is ticked the block offers every tier, including any you add to the settings later; removing a tier from the settings removes it from every block.
A reader who already holds one of the block’s own tiers sees a short confirmation instead of the offer, so you can leave it in place year-round, or set the block to hide from members entirely. Someone who belongs to a different scheme is offered the block as normal.
It renders nothing at all where the Memberships feature is off, where you have picked no products or none of the block’s own tiers are still among them, or on a post that is already showing a wall — two subscription offers on one page would only compete.
To post things to your members, turn on Collect postal address in the same panel’s Joining card. Joining then asks for a name and full address, which is saved on the member’s Stripe customer and shown on their profile under Monetization. It applies to this block only; paywall subscriptions are unchanged.
Once the payment goes through, the block thanks the new member in place. To send them somewhere next — a form where they complete their details, say — fill in After joining with a page on your site and a button label. A bare path such as members/welcome/ is read as one on your site; off-site links are ignored.
To gate a members’ area with another plugin, turn on Give members the Member role. Everyone with an active membership gets the Member role, and loses it when their membership ends, so a restriction plugin such as Profile Builder can limit pages to that role. Members who pay you some other way can be given the role by hand; it is only ever taken away from people who got it by joining here. It needs memberships billed by Stripe, so a site where WooCommerce Subscriptions bills them is not offered it.
To show the block on every post without placing it by hand, tick Add the Membership block to the end of posts in the On the page card and pick the post types. It is left off wherever the reader meets a wall, where the post already has the block, and on any post whose editor sidebar ticks Hide membership block. The same card sets the Default heading, which each block can change.
Unlike the Paywall block it restricts nothing. It is an invitation, not a gate.
Contributions
fabrica-monetization-kit/contributions
Collects donations to a campaign. Readers can give once or set up a recurring donation, choose from suggested amounts or enter their own.
Optionally shows a running total against a goal, which is what turns a donation box into a crowdfunder. Refunds adjust the total automatically.
Placement. Put it inside or beneath the work it is funding. An appeal at the end of the piece that made the case for it does better than one on a standing “donate” page.
Donations are not purchases: they grant no access to anything. If you want supporters to receive something in return, sell a membership instead.
A block is Standalone or Product-backed, set in its sidebar. A Standalone block sets its own amounts and needs nothing in the settings. A Product-backed block takes payment for a WooCommerce or Stripe product, offering its prices, and can only use products picked under Monetization → Contributions → Products for product-backed blocks. Renewals of those products count toward their campaign, even for subscriptions set up outside the block. The same panel sets the Default heading, which each block can change.
Signup
fabrica-monetization-kit/signup
Collects sign-ups for one specific thing — an event, a pledge, a call to action. It takes a name and an email address and nothing else; no money changes hands.
Nobody is on the list until they follow a link sent to the address they typed. That round trip is the whole point: it is what makes the address real, and it is why the block can quietly mint an account without offering a weaker door than your registration wall already does. The reader is never told about the account, because from where they stand they signed up to a thing, not to a website.
Campaign ID. Give this block and a Contributions block the same ID and one campaign carries both the guest list and the money raised. Both are listed under Campaigns → People.
Three states, one block. The toolbar switches the editor between the form, the wait for the emailed link, and the confirmation. Each has its own copy, and the two later ones may override the heading — a form that says “Reserve your seat” should not still say it to somebody holding one. Leave a heading empty and it inherits the form’s; the placeholder shows you what it will say.
A separate opt-in. The form can carry one checkbox of its own, labelled in your words — a mailing list, updates, permission to come back to them later. It ships unticked and is never a condition of signing up: making it one would not be consent at all, and would leave every recorded tick worthless as evidence that anyone wanted it. It sits above the submit button, because a box a reader only meets after pressing the button asks for consent too late; the separate small-print field, for whatever wording your privacy policy needs, prints below the button. Ticks show as their own column under Campaigns → People, and each one fires fabrica_monetization_kit_campaign_opt_in, which is where you wire the address into the list it was offered for. Joining the campaign is not agreement to anything else, and is never recorded as one.
Writing the confirmation email. Two placeholders go in the message: {{first_name}} greets them by the name they typed, and {{confirm_link}} is the link itself. Where you put {{confirm_link}} is where the link lands, so anything below it — a sign-off, a note about replying, a P.S. — comes after the link rather than in front of it. Leave the placeholder out and the message works as it always has: your words, then the link, then how long it lasts. On a campaign that does not ask for names, {{first_name}} takes its whole line with it, so “Hi {{first_name}},” disappears rather than greeting nobody.
You write plain text; it arrives as a message. Blank lines stay paragraph breaks and single line breaks stay line breaks, so an address or a sign-off keeps its shape. Put the link on a line of its own and the reader sees words to tap rather than a web address — the address itself is never shown twice, so a line ending in a colon directly above it is dropped as the introduction it was. This matters more than it sounds: a mail server is allowed to break a plain-text message at 76 characters, and Google’s does, which is why a long paragraph used to reach a phone with a hard break through the middle of every line.
Who the emails come from. By default they carry whatever sender the site uses for everything else, which for a campaign signed by a person reads oddly — and any reply goes to the site’s general inbox rather than to them. Fill in the From name and address and both campaign emails carry those instead. Use an address on this site’s own domain: it sits in every guest’s mailbox indefinitely and gets forwarded on, and a sender outside the domain the site is allowed to send for is the quickest route into a spam folder. Leave them blank and nothing changes.
Switching the second email off. The confirmation email always goes — it carries the only link there is to join by — and leaving its Subject and Message empty is all it takes to fall back to the built-in wording. The email to a signed-in guest is genuinely optional, so that one has a switch of its own. Off means they hear nothing at all: the page changes and no email arrives.
Writing the second email separately. By default the email telling a signed-in guest they are in reuses the success message from the block, with a link back added underneath. Where the email needs to say more than the page does — the date and the address, which sit beside the message on the page but not in an inbox — write it in the Message field under Email for signed-in readers instead. Then {{success_link}} puts the link exactly where you want it and nothing is added after it, so you can sign off below it, and {{first_name}} greets them by name.
Two emails, two subjects. The one asking a reader to confirm, and the one telling a signed-in guest they are in, are written separately and now carry separate subject lines — a subject meaning “please confirm your seat” reads as an instruction to somebody who already has one. Leave the second blank and it uses the block’s success heading — the words sitting directly above that email’s own wording on the page — falling back to a plain default only if there is no heading either. It never borrows the first.
The other email. Somebody who is already signed in joins in one click, with no link to follow — so the only email they get is the confirmation, whose text is the block’s success message. Because that message is also what they read on the page, it cannot carry a placeholder; the page’s own address is appended to the email instead, so a guest reading it a week later still has the date and the directions.
Content gate. Optionally withholds everything below the block until the reader signs up. By default it waits until they have confirmed by email; you can set it to open the moment they submit the form instead, which shows the lower half of the page to anyone who typed an address, whether or not it turned out to be theirs. Withheld content is never sent to the browser. The gate stands down on a post your paywall already covers — two walls on one post is an ambiguous thing to render, so the paywall keeps it.
Hiding what the sign-up has answered. Add the class fmk-hide-on-signup to any block on the page, in its Advanced → Additional CSS class(es) panel, and it disappears once the reader has asked to join. Use it for the copy that argued the case — the pitch above the form — so the confirmation is not lost among the words that are now beside the point. Leave it off anything they still need, such as the date, the address or an add-to-calendar link. It works anywhere on the page, above the block as well as below it.
Showing what only makes sense once they have joined. The class fmk-show-on-signup, added the same way, does the opposite: the block stays off the page until the reader asks to join, then appears. Use it for what belongs to the outcome rather than the argument — an add-to-calendar link, a note about what happens next, a line asking them to bring a friend. It is not the content gate and protects nothing: the words are sent to every browser and merely go undrawn, so anything that must genuinely be withheld goes below the block with the gate switched on instead.
Account
fabrica-monetization-kit/account
Sites without WooCommerce only. Where WooCommerce is active this block is never registered, so it is not in the inserter at all.
The reader’s account page: log in, see what they have bought, manage their subscription, set or reset a password, log out.
Also available as the [fmk_account] shortcode, for themes that are not block-based. The shortcode is registered alongside the block, so it is equally absent where WooCommerce is active — there it renders as literal text.
Where the block exists, it is required. Put it on a page and set that page under Accounts & login → Account page. It is where password-setting links from account emails land, and there are two ways to get it wrong. Set no page at all and new readers get WordPress’s stock login email pointing at wp-login.php, rather than your set-password page. Set a page that has no Account block on it and the link lands on a page with no form. The plugin watches for both and offers to create the page for you in one click.
On a WooCommerce site none of this applies. WooCommerce My Account already covers the same ground, and gains a Content Access tab.
Gift Aid
For UK charities and CASCs registered with HMRC. Switch on the Gift Aid panel under Monetization, then fill in the charity’s name and its HMRC reference; Gift Aid stays off until both are there. Until then the panel says so, and the status strip above the panels reads Gift Aid: needs details.
The Contributions block then asks donors paying in pounds to add Gift Aid. Ticking the box agrees to HMRC’s standard declaration, naming your charity, and asks for a house name or number and postcode. The declaration covers that payment, everything the donor gives later, and the previous four years, so a regular donor is asked once and every later payment carries it.
Memberships can carry Gift Aid too, when their benefits stay within HMRC’s limits — members’ journals and newsletters count as having no value. List the tiers that qualify under Memberships eligible for Gift Aid; the Membership block asks only for those. With Collect postal address on, the declaration uses that address rather than asking again. Whether a membership qualifies is for you to judge. Paywall checkouts never offer Gift Aid: they sell content.
To claim, open Tools → Gift Aid claims, choose the dates — the current tax year by default — and download the CSV. Its columns are those of HMRC’s schedule spreadsheet, so paste the rows into that and upload it in Charities Online; HMRC takes at most 1,000 rows at a time. Fully refunded payments are left out, and a partly refunded one is claimed on what you kept. A Direct Debit is claimed once it has been paid.
A declaration is made to one charity, so each records the HMRC reference it was made under. If the reference changes, donors are asked to declare again at their next checkout and renewals go unclaimed until they do; the export lists each reference separately, so every charity claims only on its own declarations.
When a donor cancels, remove the declaration from their profile under Monetization. Later payments are then not claimed; earlier ones stay in the claim. Declarations survive a personal-data erasure request, because HMRC requires you to keep them.
The name on a bank statement
The Paywall, Membership and Contributions checkouts end with the name the reader’s bank statement will show, read from your Stripe account — see Stripe or WooCommerce for where to change it and how to hide it.
Demonstrating the blocks
To show the blocks on a site that must never take money — a demo, or a staging copy running live Stripe keys — add add_filter('fabrica_monetization_kit_demo_mode', '__return_true'); to the theme. Every block still renders and opens its checkout, card form and Gift Aid box included, and checks what is typed. Submitting then shows Demo – no payment taken, or Demo – nothing was sent for a sign-up, in place of the result: no payment, account, sign-up, Gift Aid declaration or email is made, and the endpoints behind the blocks refuse even when called directly. Signing in still works. There is no setting for it.
Changing what a block shows
Most copy comes through fabrica_monetization_kit_text, so you can reword any string without touching markup. Each string has a key, such as paywall.buy.heading, and can also be targeted directly — fabrica_monetization_kit_text_paywall_buy_heading.
To change what is offered rather than what is said, use fabrica_monetization_kit_purchase_options. It runs over every list a wall can show — term bundles, authors, subscriptions — so you can add an option, remove one, or reorder them.
To add your own markup around a wall, fabrica_monetization_kit_header and _footer take a context of paywall, regwall or membership.
See the hooks reference for the full set.