Practical use cases
Get feedback before a campaign
Publish a page and send the link to your team so they can review the offer,
layout, and buttons before you send traffic.
Use a branded campaign link
Connect a subdomain such as offers.example.com so your campaign sends
visitors to an address under your own domain.
Put approved edits live
Update a published page after reviewing changes, so visitors see the
version you intend to use.
Before you start
Have a successfully generated Build page and a destination URL for its call-to-action buttons. Check the copy, images, and button destinations before publishing. For a custom address, you also need a domain you control and access to its DNS provider. DNS connects the address to the hosted page.Publish without connecting a domain
Find Publish, the page slug, and Custom subdomains in the Build editor.
1
Open your page
From the StefanBrain sidebar, open Build and open the page you want to share.
2
Open Publish
Select the black Publish button at the top-right of the editor, above your page preview.
3
Review the slug
Under Published page, review the Slug. This is the page-specific part of the URL, such as
summer-offer, not a domain name.4
Publish the page
Select Publish. Anyone with the public URL can view the page.
5
Copy the link
Copy the published URL shown in the dialog. Use that exact URL rather than constructing one from your slug.
6
Check the published page
Open the link in a signed-out browser window. Check desktop and mobile layouts, and test the call-to-action links.
Connect your own subdomain
1
Open Custom subdomains
Select Publish at the top-right of the Build editor. Custom subdomains is inside this dialog, not a separate toolbar option.
2
Enter your subdomain
Under Custom subdomains, enter your subdomain—for example,
offers.example.com.3
Start setup
Select Add. The example text in an empty field is only a placeholder; enter your own address to enable the button.
4
Follow the DNS setup
Follow the guided DNS setup. Sign in to your DNS provider when prompted and review the proposed changes before confirming them.
5
Check the status
Return to the Publish dialog and check the status. DNS changes and the HTTPS certificate may take time to become ready.
6
Connect the subdomain
If the subdomain is Available, select Connect to attach it to this published page. If prompted to publish first, finish publishing before connecting.
7
Copy the custom link
Once it is Connected, copy the complete custom URL shown for the page. It includes the slug:
https://offers.example.com/summer-offer.8
Test the complete URL
Open that complete URL in a signed-out window. Confirm HTTPS loads without a warning and the buttons work before sending traffic.
https://offers.example.com is not the same as opening the page’s complete URL. Keep the slug in campaign links.
Publish later changes
The public page is a published snapshot, not the live editor preview. After editing, open Publish and select Update to put the new version live. Open the published link again and check the changed section. Recheck links before replacing URLs in active campaigns.If you get stuck
Never send passwords or DNS-provider login codes in a support message.

