THE ESSENTIALS

A Landing Page is a stand‑alone, purpose‑built web page that a Contact "lands" on - typically after tapping a link, scanning a QR code, or reading a barcode. It lets a business capture new contacts or sell electronic gift passes without writing any code: a system user designs the page from the back end, activates it, and shares its link.

Landing Pages are part of CRM.COM's Contact‑Facing Essentials. Each page is hosted by CRM.COM at a unique URL, is fully branded to the business (logo, images, colours, text), and is rendered on any device.

Who this manual is for - four roles

• 🔧 Configurator - designs the landing page, sets its texts, colours, images, form fields and legal terms, then activates it. Works in Settings > Platform > Contact Facing Essentials > Landing Pages.

• 🖥️ Operator - shares the page link/QR code, and monitors the contacts and gift purchases it produces.

• 📱 Contact - opens the page to register or to buy a gift pass.

• 🔗 Integrator - a) can create a custom landing page to replace the one provided by CRM.COM, b) submits contact registrations or gift pass purchases to CRM.COM using Web APIs.

This manual explains the key concepts and how they map to the platform. For full integration guides, request/response schemas and code examples, refer to the Backoffice & Self‑Service APIs and the Integrators Hub.

• No‑code, fully branded. A system user defines the content, colours and images of the page but cannot change the fixed layout/arrangement of its elements.

• Two types, one designer. Register and Purchase a Pass share the same design wizard, the available options adapt to the type.

• Activate to publish. A page is Inactive by default and must be activated before its link is live.

• Distributed by link, QR or barcode. Every active page has a unique URL that you can copy, turn into a QR code, or encode in a barcode.

Key Concepts

Landing Page Type

The type is chosen on the Information step and determines the whole behaviour of the page.

• Register - collects contact details and creates a contact, can also optionally issue a Mobile Pass Card.

• Purchase a Pass - sells Gift passes (i.e. electronic gift cards), requires a Pass Plan configuration and a Payment Gateway integration.

State (lifecycle)

A landing page is either Active or Inactive. New pages start Inactive. Only an Active page serves its public URL. A Landing Page can be activated/deactivated at any time from the Landing Pages summary page or from the design wizard's Enable switch.

ℹ️ A Purchase a Pass page cannot be activated unless it has both a Pass Plan defined and a Payment Gateway integration. A Register page with Support Mobile Pass Cards enabled cannot be activated unless an active Mobile Pass Card configuration exists.

Managing Landing Pages

The Landing Pages summary page

Open Settings > Platform > Contact Facing Essentials > Landing Pages. Each page is shown as a card with its name, state badge, type badge, description and its link (with a copy button).

Distributing a page

Every active page has a unique URL of the form <https://<business>>.crm.com/landing-page/<page‑id>. Once a page has been saved, the wizard's Distribution step shows that URL together with a generated QR code (a barcode representation of the same link is also supported). Copy the link, or print the QR/barcode, to place the page on emails, posters, receipts, in‑store displays, etc.

The contact journey - Register

1. The contact opens the link/QR/barcode and sees the branded form (title, description, image, fields).

2. They complete the required fields (Email or Phone plus any others), accept the terms and choose their communication consents.

3. On submit, a contact is created in the back-end. If Support Mobile Pass Cards is enabled, a mobile pass card is provisioned. The success message is shown (or the failure message on error).

4. Already‑registered contacts can use the sign‑in prompt to log into the portal (subject to configuration).

Registered‑contacts sign‑in (optional)

A Register page can optionally include a link for existing contacts to access the portal. The configurator allows for a prompt message, a label for the link, and a Sign-In URL (typically the business portal). Registered contacts can use this link to log in instead of going through the registration process. These settings can be configured in the Texts step..

Mobile Pass Card provisioning

When Support Mobile Pass Cards is enabled on a Register page, a contact is automatically issued a Mobile Pass Card upon successful registration. The card configuration must exist and be activated first, otherwise the option is hidden and the page can't be activated. See the Mobile Pass Cards manual.

The contact journey - Purchase a Pass

1. The contact opens the link and sees the purchase a gift pass form: amount (fixed, or within the plan's min–max), sender, beneficiary name/email/language, and a gift message.

2. They pay through the configured payment gateway (secure one‑time payment).

3. If the transaction is successful, the Gift pass is issued/sent to the beneficiary and the success message is shown, otherwise the failure message appears.

Landing Page Settings 🔧

Design a page from Settings > Platform > Contact Facing Essentials > Landing Pages → Create Landing Page (or Edit). The current step is shown on the left, a live preview on the right, and an Enable Landing Page switch. Move through with Next/Previous (or click a step), then Save.

The design wizard & live preview

The page is built through a step wizard with a live preview beside it. The preview shows three pages of the contact's journey - the form (page 1), the success screen (page 2), and the failure screen (page 3) - and updates instantly as you edit. The steps shown adapt to the type:

Information

Texts

The wording shown on the page. Title, Success message and Failure message are required.

Colours

Pick colours for eight distinct areas; sensible defaults are pre‑filled:

Fields (Register)

The form fields determine which contact details are captured. The configurator chooses the fields to collect, orders them by drag‑and‑drop, and gives each a display label. Available fields: Full Name, Email, Phone, Pass Code. The form must include either Email or Phone (one of the two) so the contact can be uniquely identified.

On a Purchase a Pass page, this step is skipped - the gift fields are fixed by the platform: Gift Amount, Sender Name, Beneficiary Name, Beneficiary Email, Beneficiary Language, and a Gift Message.

Images

Upload and position the page imagery:

Legal (Register)

Capture consent and terms - important for GDPR/marketing compliance:

• Acceptance message shown next to the accept checkbox.

• Terms & Conditions - rich text and/or an external link.

• Privacy Policy - rich text and/or an external link.

• Email consent and SMS consent wording for communications opt‑in.

Distribution

Available after the page is first saved. Shows the page's unique URL and a generated QR code for that URL, ready to copy or print. (A barcode representation of the same link is also supported.)

Activate & Save

Toggle Enable Landing Page on and Save. The page is now live at its URL. Editing an active page and saving re‑publishes it immediately (the page cache is refreshed on every update, action or delete).

Good to Know

• Inactive by default. A new page won't serve its URL until you enable it.

• Type drives the wizard. Switching type reshapes the steps and (for Purchase a Pass) auto‑fills the gift fields; changing type clears type‑specific selections.

• Email or Phone, not both. A Register form is rejected on save if it has neither or both of Email and Phone.

• Purchase pages need a plan and gateway. Activation is blocked until both are set.

• Mobile Pass Cards must be active first. The support option is hidden - and activation blocked - if no active card exists.

• Distribution appears after saving. The QR/URL step only shows once the page exists.

• CIM must be enabled. Collecting Email/Phone relies on the corresponding Contact Information Method being enabled in Contacts settings.

• Live & Test mode. Pages are resolved in both live and test mode, so a page can be validated before go‑live.

• You can't restyle the layout. Only content (text/colours/images/fields) is configurable; the arrangement is fixed.

Reference Material

Mobile Pass Cards · Passes · Contacts · Integrations

TABLE OF CONTENTS