Sites

A site is what you build for your users: a storefront, a catalogue, a form, a user area, a quiz. One site opens both in a browser and inside Telegram — you never build two.

Where it opens

• In a browser. A project has one address — <subdomain>.geckochat.app — and the sites of the project live on it as paths: the first site takes the root, the others get a path of their own, for example <subdomain>.geckochat.app/promo. The path of a site is changed with the "Address" button in the Sites section, the subdomain itself in the project settings. A custom domain cannot be connected to a site yet.
• In Telegram. The same site opens inside Telegram as a Mini App — from the "Mini App" button under a bot message.

How it's built

In words. You describe what you need, the agent writes the pages, builds the site and shows a preview. Edits work the same way: "make the cards bigger", "add a price filter".

Each site has its own pages, styles and logic. Users, products, orders and files belong to the project and can be used by several of its sites.

What it can do

• Show data from the project's collections.
• Take orders and lead to payment.
• Collect form answers and store them on the person's card.
• Know who opened it: in Telegram by their Telegram account, in a browser after they sign in. Before signing in, a visitor is a guest.

Publishing

A site has two states: draft and published. Users see the published one; edits live in the draft until you publish. There is version history and rollback.

What you see afterwards

Visit and activity metrics are available in analytics and on an identified project user's card. Before sign-in, the visit is anonymous; it does not prove the person's identity.

In Live sessions, enable recording to watch site sessions: pages, clicks, movement and scrolling. Session cards include device and browser information and the country when known. Viewing is scoped to your project; the raw IP address is available only to platform admins.