Improvements and fixes: October 20–26

Small improvements and fixes for the week.

Improvements

• Campaigns and Adset AI: the assistant now builds a campaign end to end and edits its stream sets. It creates a campaign with settings and sets (filters, pixels, flows with PWAs and landings), adds and changes sets and flows, and turns them on and off — with the same result as saving in the campaign editor. Before writing anything, the assistant shows a plan and waits for confirmation; deleting a set or a flow is confirmed separately. External MCP clients get the same actions via the new key permissions “Create Campaigns” and “Edit Campaigns & Stream-sets” (off by default).
• Domains: a new domain has a main page right away. When a domain is created, transferred, or registered, it is automatically assigned the system white page, so the domain root no longer returns an empty response. You can still pick your own page in the domain settings.
• Report builder: query and CSV export errors are shown as the server's message — you can see which field or filter was rejected instead of “Request failed with status code…”. If no grouping is selected, a hint with the “Columns” button is shown instead of an empty report.

Fixes

• Telegram conversion notifications: the {event.event_session} macro (start of the user's session) is rendered as a readable UTC date, for example 2026-10-16 16:15:34 UTC, instead of a number. The macro has been added to the template hints next to {event.event_time}.
• Campaign flow statistics: the campaign total in the sets and flows statistics panel is calculated on the server from the sum of events. Percentages and averages (CR, EPC, ROI) are no longer summed from ready-made set values — previously the campaign row could show figures like 600% instead of 17%.
• Team billing: the plan start, renewal, and upcoming charge dates are shown in one format (date and time) both on the “Team billing” page and in the team summary in settings; the start date no longer differs between screens.
• API: the traceId field in responses and the X-Trace-Id header contain the real request identifier — you can quote it when contacting support (previously the response could contain unknown).

Where to find it: Adset AI (assistant button in the dashboard) → “create a campaign…”; Settings → MCP keys → key permissions; Domains → domain list; Pixels → Telegram bot → message template; Reports → Report builder; Campaigns → campaign editor → flow statistics; Settings → Team billing.