# Create a Landing Page This guide walks you through creating, configuring, and publishing a high-converting landing page in the Bird Marketing platform — from design to tracking performance. ### Before you start * Prepare assets: headline, hero image, body copy, CTA, form fields, and any tracking pixels or UTM parameters. * Ensure you have permission to publish on the domain/subdomain configured in Bird. This can be done under Settings > Marketing > Custom domains > Landing Page Domains ### Create a new landing page Go to **Marketing → Landing Pages** and click **Create landing page**.
*** * Under Details section, name the page, provide description and add any tags. * Click **Continue** to move to the Design step to the editor.
### Design the page (drag-and-drop editor) * **Building blocks:** Add pre-built sections (hero, features, testimonials, CTA, footer) * **Forms:** To add a form, select **Embeddables** block and select a embed sign up form you have created * **Settings:** Select Page settings and theme settings for the landing page * **Previews:** Switch between desktop/mobile preview while editing. You
*** ### Adding a form to a Landing page You can create an embed form under Sign up forms and add it easily to a landing page. Refer to this article on [how to create embed Sign up forms](https://docs.bird.com/applications/sign-up-forms/quickstarts/create-a-sign-up-form#embedded-sign-up-forms) * Once, you have published your embed Sign up form, add the **Embeddable** block to your landing page * After that on the right side for Embeddable block configuration, select the sign up form you want to embed
### Publishing the Landing Page Once designed, you can preview and publish the page. Here you can select page settings such as: * Page title: Used to show the title on the browser * Page description: Used to show the description on the browser * Domain: You can select a custom domain that you predefined and verified under Settings > Marketing > Custom domains > Landing page domains * Slug: Used to generate the URL of the page * Visitor tracking: Select an application created under Developer > Application to track visitors. Once the settings are defined, click **Publish.**
*** ### Tracking Events Monitor views and form submissions * When you select an application for page view tracking, you will get page view events * When a sign up form is submitted, you will get Form submitted events Note that events will be visible on the contact only when contact is identified and not anonymous. For example, if you have a sign up form and if the user fills up the sign up form, then they are identified and created as a contact with these events.
*** ### Adding a Landing Page link to an email You can add the link to a landing page to an email after publishing so that you can drive your email recipients to your landing page * Select the {} icon to add a variable > Links * Under Links, select Landing Page URL * Select the published landing page you want to embed the link for
You can also directly use the following liquid code to add a landing page URL ``` {% landingPageUrl project_id:'landing-page-id' %} ``` where **landing-page-id** is the **project-id** which you can copy from Landing page Overview. ### Best practices * One clear goal per page; single, prominent CTA above the fold. * Keep forms short — ask only for essential info to maximize conversions. * Use social proof (testimonials, trust badges) near the CTA. * Use concise copy and consistent visual hierarchy for scanability. --- # Agent Instructions: Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter: ``` GET https://docs.bird.com/applications/landing-pages/landing-pages/how-to/create-a-landing-page.md?ask= ``` The question should be specific, self-contained, and written in natural language. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.