[{"data":1,"prerenderedAt":9},["ShallowReactive",2],{"docs-settings-rm":3},{"title":4,"excerpt":5,"body":6,"seo_title":7,"seo_description":8},"Bot settings","Fields, tags, segments, landings, content, shop and access — everything covering the bot's data and monetization.","\u003Cp>The \"Settings\" section (the gear icon in the top bar) covers data, monetization, and access rights — unlike \"Messages\", where the dialogue logic lives.\u003C\u002Fp>\u003Ch2 id=\"fields\">Fields\u003C\u002Fh2>\u003Cp>Data the bot stores about a subscriber, which you can reference in message text via @field_name. Created by default: id, first_name, last_name, username, avatar, email, phone_number.\u003C\u002Fp>\u003Cp>When creating a new field you pick one of 12 data types, plus two toggles — \u003Cstrong>Unique field\u003C\u002Fstrong> (the value can't repeat across two subscribers — handy for promo codes\u002Forder IDs) and \u003Cstrong>Global field\u003C\u002Fstrong> (the value is shared across all subscribers rather than being individual): String (up to 255 chars, extended comparisons in segments), Text (up to 4095 chars), Number, Date, Email, Phone, Attachment, Photo, Photo collection, Audio, Video, File.\u003C\u002Fp>\u003Ch2 id=\"tags\">Tags\u003C\u002Fh2>\u003Cp>Labels for grouping subscribers — assigned manually or automatically (through the \"Add tag\" action in messages and buttons). A tag has its own color (for visual distinction in the CRM) and a \"Limit duration\" toggle — the tag is automatically removed from the subscriber after a set time (handy for labels like \"Waiting for reply 24h\"). The section also shows tag analytics. \"Has tag\" can be used as a condition in a segment.\u003C\u002Fp>\u003Ch2 id=\"segments\">Segments\u003C\u002Fh2>\u003Cp>A segment is a set of conditions; if a subscriber matches all of them, they land in the segment automatically. Segments are used in broadcasts, message-sending conditions (the \"Scenarios\" topic), and action conditions. There are 20 condition types available: Bot subscription date, Subscribed via a landing page, Received a message, Going through a scenario, Clicked a link, Clicked a button, Field comparison, Has tag, Made a payment, Has an active subscription, Assigned to a manager, Booked an appointment, Opened an article, Answered a survey, Is a group\u002Fchannel member, Invited referrals, Specific date, Specific time, Specific day of the week, Segment trigger probability, Nested condition.\u003C\u002Fp>\u003Cp>\u003Cstrong>\"Segment trigger probability\"\u003C\u002Fstrong> is a rare but handy one for A\u002FB tests: you can send 50% of a segment one message and the other 50% a different one, without manually splitting the base.\u003C\u002Fp>\u003Cp>The \"Answered a survey\" and \"Invited referrals\" conditions reference mechanics that don't have their own clearly labeled section in the interface — a \"survey\" is assembled out of a regular message with a keyboard\u002Flist button plus \"Data to save\", and referral links aren't exposed as a separate builder at the interface level. If you specifically need a referral program, check with TvoyBot support on how it's implemented on your plan.\u003C\u002Fp>\u003Ch2 id=\"landings\">Landings\u003C\u002Fh2>\u003Cp>Separate pages\u002Flinks for subscribing to the bot — traffic from different landing pages can later be distributed into segments (the \"Subscribed via a landing page\" condition) and viewed separately by geography. Every new landing page immediately gets its own pair of links (a short one, i.tvoybot.com\u002Ftg\u002F..., and a direct one, t.me\u002FYourBot?start=...), plus an \"Open editor\" button — a visual builder for the subscription page itself. The bot already has a \"Main landing\" by default, created when you created the bot.\u003C\u002Fp>\u003Cp>Inside the editor is a WYSIWYG builder: a \"desktop\u002Fmobile\" toggle to preview responsiveness, and every block on the page (avatar, bot name, the \"Open in Telegram\" button) has its own mini settings panel via a gear icon. Clicking a text block brings up a formatting toolbar — bold, italic, strikethrough, underline, link, font size and color, background color, emoji, lists, quote.\u003C\u002Fp>\u003Ch2 id=\"content\">Content\u003C\u002Fh2>\u003Cp>Tabs for Attachments (files you can attach to messages — with a usage counter, plan limits, a type filter, and a \"Cloud storage\"\u002F\"messenger storage\" filter) and Articles (long-form pieces opened via the \"Article button\").\u003C\u002Fp>\u003Ch2 id=\"shop\">Shop\u003C\u002Fh2>\u003Cp>Three tabs:\u003C\u002Fp>\u003Cul>\u003Cli>\u003Cstrong>Products\u003C\u002Fstrong> — a product card has four blocks: Product info (name, description, image), Payment settings (integration, currency, price, discount, restricting payment to a segment only), Seller details (a link to the agreement\u002Foffer, a terms article, business name, email, phone — the legal minimum required to accept payments) and Post-payment actions (the same action builder: assign a tag, continue a scenario, etc.). Every product immediately gets its own payment page like i.tvoybot.com\u002Fproduct\u002F…, and its button is added to a message via \"Buy product\"\u003C\u002Fli>\u003Cli>\u003Cstrong>Subscriptions\u003C\u002Fstrong> — recurring payments; a subscriber can see and cancel access via the \"Subscriber's account\" button\u003C\u002Fli>\u003Cli>\u003Cstrong>Integrations\u003C\u002Fstrong> — connecting a payment aggregator. Supported: Prodamus, Tinkoff, Robokassa, YooKassa, YooMoney, Fondy, Fanspay, Stripe, bePaid, Lava, Telegram Stars, CryptoCloud, ClickUz, Payme, CryptoBot, NOWPayments, Tochka, ExpressPay, Ozon, AlfaBank — including cryptocurrency. If the aggregator you need isn't on the list, you can request it from support\u003C\u002Fli>\u003C\u002Ful>\u003Ch2 id=\"access\">Access\u003C\u002Fh2>\u003Cp>This is about managing the bot itself, not its subscribers:\u003C\u002Fp>\u003Cul>\u003Cli>\u003Cstrong>Change token\u003C\u002Fstrong> — if the Telegram bot's token was reissued\u003C\u002Fli>\u003Cli>\u003Cstrong>Change language\u003C\u002Fstrong> of the bot\u003C\u002Fli>\u003Cli>\u003Cstrong>Change domain\u003C\u002Fstrong>\u003C\u002Fli>\u003Cli>\u003Cstrong>Delete bot\u003C\u002Fstrong> (irreversible)\u003C\u002Fli>\u003Cli>\u003Cstrong>Add a user\u003C\u002Fstrong> — invite team members with a role that restricts which sections they can access (e.g. a manager only sees \"Chat\", not \"Access\")\u003C\u002Fli>\u003C\u002Ful>","Bot settings in TvoyBot: fields, tags, shop, access","A full breakdown of the TvoyBot Settings section: fields, tags, segments, landings, content, shop and team access.",1783936971173]