> For the complete documentation index, see [llms.txt](https://docs.reachplatform.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.reachplatform.com/customizations-and-bolt-ons/hosted-checkout-landing-pages/landing-page-marketing-guide.md).

# Landing Page Marketing Guide

Plan and launch branded landing pages that drive campaign traffic into Reach hosted checkout.

Launch branded, direct-to-checkout landing pages without waiting for a product release. Use them to test offers, reach distinct audiences, and measure campaign performance.

{% hint style="info" %}
**Best for:** campaign teams that need a focused path from a marketing message to a preconfigured checkout or benefit activation.
{% endhint %}

### Choose your landing page pattern

A landing page connects your brand and offer directly to checkout. It gives visitors a prefilled purchase or activation flow.

First, decide where the page sits in your funnel. Acquisition and enrollment pages serve different audiences and need different messages.

{% columns %}
{% column %}

#### Acquisition pages

**Goal:** Turn prospects into subscribers.

Use these pages for cold or warm traffic. Lead with the offer, price, and plan comparison.

Typical sources include ads, events, and campaign content. Customers usually select a plan and complete purchase.
{% endcolumn %}

{% column %}

#### Enrollment pages

**Goal:** Help existing customers activate a benefit.

Use these pages for an engaged audience. Lead with benefit value and a simple activation path.

Typical sources include welcome emails, benefit portals, and enrollment windows. The checkout flow is often shorter.
{% endcolumn %}
{% endcolumns %}

### What landing pages unlock

#### Move faster

Launch a page, offer, or audience segment in days. You can test new campaign messaging without joining an engineering release queue.

#### Control the message

Shape the page's copy, imagery, offer framing, and call to action. Reach checkout remains standard across landing pages.

#### Attribute conversions clearly

Connect each conversion to its campaign, channel, or audience segment. This provides verified transaction data for future targeting.

#### Run campaigns in parallel

Create separate pages for seasonal offers, partner audiences, and marketing channels. Each page can use its own campaign context without a separate integration.

### Understand the limits

Landing pages balance speed with a focused scope. They are not a replacement for a fully custom funnel.

{% hint style="warning" %}
Every new landing page and change to a live page requires Reach design approval before publication.
{% endhint %}

| Landing pages support                   | Requires additional design or engineering work   |
| --------------------------------------- | ------------------------------------------------ |
| Focused, single-offer paths to checkout | A new checkout connection                        |
| Brand-led messaging and campaign design | Custom calculators, quizzes, or bill checkers    |
| Multiple pages for distinct audiences   | A multi-page website or a white-labeled checkout |

Reach controls the checkout experience. It remains consistent across every landing page.

### Know who owns each task

{% columns %}
{% column %}

#### Reach owns

* Hosting on a Reach domain by default
* Page design, build, and approval
* Checkout connection, promo prefill, and custom engineering requests
* Request coordination through your account manager
  {% endcolumn %}

{% column %}

#### Your brand owns

* Brand assets, copy direction, and design references
* Offer details, pricing, and traffic generation
* Custom domain acquisition, if needed
* Build requests beyond standard content
  {% endcolumn %}
  {% endcolumns %}

Your account manager coordinates work across design and engineering. Contact them first for build status or changes.

### Drive traffic to your page

Use the channels where your audience already engages with your brand:

* **Direct links:** Email, SMS, benefit portals, and existing brand touchpoints.
* **Campaign traffic:** Paid social, events, QR codes, print, and affiliate links.
* **Embedded calls to action:** Links from your website or app into the landing page.

Acquisition pages often use paid, social, and print channels. Enrollment pages usually use owned channels, such as email and benefit portals.

### Plan your page before requesting a build

{% stepper %}
{% step %}

#### Define the audience

Decide whether visitors are new prospects or an existing audience. Identify what prompted their visit.
{% endstep %}

{% step %}

#### Define the conversion

Choose one action. Visitors can compare plans and purchase, or activate a benefit they already have.
{% endstep %}

{% step %}

#### Define the message

Decide how much the page needs to persuade. A new audience needs more context than an enrolled customer.
{% endstep %}

{% step %}

#### Define the campaign lifecycle

Confirm whether this is a one-time page or a reusable pattern for future campaigns, cohorts, or partners.
{% endstep %}
{% endstepper %}

{% hint style="info" %}
For payload configuration, testing, and launch requirements, see [Hosted Checkout Landing Pages](/customizations-and-bolt-ons/hosted-checkout-landing-pages.md). Review the [Landing Page Approval Guide](/customizations-and-bolt-ons/hosted-checkout-landing-pages/landing-page-approval-guide.md) before submitting a page.
{% endhint %}

### Questions or clarification?

Reach out to your respective account manager or email us at <account-desk@reachplatform.com> for help and support.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.reachplatform.com/customizations-and-bolt-ons/hosted-checkout-landing-pages/landing-page-marketing-guide.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.