Most tools in this market treat a hosted landing page and a tracked external website as two unrelated features. Different screens, different settings, different reporting, and two places to attach a pixel. It reads fine in a feature list and it produces a mess in practice, because the funnel does not care which of the two a click landed on.
Scalegram makes them one object. A tracked site is a domain you have registered, with pixels attached and stats collected. A bridge page is that same object with hosted content attached to it. One record, one domain, one set of numbers, whether the page is served by us or by a site you built yourself.
What the object holds
The site record is where the funnel's identity actually lives. It carries the hostname you pointed at us, the pixels assigned to it, the events those pixels fire, and the stats collected for anything that happened on it. If the site has hosted content, it also carries the headline, the copy, the button, the colours and the channel it points at.
The reason this matters is attachment. A pixel is assigned to a site, not to a page and separately to a site. When you swap the hosted content, the pixels stay put. When you move a page to point at a different channel, the domain and its history do not move. And when you look at the numbers, there is one row for that hostname rather than two that need adding up.
The planning consequence
Because a page counts as a site, the unit you plan around is the domain. This changes the shape of a sensible funnel.
Do not build one enormous page and try to make it serve five offers with query parameters. Build a site per offer, give each one its own hostname, and let the reporting separate itself. The tracking layer works by hostname and first-party storage, so an offer that has its own hostname also has its own clean cookie space and its own pixel assignment. Offers sharing a hostname share everything, including each other's noise.
Plans include a fixed number of tracked sites, and a hosted page consumes one of them exactly as an external site does. Check the current allowance at scalegram.io before planning a funnel around a large number of hostnames, and retire the ones you no longer run.
Where an external site fits in the same model
If you already have a real website, it is registered the same way. One line of code goes on it, the site record holds its pixels, and events from it join the same reporting as everything else. The hosted page then becomes an option rather than a requirement: use it for angles that do not deserve a real page, use your own site for the ones that do, and keep both in one funnel view.
This is also why the answer to "should I build a proper site or use a bridge page" is usually both. Build the site for credibility and search, and still point the paid traffic at a page you can spin up and retire in an afternoon. The bridge page article makes the case for the hop itself.
What the model gives up
Being honest about the trade: one object per hostname means you cannot run several genuinely different hosted pages on the same domain and report them separately. If you want that separation, you want another subdomain, which is one DNS record away, covered in pointing a custom domain. There is no page hierarchy, no folder structure, no path-based routing. For a funnel that is a simplification. For someone expecting a CMS it is a limitation, and it is better to say so than to let them find out in week three.
Retiring a funnel without losing the record
Funnels end. The offer changes, the ad account is rebuilt, the angle stops working. What you want at that point is to stop the traffic without deleting the history, because the numbers from a dead funnel are the only benchmark the next one has.
Because everything hangs off the site record, that separation is easy to keep. Remove the CNAME and the hostname stops answering while the record, its stats and its attached pixels stay where they are. Deleting the site record itself is a different action with a different consequence, and it is the one worth restricting: access in Scalegram is granted per area with read, add, write and delete handled separately, so the person tidying up a workspace does not need the permission that removes six months of reporting.
The habit that makes any of this useful is writing down what a funnel was doing while it was alive. A site called "gold-q3-hookB" with a note about which creative it served is a benchmark. The same record with no note is a row in a list that nobody will ever be able to interpret again.
How to name things so you can find them later
Name the site record for the offer and the angle, not for the channel. Channels get renamed, angles get retired, and a list of sites called "main", "new" and "test2" is worthless by the second month. Put the offer first so the list sorts into groups, and keep the hostname visible next to it so the DNS panel and the app agree with each other.
One last thing worth keeping in view: none of this architecture makes an offer perform. It makes the reporting truthful. What the funnel sells at the end of it, and whether that is a trading community or anything else, carries its own risk, and no amount of clean data model changes that trading is high risk for the people at the end of the chain.
"We could have built pages and sites as two features. Then everyone would have had two places to check and two sets of numbers that disagreed."
— Alex Onta, Executive Director, SINGUARD
Key Takeaways
- A hosted bridge page and a tracked external website are the same object, so pixels and stats attach in one place.
- Pixels are assigned to the site record, which means content edits and channel changes leave the tracking untouched.
- Plan a funnel by hostname: one site per offer keeps the cookie space and the reporting separate.
- There is no page hierarchy or path routing, so separating two pages means adding another subdomain.
Frequently Asked Questions
Does a hosted page count against my tracked site allowance?
Yes. A hosted page is a site with content attached, so it consumes one of the tracked sites included in the plan, the same as an external website would.
Can I run two different bridge pages on the same domain?
Not on the same hostname. Add another subdomain and point it at Scalegram with its own CNAME, then each has its own record, pixels and stats.
What happens to my pixels if I edit the page content?
Nothing. Pixels belong to the site record rather than to the content, so edits and channel changes leave the tracking assignment in place.
About the Author
Alex Onta is an Executive Director at SINGUARD. He built eTrader, the terminal, the mobile apps, eTrader Broker, Copytrading, Business and Community, along with the worldwide clustered-server infrastructure it all runs on, with his brother Roman Onta helping on the design, and he leads that division today. Together with Roman he builds the Prop Firm CRM, the Broker CRM, Scalegram and CopySignals, and the two of them carry worldwide compliance, payment processing and international business structuring side by side. He lives and works in Dubai for most of the year. Meet the executive duo leading Singuard's five divisions.