


Aspro.Cloud report: deals, sources, and stages
Aspro.Cloud combines CRM, projects and finance, and Reportkey takes from its CRM module what a marketing report needs: new deals by source, won and lost deals with budget, the open pipeline by stage and manager results.
- An Aspro.Cloud server API key or OAuth, set up once for all projects.
- New deals and their budget by source from the account's source list.
- Won and lost deals, average deal and the open pipeline by stage.


Aspro.Cloud integration: the account address and a server API key with CRM module access are entered once, the project picks pipelines, and deals by source, won amount, average deal, stages and managers go into a recurring report next to Yandex Direct and Yandex Metrica.
Aspro.Cloud CRM analytics in a client report
Aspro.Cloud is a cloud system for service companies, where CRM, projects, tasks, time tracking and finance live side by side. Sales run in the CRM module: a deal with a budget and source moves through pipeline stages and has an owner, a creation date and a close date. Reportkey reads that module through the open API and builds recurring report blocks from deals, placed next to advertising and web analytics.
Projects, tasks and invoices stay out of the report: the block answers marketing and commercial questions about how much came in, how much was sold, from where and by whom.
Aspro.Cloud integration: API key or OAuth
There are two ways to connect. The first is a server API key with CRM module access: an administrator creates it in settings, and you enter the account address and key on the integrations page. The second is OAuth sign-in, where access follows the user’s rights. Either way the connection is stored centrally and chosen in the relevant projects. If the key is revoked, the connection asks for re-authorisation without losing settings.
Aspro.Cloud deals by source
The first block splits the period’s new deals by source from the account list:
- New deals — by creation date per day, week or month.
- New deal amount — budgets from the cards.
- Source — the value selected on the deal.
Sources are filled by managers or forms, so block quality depends on team discipline. Deals without a source get their own row so the total matches the CRM.
Won deals and amount
The second block reports closing results by close date. The Aspro.Cloud state flag splits closed deals cleanly into won and lost:
- Won deals and won amount;
- Average deal for won deals;
- Lost deals and win rate.
Several pipelines are shown separately, each with a previous-period comparison.
Aspro.Cloud sales pipeline
The third block shows open deals across the stages of the chosen pipeline: how many deals and how much budget sit at each step when the report is built. The sales head sees where volume piles up, and an agency sees how many ad-driven deals are still undecided. Past stage transitions are not guaranteed by the API, so this is a snapshot rather than a history.
Sales by manager
The owner breakdown gives new and won deals and won amount per employee. With a previous-period comparison it is a ready basis for the weekly sales meeting.
Aspro.Cloud with Yandex Direct
CRM blocks usually follow Yandex Direct spend, VK Ads campaigns and Yandex Metrica goals. Calls can come from CoMagic or Calltouch, and revenue per ad campaign from Roistat.
Agency-branded design and AI insights are not on every plan. Other sales systems are under CRM, a sample document is the in-house team demo report, and trial terms are on the pricing page.
What goes into the Aspro.Cloud report
These are the metrics that the Aspro.Cloud integration already brings into Reportkey reports.
Aspro.Cloud reporting: plans and free trial
14 days free, no card required. Prices and plan limits are on the pricing page.
Why teams connect Aspro.Cloud to Reportkey
Real reporting jobs, typical pain points, and the outcomes teams get from Aspro.Cloud in client reports.
- A studio runs deals, projects and invoices in Aspro.Cloud, yet the client ad report is still assembled from ad accounts separately.
- Managers pick a deal source in the card, but seeing deals and revenue per source for the month takes manual work.
- Open deals sit at intermediate stages, and the sales head cannot see how much budget is currently in progress.
Incoming development and advertising inquiries become deals with a source. A monthly internal report shows, next to spend on the studio's own promotion, how many deals and how much budget each channel produced.
New clients and renewals run in different pipelines. The report shows them apart: new deals by source for marketing, won deals and average deal for management.
A weekly summary shows open deals and budget by pipeline stage and each owner's results for the week compared with the previous one.
How Aspro.Cloud appears inside the report
The report keeps the familiar Reportkey layout: source sections and period comparison.

A source table with new deals and new deal amount, tiles for won deals, won amount, average deal and open pipeline, and a bar chart of pipeline stages.
Three steps to the first report
Connect the account once, choose the reporting scope, and save the setup for recurring client reports.
Frequently asked questions
Short answers about how the integration works in Reportkey today.
How is an Aspro.Cloud account connected?
How is a won deal identified?
Is the deal budget a received payment?
Will UTM tags appear in the report?
How often is data refreshed, and why do large accounts load longer?
Often connected together
Working sources that teams usually add to the same report.
Aspro.Cloud report: deals, sources, and stages
Sign up, add your Aspro.Cloud address and API key and pick pipelines in a project. Your first report in 5 minutes.


