How to Use Swipe Pages to Launch a Mobile Page for Meta Ads

The short answer: if your Meta ads send phone traffic to a page that loads slowly or sits on a shared address, rebuild it in Swipe Pages on your own subdomain, which the Startup plan covers for $39 a month with 20,000 visits, per the pricing page: connect the subdomain by CNAME, build an AMP page, add hidden UTM fields that load from the URL, add the Meta Pixel ID and the cookie notice, validate the AMP, run the CRO agent on the live URL with your ad screenshot, then publish the changes a person approved.

Disclosure: I may earn a commission through some links on this site. It does not change what this page says.

The job: a paid social campaign is running, most clicks come from phones, and the leads arrive without any record of which ad sent them. Swipe Pages builds pages for exactly that click. For the plans and what each includes, see the Swipe Pages glossary entry.

Before you build:

1. Turn the ad budget into visits. For example, a €2,000 monthly budget at €0.80 a click buys 2,000 / 0.80 = 2,500 clicks, far inside Startup's 20,000 visits; above the allowance, the pricing FAQ charges $5 per extra 5,000 visits.
2. Collect what the campaign already has. The ad creative and its copy, a screenshot of the ad, the Meta Pixel ID from your ads account, and DNS access for your domain.
3. Choose the measure before launch. Leads per ad, read from a UTM field on every lead and set against the spend for that ad in Meta's reporting.

What you need

• A Swipe Pages trial or plan. The trial is 14 days without a card; Startup is $39 billed monthly on the pricing page (checked on 26 October 2026). Dynamic text and A/B testing need Marketer at $89.
• Your own domain. This is not optional for ads, as step 1 explains.
• The Pixel ID and a privacy policy URL for the cookie notice.

Step 1: Connect a subdomain first

Swipe Pages' free addresses, swipepages.net and swipepages.page, are shared by tens of thousands of free users, and the Facebook article explains that Facebook blocks a whole domain when some of its content breaks the rules. Your own domain carries only your reputation.

Open Domains, click Add New Domain, enter yourcompany.com, then a subdomain such as promo. Copy the hostname and the "Point To" value, create a CNAME record with them at your DNS provider, and click Finish. The domain guide allows a few hours up to 72 for propagation; click Connect until the status reads CONNECTED. The "Point To" value is case-sensitive.

Step 2: Build the page as AMP

Start from a template in the drag-and-drop builder and keep the page type as AMP, which loads fastest on a phone. If you later need custom scripts, the dashboard's three-dot menu offers Create Smart Version to make a standard copy, and Create AMP Version to go back, per the conversion article.

Step 3: Capture the ad on every lead

Click the form and add a hidden input field. Give it a label such as utm_content, which appears in the leads tab, and switch on Load from URL so the value comes from the ad link, as the UTM guide shows. Repeat for utm_source and utm_campaign, and put the same parameters in every ad's URL. Then send the leads where they belong: open the direct integrations dashboard, connect the app with its credentials, and link it in the page's Integrations tab, per the integrations guide.

Step 4: Echo the ad in the headline, on Marketer

Dynamic Text Replacement swaps a word on the page for a value in the URL. In a text, button or form module, type a shortcode such as [angle::faster setup], where angle is the URL parameter and the text after the colons is the default, per the DTR guide. Each ad links with its own angle value, and one page answers several ads.

Step 5: Add the Pixel behind a cookie notice

Paste the Meta Pixel ID in Global Settings, Tracking Codes, then save and publish, per the Pixel guide. Then switch on the Cookie Notice in global settings and fill in the consent text, the accept and decline labels and your privacy URL. The cookie notice article states that Google tags and Facebook pixels do not fire until the visitor accepts.

For visitors in the EU, that order matters: Article 5(3) of the ePrivacy Directive requires consent before storing or reading information on a visitor's device, except where strictly necessary for the service.

Step 6: Validate the AMP

Run the published URL through the AMP validator linked in the AMP check article. An invalid page usually means a script or style tag in Other Scripts or the custom JavaScript area. Only valid AMP pages are served through Google's CDN.

Step 7: Let the CRO agent audit the page, then decide yourself

Open the CRO agent, drop in the screenshot of your ad, add the live page URL with its tracking parameters, and adjust the prompt if one area worries you. The AI agents guide describes what follows: clarifying questions about the goal and the traffic, a written plan, the agent's reasoning as it works, and a report you can download as a PDF. A research task of this kind uses about 125 to 175 credits, per the credits guide.

The agent recommends; a person decides. The marketer who owns the campaign reads each recommendation against what the ad promises, applies the ones that hold up in the builder, and republishes.

Step 8: Test one change, on Marketer

In the Variants panel, switch on A/B test mode, add a variant with the single change, and set Variant weights, per the A/B testing guide. Each variant's results appear in the Analytics tab.

What the Swipe Pages docs warn about

• Ads to a shared domain. Blocked domains are hard to recover, per the Facebook article.
• Custom JavaScript on AMP. It makes the page invalid AMP, even when the code runs.
• Standard GTM on AMP. It needs an AMP container instead.
• Changes that do not appear. Publish after every edit and clear the browser cache, as the DTR guide notes.
• Per-variant results in the AI Page Builder. The variants guide lists them as coming soon, so run tests you need to read in the drag-and-drop builder.

The shared domain gets a trial page live with no DNS work, which is what a trial is judged on; your ad account judges the domain's reputation instead, so connect your own before the first ad runs.

FAQ

Can I keep Google Tag Manager on an AMP page?

Only with an AMP container. The GTM article says the conventional script does not work on AMP pages.

Does the cookie notice stop tracking before consent?

Yes. The cookie notice article says Google tags and Facebook pixels do not track until the visitor accepts.

How long does a custom domain take to connect?

From a couple of hours up to 72, depending on your DNS provider, per the domain guide.