---
description: "Landing Pages (beta): Dalton drafts one version of your landing page per Meta ad, matched to the ad's message. Setup, approval, daily ad sync and the optional split test."
---

# Landing Pages for Ads (Beta)

::: info The short answer
Landing Pages gives every Meta ad its own version of your landing page, matched to what the ad promises. Dalton drafts a version per ad and you accept each one. Until you do, visitors see your original page. You can split test the versions against the original page to measure the effect.
:::

::: tip Beta: ask us for access
Landing Pages is in beta. Ask us to turn it on for your account.
:::


## What it does

An ad about waterproof jackets and an ad about a summer sale usually land on the same page. Landing Pages gives each ad a page version whose headline and content follow that ad's message.

| Step | What happens |
| --- | --- |
| Ads sync | Dalton reads your Meta ads once a day |
| Draft | Dalton drafts a page version for each ad |
| Review | You accept each version, or leave it |
| Serve | Visitors from an ad see its accepted version. Before that, they see your original page. |


## Setup

1. **Connect Meta Ads** in **Connectors**.
2. **Point a subdomain at Dalton** with a DNS record, such as `offers.example.com`. The page versions are served there.
3. **Connect your Shopify store**, so the pages can show your products.
4. **Tag your ads.** Link each ad to the Dalton URL with <code v-pre>utm_content={{ad.id}}</code> (or `utm_id`), so Dalton knows which ad a visitor came from.


## How it runs

**You stay in control.** Nothing goes live until you accept it. An ad without an accepted version sends visitors to your original page.

**New ads are picked up daily.** Launch a new ad in Meta and its draft appears after the next sync.

**Optional split test.** Turn on a split test to send part of the traffic to your original page. That shows whether the matched versions convert better than the page you had.

## Good to know

- One version per ad. Ads without the <code v-pre>utm_content={{ad.id}}</code> or `utm_id` tag can't be matched.
- The versions run on your subdomain. Your main site is not changed.
- For a test on your own pages for one campaign, use an audience rule instead. See [Personalise by Audience](/personalise/by-audience).