To measure and manage a lander, open the Analytics tab for pageviews, CTA clicks, and CTR, use the Tracking and Code tab to add Google Analytics or GTM, and use the Domains page to manage your domain pool. Built-in analytics runs automatically on live landers, and preview visits are never counted.
Once a lander is live, two things matter: knowing how it performs and being able to adjust it. CasinoLanders gives you both. Built-in analytics tracks the numbers that count for an affiliate page, pageviews and CTA clicks, without any tags to install. On top of that, each lander has code fields for your own Google Analytics or Tag Manager, and the dashboard keeps your domains, MCP, and SEO settings organized so you can tune a page whenever you need to.
Because analytics is automatic and preview visits are excluded, the data you see is a true picture of real visitor behavior on your domain. That makes it easy to compare landers and double down on the markets and angles that convert.
Pageviews
Real visits to your live lander. Preview visits are excluded.
CTA clicks
Clicks on your affiliate links, the rel=sponsored links on the page.
CTR
The click-through rate, or CTA clicks as a share of pageviews.
Every live lander records analytics automatically, with no setup. Open the Analytics tab in the lander editor to see pageviews, CTA clicks, and the click-through rate between them. Pageviews count real visits to the published page, and CTA clicks count taps on your affiliate links. These give you a quick read on whether a lander is getting traffic and turning it into outbound clicks.
CTA clicks are tracked on your affiliate links, which are the rel=sponsored links on the page. Preview visits inside the editor are never counted, so reviewing a lander does not inflate your numbers. That means the pageviews and clicks you see reflect genuine visitor behavior on the live domain, which keeps your CTR honest.
If you want your own tracking on top of the built-in analytics, use the Tracking and Code tab. It has separate fields for head code, body-start code, and body-end code, so you can drop in Google Analytics, Google Tag Manager, or any pixel exactly where the provider asks. There is also a toggle for the built-in analytics if you ever want to turn it off. Your custom code runs alongside it.
The Domains page is where you add a domain, point one DNS A record at the server IP shown, and click Verify to issue free SSL. Assign one domain to one lander, or remove domains you no longer use. Assignments are 1:1, so moving a domain to a different lander is a matter of reassigning it. Search, a status filter, and pagination keep a large list easy to manage.
Beyond a single lander, the dashboard is where you manage everything else: your MCP URL on the MCP page, your domains on the Domains page where you verify them for free SSL, and your SEO fields per lander on the SEO and Domain tab, including title, angle, keyword, SEO title, and SEO description. Together these let you tune both how a lander is found and how it is tracked.
The three code fields map to where providers ask you to place snippets: head code for most analytics tags, body-start code right after the opening body, and body-end code just before it closes. Paste each snippet into the matching field and it loads on the live lander.
The Tracking and Code tab, the Domains page, and the SEO and Domain tab work as a set. Use the code fields to layer Google Analytics, Google Tag Manager, or a pixel on top of the built-in tracking, and keep the built-in analytics toggle on unless you have a reason to disable it. Use the Domains page to keep your pool tidy and to assign the right domain to the right lander, remembering that the relationship is 1:1. Use the SEO and Domain tab to set the title, angle, keyword, SEO title, and SEO description that shape how each lander is found. Together they cover both sides of a successful page: getting found and being measured.
That completes the CasinoLanders workflow. You have connected Claude with your MCP URL, built a library, generated a lander with AI, taken it live on your domain with free SSL, and set up analytics and settings. From here you can repeat the build and go-live steps for every new market, all from the same casino library, and all free while we are in beta.
No. Built-in analytics runs automatically on every live lander, recording pageviews and CTA clicks with no configuration. Open the Analytics tab in the lander editor to see pageviews, CTA clicks, and click-through rate.
No. Visits to the live preview inside the editor are never counted, so reviewing and refining a lander does not affect your numbers. Only real visits to the published domain are recorded.
CTA clicks are recorded on your affiliate links, which are the rel=sponsored links on the lander. That lets CasinoLanders show a click-through rate against pageviews so you can judge how well a page converts traffic into outbound clicks.
In the Tracking and Code tab of the lander editor. It has head, body-start, and body-end code fields, so you can place GA, GTM, or any pixel exactly where the provider requires. A toggle controls the built-in analytics, and your custom code runs alongside it.
On the Domains page. Add a domain, point one DNS A record at the server IP shown, click Verify to issue free SSL, then assign one domain to one lander. Assignments are one to one, so reassigning moves a domain to another lander, and search, a status filter, and pagination help with a large list.
In the SEO and Domain tab of the lander editor. You set the title, angle, keyword, SEO title, and SEO description there, and assign the domain the lander will use when it goes live.