Conditional display at the web page level of a web page

When creating a page in the Website Builder, several levels of control are available.

Page publishing

Before even discussing visibility, you can decide:

To publish the page, making it available in the browser and accessible;
Not to publish it (back-office preparation only)

This allows you to prepare content in advance without it being publicly visible.

SEO SEO

You can also choose whether the page:

Should be indexed by search engines
Or remain unindexed

This is particularly useful for:

Private pages
Participant-only areas
Temporary content

Visibility restrictions

A. Restriction by date

By fixed date

You can set:

A start date for visibility;
An end date for visibility;
Or a specific period (from X to Y);

This allows, for example:

To display a "Badge" button only on the event day
To open access to a VIP page on a given date
To hide content after the event

Important :
Adhering to the date format is essential for the restriction to work correctly. It is recommended to use a clear standard format (e.g. YYYY-MM-DD HH:MM) to avoid any misinterpretation.

2. Dynamic dates

In addition to the simple configuration via the date selector in the back office, it is possible to use dynamic variables to manage conditional display based on event dates or custom metadata.

Use the event's native dates

You can use:

##{{ event.start_date }} ##{{ event.end_date }}

With operators:

##{{ event.start_date | add_days: 3 }} 
##{{ event.start_date | subtract_days: 3 }}

This allows, for example:

To display a button 3 days after the event start
To hide a page 3 days before the end

Use a custom metadata field

You can create an event metadata (required format: yyyy-mm-dd) and use it as follows :

##{{ event.traits.nom_de_votre_metadata | add_days: 3 }}

Expected date format for metadata

The accepted format is:

YYYY-MM-ddThh:mm:ss+00 YYYY-MM-ddThh:mm:ss+01

Important rules :

24-hour format required
The T is required between the date and the time
Seconds are optional
+01, +00, etc. define the offset from UTC

Concrete metadata example:

If you want to set a date to 29 February 2028 at 16:30 (London time) :

2026-02-29T16:30+01

B. Visibility based on connection

You can define whether the page is:

Visible to everyone (logged in and not logged in);
Visible only to logged-in participants;
Visible only to non-logged-in visitors

The notion of "logged in" means that the user is recognized by the platform via cookies.

C. Restriction by segment

When you limit a page to logged-in users, you can add an additional restriction:

Restrict access to a specific segment

This requires:

Creating a segment beforehand
Based on precise criteria (category, country, status, custom field, etc.)

Example :

A page accessible only to premium exhibitors
A page reserved for French VIPs
A page visible only for participants registered to a given session

2. At the level of sections & elements

In addition to entire pages, you can condition a specific section.

The same logic applies:

Date restriction
Connection restriction
Segment restriction

This allows you to create a unique page while adapting its content according to the visitor’s profile.

3. Conditional display in emails

The logic is similar, with one important difference:

In an email, the recipient is always identified.
💡 The notion of "non-logged-in" therefore does not exist.

You can condition an entire section, whether it is a button or a text block.