Video guides
Historical interface: the recordings and preview examples below predate the official API cutover. The current runtime uses official tokens and does not support provider preview. Follow current setup for sign-in, explicit token transfer and separate AI authorization.
These recordings show the version 1.4.7 popup interface. Version 1.4.8 moves settings and checks to a separate options tab and remembers personal access locally. Use the current written guide for setup. The historical transcripts below describe the recorded version.
Short walkthroughs of the development extension. Each guide uses the real extension interface with demonstration accounts and responses. There is no audio; the steps appear on screen, with optional English and Ukrainian captions. Use fullscreen to inspect the popup.
Before you start, install the extension and obtain a personal API token from your operator. Chrome permission prompts are explained in the videos; permissions were already granted in the isolated recording profile. The videos do not show a live account or a real advertising transaction.
Connect your account
Read the steps
- Open TG Ads Assistant from Chrome's Extensions menu after installing the development ZIP.
- Set API origin to
https://tgads.tlmtr.devand enter your personal API token. A Telemetr.io analytics API key is a different credential. - Enter a recognizable connection name. The token is masked and kept only in browser-session storage.
- Click Connect Telegram Ads. This shares the two login cookies with the cabinet API. Accept the requested Chrome permissions when prompted.
- Confirm the active connection and its account list.
- Check validates the saved session. If it expires, sign in again and use Replace cookies.
Check a draft before launch
Read the steps
- Keep the cabinet API origin above. Set the separate Assistant origin to
https://tgads-assistant.tlmtr.dev. - Click Approve assistant access. This permits the assistant to receive your personal API bearer when checking a draft. Telegram cookies remain with the cabinet API.
- Open a Telegram Ads ad form, then open the extension from Chrome's menu. Read current ad copies the supported fields.
- Review the selected account, text, destination and target list. Read any import coverage warnings; unsupported fields are not silently checked.
- Click Check before launch. This is the action that sends the draft. It does not create, activate or fund an ad.
- Review findings and coverage. A ready preview is a technical result, not moderation approval.
Preflight setup and limitations
Understand and fix findings
Read the steps
- The example contains text over the length limit, a duplicate channel and a rejected target. Every input row stays visible.
- Read the affected field and suggested action. Shorten text that exceeds the limit.
- Inspect each target: resolved, duplicate and rejected describe different outcomes. A generic rejection does not establish a specific reason.
- The clean list contains unique resolved targets. Copying it does not modify the Telegram ad or approve it for launch.
- Fix the text and review the targets, then run the check again. Editing invalidates the previous report.
- Even when the result is checked, review coverage warnings. Telegram makes the final moderation decision.
The UI currently displays some assistant explanations in Ukrainian; the surrounding steps explain the same outcomes in English. Unavailable means a check could not finish, not that a target is unsuitable. Bot lookup is supported, but bot-placement preview is not. More than nine unique channels produce a creative-only preview with an explicit target-compatibility gap.