Landing blocks

Block editor

On the editor page, the landing is assembled from top to bottom:

1. Hover over a block area.
2. In the block toolbar, select the pencil to open its fields. The toolbar also lets you move, hide, duplicate, or delete the block.
3. Select the insertion zone between blocks and choose the new block type.

A hidden block stays in the editor and draft but is not shown to visitors. A new block can be saved with empty optional fields. The standalone Button block is the exception: configure its action before publication or delete the block.

Block types

Each type has a separate guide with a screenshot of the landing result, the complete settings panel, and empty-field behavior:

• Cover — a first screen with a title, text, background image, and optional button.
• Text — a content section with a heading and formatted body.
• Button — a standalone subscription or URL action.
• Image — one wide illustration with alternative text.
• Advantages — a shared heading and a grid of feature cards.
• Reviews — comments with author names and images.
• Products — product, service, or pricing cards with a price.
• Video — a video link with a heading, description, and play icon.
• Timer — a countdown or text label with an optional button.
• Divider — a horizontal line with no content fields.

Images

Images can be uploaded for Covers, standalone Images, and Feature, Review, or Product cards. PNG, JPEG, and WebP files up to 10 MB are supported; width and height must not exceed 8,000 pixels.

Cover and standalone Image blocks can use separate desktop and mobile files. If only one version is uploaded, it is used on every screen. Timer has one optional background image; Cover and Timer also provide a separate background overlay setting.

If an upload fails, the reason appears below the field. Fix the format, size, or connection and select the file again.

Text formatting

Hover over the text block area and select the pencil. The block or card text editor lets you make a fragment bold, italic, struck through, or monospace and add a safe link with the http or https protocol.

Headings, bulleted and numbered lists, quotes, code blocks, and dividers are also available. The result is saved with the text and shown on the published page.

Variables in text

In a text field, open the variables list, switch the data scope, and select the required value. The editor inserts a reference such as {{project.company}} for a project variable or {{lead.city}} for a lead variable. Landings support the project and lead scopes specifically; a {{lead_data.first_name}} reference used elsewhere in Senler AI is not substituted here.

When a value is missing, the page leaves an empty place instead of the reference. For an optional fragment, provide two variants: {{#if lead.first_name}}Hello, {{lead.first_name}}!{{else}}Hello!{{/if}}. A personalized page uses the first variant when the name is filled and the second when it is empty.

For a JSON variable, access a nested field with a dot, for example {{project.catalog.title}}, and an array item by index, for example {{lead.orders.0.title}}. If the Markdown editor stores an underscore as \_, the landing still recognizes the variable name correctly. Lead variables are empty in preview. On a published page, they are substituted only in a supported channel where Senler AI can verify the lead from the launch context; they also remain empty when the page opens without that context.