The setup is genuinely one record. You pick a subdomain, say join.yourbrand.com, and add a CNAME in your DNS pointing it at the hostname Scalegram gives you. Nothing else. There is no server to rent, no certificate to buy, no WordPress to keep patched and no plugin waiting to break during a campaign launch.
The first time a browser asks for that subdomain, a certificate is issued for it on the spot and the page is live over HTTPS. That on-demand issuance is why the setup has no certificate step for you to get wrong, and also why the very first request can feel a moment slower than every one after it.
Choose the subdomain like it is disposable
Use a subdomain, not the apex. The apex domain usually has other records on it, sometimes email records, and pointing it anywhere is a much bigger decision than pointing join at something.
Beyond that, plan for rejection. Media buyers running several angles want a separate subdomain per angle, because a destination that gets flagged takes down the campaigns using it and nothing else. One subdomain for every offer, and a spare already resolving, is cheap insurance for a funnel that lives on paid traffic. The reasoning behind having a page at all is in bridge pages on your own domain.
The three reasons it does not load
A subdomain that will not open looks the same in a browser whatever the cause, so work through them in this order.
- The record has not propagated. DNS changes are not instant, and the resolver your laptop is using may be holding an old answer for an hour or more. Check the record from outside your own network before assuming anything is broken.
- The domain sits behind a proxy. If your DNS provider offers a proxy or CDN mode and it is switched on, requests never reach the host that is supposed to issue the certificate. This is by far the most common cause of a protocol error on an otherwise correct setup, and it is fixed with one toggle.
- The domain is not registered on the Scalegram side. The certificate is only issued for hostnames the platform expects. A CNAME pointing at the right place for a domain nobody told the platform about produces a handshake failure rather than a page.
Nearly every case is one of those three. If a browser shows a certificate or protocol error, that is a signal about the connection, not about the page, and no amount of editing the page content will change it.
Test the subdomain yourself, from a phone on mobile data, before any spend touches it. A media buyer discovering a dead destination through a rejected ad is an expensive way to find a DNS typo.
What lives on the domain once it works
More than the page. The domain becomes your first-party surface, which is the point of the whole exercise. Click identifiers captured on it are stored there and can be read back by another page on the same subdomain later, which is how a deposit weeks after the click still reports with the campaign attached. Pixels fire from a domain that carries your brand rather than a shared vendor host. Campaign values recorded there travel into the client list, as covered in UTM handling.
All of that depends on the visitor's first and last touch being on the same hostname. Splitting a funnel across two different subdomains, one for the join page and another for the verification page, quietly breaks the chain. Keep a funnel on one hostname.
Housekeeping worth doing once
Keep a plain list of which subdomain points at which page and which campaign uses it. Six subdomains in, nobody remembers, and the one nobody remembers is always the one still running spend. Remove the CNAME when you retire an angle, so a domain you no longer watch is not resolving to a page you no longer maintain.
Treat the page copy as part of the compliance surface too. A destination page in front of a trading community is reviewed like any other advertising asset, and claims about outcomes are the fastest route to a rejected domain. Trading carries a high risk of loss and the page should not suggest otherwise.
Several domains in one workspace
Nothing stops you pointing a dozen subdomains at Scalegram, and any funnel running paid traffic at volume ends up doing exactly that. The thing that goes wrong is not technical, it is bookkeeping. Six months in, half the subdomains resolve to pages nobody has opened since spring, and one of them is still the destination on a live ad set.
Two habits fix it. Give every hostname a name that says what it is for at a glance, matching the site record inside the app, so the DNS panel and the workspace read the same. And review the list on a schedule, retiring the CNAME at the same time as the page rather than months later.
Who can touch that list is worth deciding too. Access in Scalegram is granted per area with read, add, write and delete handled separately, so a media buyer can be given the reporting without being able to unpick the domain that carries it. Domains are the one piece of the funnel where a mistake takes every campaign down at once, which is a good argument for keeping the delete permission narrow.
Then it is boring, which is the point
Once the record resolves and the certificate is issued, the domain stops being something you think about. It renews itself, it survives page edits, and moving a page to a different channel does not disturb it. The whole configuration is one line in a DNS panel, which is the correct amount of infrastructure for a marketing page.
"Every domain problem I have looked at was DNS, a proxy or impatience. In that order, and never anything more exotic."
— Roman Onta, Executive Director, SINGUARD
Key Takeaways
- Setup is a single CNAME on a subdomain, with the certificate issued automatically on the first request.
- A proxy or CDN mode left switched on at the DNS provider is the most common cause of a handshake failure.
- Run one subdomain per angle so a rejected destination costs you one campaign rather than the account.
- Keep the whole funnel on one hostname, or the stored click identifier cannot be read back at the deposit step.
Frequently Asked Questions
What DNS record do I need?
A CNAME on the subdomain you want to use, pointing at the hostname Scalegram gives you. Use a subdomain rather than the apex domain.
Do I have to buy an SSL certificate?
No. The certificate is issued automatically the first time the hostname is requested, and it renews without any action from you.
Why does my new subdomain show a connection or certificate error?
Usually DNS that has not propagated yet, a proxy or CDN mode enabled at the DNS provider, or a domain that has not been registered on the Scalegram side.
About the Author
Roman Onta is an Executive Director at SINGUARD. He builds the Prop Firm CRM, the Broker CRM, Scalegram and CopySignals side by side with his brother Alex Onta, and he helped on the design of eTrader, the division Alex built and leads. His ground is worldwide payment processing, AML compliance and the corporate structures brokers are built on, work the two of them carry together, shaped by executive roles in the UAE and international corporates. He lives and works in Dubai for most of the year. Meet the executive duo leading Singuard's five divisions.