The data sits in different systems
Spend in the ad account, behaviour in web analytics, calls in the call-tracking tool, deals in the CRM. To get one number, somebody exports four files every single time.
The analytics integrations module connects 22 systems — web analytics, ad accounts, social, ecommerce and CRM, call tracking and email — and rolls their metrics for the last 30 days into one screen. Nothing changes in the connected system: the module only reads.
Spend in the ad account, behaviour in web analytics, calls in the call-tracking tool, deals in the CRM. To get one number, somebody exports four files every single time.
A token expires, access is revoked, the platform changes its API — the data simply stops arriving. It gets noticed at month end, once the report is already out.
Call tracking, CRM and email tools usually connect with an API key, and those keys end up scattered across chats and personal notes instead of one controlled place.
Where the platform supports OAuth, it is a one-click authorisation. Where it doesn't, you paste an API key in a dedicated dialog. Keys and tokens are never handed back to the interface.
The module collects metrics from every connected source for the last 30 days and shows, per source, its status, the last sync time and the platform's own error text.
The built-in assistant works only on data that actually synced and returns five findings with a type and a priority, plus an answer to any question about that same summary.
Web analytics, ad accounts, social, ecommerce and CRM, call tracking and email marketing — in one list, each with what it actually contributes.
GA4, Google Search Console, Yandex Metrica, Yandex Webmaster and Microsoft Clarity — behaviour, search demand and session recordings next to the ad numbers.
Calltouch, Comagic and Ringostat, Bitrix24 and amoCRM connect on the same footing as the ad accounts, so a lead stays visible past the click.
Active, pending, error or disabled — with the last sync time and the platform's error text instead of a silently empty chart.
Impressions, clicks, spend and conversions from every connected source are counted together, with a per-platform breakdown.
The module pulls data and changes nothing in the connected system: no goals in analytics, no deals in the CRM, no campaign settings in your email tool.
There are 22 platforms across six categories: web analytics (GA4, Search Console, Yandex Metrica and Webmaster, Microsoft Clarity), ad accounts, social, ecommerce and CRM, call tracking and email marketing. The full list is visible before you connect anything, with a description and the auth method for each.
Those sources connect with an API key through a dedicated dialog — that is how call tracking, CRM and almost every email tool work here. The key is entered once and never returned to the interface, and the integration can be disconnected at any time.
No. The analytics integrations module only reads: it creates no goals, edits no deals and touches no email settings. Changes to advertising happen in other modules and always go through an explicit human confirmation.
Each integration shows its status — active, pending or error — along with the last sync time and the error text the platform returned. That way an empty chart is immediately distinguishable from 'no data arrived because the token expired'.
No, and that is deliberate: with no synced data it refuses to produce recommendations. Once data is there, it returns five findings with a type and a priority, and answers free-form questions against that same summary.
Connecting takes a couple of minutes, and the module is read-only — your systems stay exactly as they are.