Connect Cloudflare and create a webspace
- Open Landings → Create, choose Hosted, then click Connect Cloudflare.
- Authorize access in Cloudflare. Return to the editor and choose Cloudflare account.
- Select a Webspace, or enter Webspace name and click Create webspace. If you already have webspaces, choose + Create webspace first.
- Wait for setup to finish. If Cloudflare asks you to activate R2 storage, enable it and click Retry setup.
/.
Prepare and upload a page
Upload one.html or .htm file, or a ZIP with index.html at its root. Include local styles, scripts, images and fonts. Use UTF-8 for text files.
- Use relative links for local files, such as
images/product.webp. URLs built in JavaScript are not adjusted to the landing’s path. - Remove
<base href>and Content Security Policy meta tags. - Remove
integrityfrom local stylesheets, including style preloads, so they can load. Keep it for CDN files.
Connect offer buttons
Use/click in each offer link:
/click links to your offers.
For buttons added by JavaScript or events sent from the page, see Tracking script functions.
Choose an address and publish
- Choose Landing domain and enter Path & parameters, such as
/summer/. - To add a hostname, click Connect domain. Enter an unused Subdomain, choose its Zone, and click Connect domain. Wait for it to appear in Landing domain.
- Set Landing protection or Block known bots if needed. Click Publish & Save.
- Add the published landing and an offer to a campaign’s Landers & Offers path.
- Open the campaign’s Tracking link, or Traffic URL for Direct script. Check the visit and offer click in reports.
/summer/ opens the same page on each domain. Give each landing a non-overlapping path. A landing at / needs its own webspace. Use separate hostnames for hosting and tracking.
Pass values to the page
Add parameters after? in Path & parameters. Use Macros for this URL to insert a supported macro:
Landing protection
For a landing reached through Redirect, turn on Landing protection and click Publish & Save. Visitors must enter through a campaign link. No PHP file is needed. The plain page address is blocked, and protected links expire after 10 minutes. Protection applies to HTML. Images, scripts and styles remain accessible. Leave protection off for the first page of Direct script. See Landing protection.Block known bots
Choose a custom Landing domain, turn on Block known bots, and click Save. The block applies to this landing on all custom domains in its webspace. This blocks verified bots, including search engines, link previews and ad platform crawlers. It does not block other automated traffic. Ad platforms can reject ads if they cannot check the landing.Edit and restore
Use the arrow beside the main button to choose:
Save does not publish an unpublished landing.
Click Edit files to change a text file or replace an asset. Click Replace to upload another HTML file or ZIP. The current page stays live until you publish the replacement.
Click Download ZIP to get the saved files. The download excludes unpublished edits and a replacement you have just selected.
Preview in the list’s context menu opens the published page, including protected pages. Use a campaign’s Tracking link to test visits and clicks.
To restore a publication, open Publication history, click Restore, then confirm Restore & publish. The saved files from that publication go live with the current saved address, parameters, tracking domain and protection settings.
A connected AI agent with Read and write access can also create and edit landings. See Publish hosted landings.
Change or disconnect a domain
To change the address:- Select another connected Landing domain and click Save.
- To change the path, edit Path & parameters and click Publish & Save.