Lead reporting beside client work
Keep acquisition outcomes close to the project, tasks, and meetings that produced or respond to them, giving performance discussions an operational next step.
Connect a Master Account API key to give every workspace member a live, read-only view of WhatConverts lead performance on the object types selected in Display settings. Profile mappings stay in Kato while contact rows are fetched only when viewed and are never imported or retained.
Keep acquisition outcomes close to the project, tasks, and meetings that produced or respond to them, giving performance discussions an operational next step.
Review supported calls, forms, chats, and revenue together instead of presenting each channel as an isolated metric with no shared client context.
Choose where WhatConverts data should appear so the workspace does not flood unrelated records with marketing metrics that do not belong there.
A workspace owner or admin adds the WhatConverts Master Account token and secret and chooses where the record tab appears. Members then link up to 25 account profiles to each record, select the reporting currency, and view combined metrics, trends, attribution, and the Lead Manager. Kato encrypts both credentials and caches only profile metadata and aggregate dashboard results.
Open the client's project before a reporting call and connect recent lead volume and attributed revenue to the campaigns and tasks the team delivered.
Compare conversion channels and lead details when a client raises a quality question, then create targeted follow-up work in the same record.
Use attributed revenue as one signal when prioritizing optimization work, while keeping WhatConverts as the specialist source for detailed attribution reporting.
The integration supports the WhatConverts lead and attribution context available for calls, forms, chats, and related revenue according to the connected account.
No. WhatConverts remains the source for lead tracking and attribution. Kato brings relevant results into the record where teams coordinate the client work around them.
Yes. Teams choose the records where the connected WhatConverts context belongs, helping the workspace remain focused and preserving a clear client association.
Last updated Aug 19, 2026