Show the right block, to the right person, at the right time.
Every block on your page can be reserved for certain visitors: a device, a country, a language, dates, days and times, or how the visitor arrived on your page. And your whole page can be protected with a password.
By default, Fastpage shows every block to every visitor, all the time. Targeting is for when that's not what you want: a promotion valid for a week, a different message for your Instagram followers, a quiet page reserved for your clients, or a weekend block that only appears on weekends.
Three levels exist, from simplest to most powerful: turning a block on or off in the editor, the display settings built into every block (dates, countries, devices, languages), and the Visibility Rules block, which creates advanced conditions like "show this block to visitors coming from Instagram" or "hide this block on Mondays". To change a block's text rather than its presence, use merge tags.
Turn a block on or off #
Every block on your page has a small switch, visible in the editor's block list (hovering it shows Change status). A switched-off block appears grayed out in the editor, but stays in place with all its settings. It disappears completely from the public page: your visitors no longer see it at all.
It's the ideal tool for preparing a block in advance (a back-to-school offer, a holiday menu) without showing it, or for setting a block aside during a seasonal break, without deleting it.
A block's display settings #
Almost every block (link buttons, titles, texts, images, forms, countdowns, socials...) hides a collapsible section named Display settings in its edit form. Click it to unfold it: you'll find five display filters.
| Setting | What it does |
|---|---|
| Schedule | Pick a Start date and an End date. The block only exists on the page between those two dates. Ideal for a seasonal offer or an event announcement. |
| Countries | Select the countries that will see the block. An empty list means "all countries". The visitor's country is detected automatically. |
| Devices | Tick Desktop, Tablet or Mobile. For example: a "Call" button visible only on mobile. |
| Browser languages | Select the browser languages to target. A visitor whose browser is set to English will or won't see the block depending on your choice. |
| Operating systems | Target by system: iOS, Android, Windows, OS X, Linux, Ubuntu, Chrome OS. |
These are strict filters: a visitor who doesn't match doesn't receive the block at all, the page loads without it. You can combine several filters on one block (for example: mobile + France + between June 1 and 15): in that case, all filters must be true at the same time for the block to appear.
Scheduling (Schedule) requires a plan that includes block scheduling. The other filters are available on all plans. A scheduled block's page also reflects it in its RSS feed: outside the dates, the block doesn't appear in it.
The "Book" button will only appear on phones.
The Visibility Rules block #
To go beyond the simple filters, there's a dedicated block: Block Visibility Rules, in the picker's advanced category. This block never shows on your page: it's a configuration block, invisible to your visitors, that decides the visibility of other blocks on the page.
How it works
- Add the Visibility Rules block
In the editor, click the add block button, advanced category, and choose Block Visibility Rules. The block appears in your block list, with a reminder: "This block is configuration only. It is hidden on the page."
- Write a rule
Click Add Rule. Each rule has three parts: the blocks concerned (click the chips of your page's blocks, they fill in automatically), the action (Show to display, Hide to conceal), and the trigger condition, chosen from eleven possibilities.
- Set the priority
Every rule has a priority from 1 to 10 (5 by default). If two rules target the same block, the one with the smaller number wins. Think of it as your queue: 1 goes before 2, before 5.
- Test, then publish
Use the Preview as... button under the preview phone (see the Test section) to check your rule in real conditions, then save.
Three concrete examples
- Marie, a florist, wants to push weekend delivery. Rule: the "Sunday delivery" block is shown only from Saturday 8:00 am to Sunday 8:00 pm, in the visitor's local time.
- Karim, a sports coach, shares two different links on Instagram and in his newsletter. Rule: visitors coming from instagram.com see the "30-day program" block, the others don't.
- The band Volt hides its "Ticketing" block once the concert is listed as sold out: a Hide rule with a date range, or simply switching the block off.
Rules run in the visitor's browser, at load time, with no click or reload. Place the Visibility Rules block above the blocks it hides: the instruction is then known before they display, and nothing flickers. A hidden block is still present in the page's code, simply hidden on screen: do not rely on a rule to keep a secret (a reserved price, private information) from a curious visitor. The page password is the right tool for that. A rule can target several blocks at once, but never the Visibility Rules block itself. Finally, if you place several Visibility Rules blocks on the same page, the last one's decision wins for any targeted block.
Combining with merge tags
A rule decides whether a block appears. A merge tag decides what it says. The two work together without replacing each other.
- One offer, two messages: two separate rules. One shows the "Business pricing" block to visitors coming from LinkedIn, the other shows the "Personal pricing" block to everyone else. Each block greets with {{name|there}} and shows today's date with {{date}}.
- One campaign, one welcome: the rule reserves the "Welcome" block for addresses containing ?campaign=spring; inside it, {{city|your region}} locates the delivery, and the button passes {{campaign|bio}} to its destination.
Remember: a tag hides nothing. If the block is visible to everyone, its text is visible to everyone; a parameter's value changes the word, not the access.
The 11 possible conditions #
Each rule picks one condition from a list. Here is what each one tests and how to fill it in.
| Condition | What it checks | Example |
|---|---|---|
| URL query parameter | A parameter present in your page's address. You give the parameter's name (for example utm_campaign) and, if you like, the exact expected value. Without a value, the rule simply checks that the parameter exists. | A visitor who opens your page with ?offer=premium in the address sees the premium version of your block. |
| Device type | The device type: mobile, tablet or desktop, to tick. | The call button only on mobile. |
| Operating system | The visitor's system: iOS, Android, Windows, macOS, Linux, to tick. | A "Download the app" link only for iOS. |
| Browser language | The visitor's browser language, in two-letter codes (fr, en, de...), with quick-entry chips. | The welcome message in French for browsers set to fr. |
| Country | The visitor's country, detected automatically from their connection. Two-letter codes (FR, BE, CH...), with quick-entry chips. | Prices in euros for France, Belgium and Switzerland. |
| Referrer | The site the visitor comes from: part of the address is enough, separated by commas. The word direct refers to visitors with no referrer (QR code, typed link, some apps). | Coming from Instagram: show the Instagram link; coming from Google: show the pricing table. |
| In-app browser | An app's built-in browser: Instagram, Facebook, TikTok, LinkedIn, X / Twitter, or any built-in browser. | A special message for those arriving from Instagram's built-in browser. |
| New or returning visitor | First visit from this browser, or a returning visitor. The test is remembered per browser. | New visitors see your introduction; regulars go straight to your services. |
| Date range | A window of dates and times, with a start and/or an end (one side can stay open). The time is the visitor's. | The "Happy hour" block from June 1 to 30. |
| Days of the week | The ticked days: Monday to Sunday. | The day's menu shown only from Tuesday to Saturday. |
| Time of day | A time range, in the visitor's local time. A range that crosses midnight (10:00 pm to 6:00 am) works. | The "Evening orders" block visible after 6:00 pm. |
Priorities and conflicts #
Every rule carries a priority number from 1 to 10: 1 runs first, 10 last. When several rules target the same block, the rule with the smallest number decides, and it alone: the others are ignored for that block, even if their condition is true.
That single rule decides both ways. If its condition is true, it applies its action (Show shows, Hide hides). If its condition is false, it applies the opposite (Show hides, Hide leaves the block visible). A "Hide on Mondays" rule therefore hides the block on Mondays only, and leaves it visible the rest of the week without a second "Show" rule.
Example: a priority-2 rule says "hide Ticketing on Mondays", a priority-5 rule says "show Ticketing to everyone". A Monday visitor does not see it: rule 2 comes first and its condition is true. A Tuesday visitor does see it: rule 2's condition is false, and a Hide rule that does not apply leaves the block on screen. Rule 5 is never consulted for that block.
Put exceptions at low priority (small number): they win when their condition is true, and leave the block visible the rest of the time. A general "Show" rule is only useful when several rules target the same block: only the highest-priority one counts, the others are ignored.
Test before publishing #
A badly set rule stays invisible to you if your own browser doesn't match the condition. The Preview as... button, placed under the editor's preview phone, solves the problem: it simulates another visitor.
The window lets you choose: the device, the system, the country, the language, the in-app browser, a new or returning visitor, the referrer (instagram.com, google, direct...), the date and time, and even the address parameters to test (for example offer=premium). Each field can stay on "Real..." to use your real browser. Click Apply: the preview reloads as if that fictional visitor were opening your page. Reset goes back to normal.
These simulated settings only affect the editor's preview: they change nothing for your real visitors.
Reset / Apply
Protect the whole page #
Beyond blocks, the whole page has its own visibility settings, in the page settings tab.
Password
In the Protection section, the Password field locks the whole page: the visitor must enter the password to continue. Once entered correctly, the browser remembers it for 30 days. This is the solution for a clients-only page, a private media kit or an "on request" portfolio.
Sensitive content warning
The second setting in the same section, Sensitive content warning, shows a warning screen before entry: the visitor must click Accept. Useful for content meant for an informed audience.
The announcement bar
The Announcement bar section adds a banner at the top of your page: a short text (up to 256 characters), an optional link, a position (the banner stays visible while scrolling, or scrolls with the page), and background and text colors. Example: "Free delivery this week". The banner only appears if the text is filled in.
Hide the page from search engines
In the Seo section, the Block Search Engine Indexing setting asks search engines not to index your page. Combine it with the page's SEO section (title, description, preview image), detailed in the Pages guide.
The waiting screen (splash page)
In the Advanced section, you can place a waiting screen before your page: your logo, a title, a description, and a Continue button that stays locked during a countdown you choose. Splash pages are created in their own section and can serve as a brand screen or an ad break.
Close the page temporarily
In your page list, each page's switch (Change status) turns the page on or off: a disabled page sends visitors to the site's home. You can also, in the Advanced section, fill in Leap Link URL to redirect everyone to another address, for a maintenance window for example. Finally, a page can be taken offline automatically if your account stays too long without a plan: everything comes back with one payment.
Once your page is verified by the Fastpage team (on request, from the Verified badge section), a "verified page" badge can appear at the top or bottom of your page: a trust signal for your visitors.
Where to set what: the final table #
| You want to... | The setting to use |
|---|---|
| Set a block aside without deleting it | The block's switch in the editor |
| A block visible between two dates | The block's Display settings, Schedule setting |
| A block visible in certain countries, devices, languages or systems | The block's Display settings |
| Show or hide blocks by referrer, a link parameter, the social app, a day or a time | The Block Visibility Rules block |
| Check your rules | The Preview as... button under the preview |
| Personalize a text (first name, city, date) | A merge tag in the text field. The Personalised text block is for reading a parameter with another name (see "Introduce yourself") |
| Reserve the page for your clients | Protection: password |
| Warn about sensitive content | Protection: warning |
| A waiting screen before the page | Advanced: splash page |
| An announcement banner at the top of the page | Announcement bar |
| Opt out of Google | Seo: Block Search Engine Indexing |
| Close the page for a few days | The page's switch, or Leap Link URL |
Frequently asked questions #
Do my visitors see the block "flicker" before it disappears?
It happens when the Visibility Rules block sits after the blocks it hides: the page starts painting before the hiding instruction arrives. Move the Visibility Rules block above the blocks concerned. The hidden block stays in the page's code either way: to keep content out of reach, use the page password, not a rule.
Can I change a block's text depending on the visitor, without hiding it?
Yes, with a merge tag: "Hello {{name|there}}" adapts with no rule and no second block. Rules decide whether the block is there. See Merge tags.
I can't see my block in the preview, but it's switched on. Why?
Your browser probably doesn't match the block's conditions (device, country, dates, visibility rule). Open the Preview as... simulator and simulate the intended visitor to confirm. Also check that the block isn't scheduled outside its dates (Schedule).
Two rules contradict each other: which one applies?
The one with the smallest priority number. The block follows the decision of the priority rule whose condition matches the visitor, and ignores the rest.
Is the page password the same for all visitors?
Yes: one password per page, shared by all its visitors. After a correct entry, the visitor's browser remembers it for 30 days.
Does my page's RSS feed account for hidden blocks?
Yes: switched-off blocks and scheduled blocks outside their dates don't appear in the feed. And the feed switches off automatically if the page is password-protected or carries a sensitive content warning.