Skip to content
Reportkey
OkoCRM
Deals from OkoCRM

OkoCRM report: deals, budget, and loss reasons

Every OkoCRM deal carries a budget, stage, owner, loss reason and five UTM fields right in the card. Reportkey builds a client report from them: which campaigns produced deals, how many were won, for what budget and why the rest were lost.

Sign up, add your OkoCRM API token and pick pipelines in a project. Your first report in 5 minutes.
  • The OkoCRM API token is entered once and used in every project.
  • New deals by the card's five UTM fields next to ad spend.
  • Won and lost deals by stage type, plus loss reasons per pipeline.
Sample Reportkey client report
Sample Reportkey client report
OkoCRM Deals, won amount, loss reasons, and UTM
30+
integrations
5 min
setup
14 days
trial
TL;DR

OkoCRM integration: an API token from the account is entered once, the project picks pipelines, and new deals by UTM source, won and lost deals, budget, loss reasons and manager results go into a recurring report next to Yandex Direct and VK Ads.

OkoCRM deals report for clients

OkoCRM organises work around the deal, and the deal card already holds much of what a marketing report needs: budget, pipeline, stage, owner, created and closed dates, loss reason and five tag fields — source, medium, campaign, content and term. You do not need to hunt for the custom field that stores the campaign, because it is standard. Reportkey reads deals through API v2 and shows them in the recurring report next to ad channels.

OkoCRM integration with an API token

The connection needs an API token from the OkoCRM account. It is entered once on the integrations page and, once checked, is available in every project. The report sees deals within the token owner’s rights, so if managers only see their own deals, issue the token from a team lead. When the token stops working, the connection asks for a replacement while the chosen pipelines stay in the project.

OkoCRM UTM report: new deals by source

The first block answers what advertising delivered:

  • New deals by creation date per day, week or month.
  • New deal budget — the sum of card budgets.
  • Source and campaign — from the deal tag fields.
  • Pipeline — for accounts with more than one.

Next to ad account spend this gives cost per deal for each campaign. Tags describe the first touch recorded by the form, not the full customer path.

Won and lost deals

The second block reports closing results by close date: won deals and won amount, lost deals and win rate. The OkoCRM stage type states clearly how a deal ended, so the report does not depend on stage names. All metrics are compared with the previous period.

OkoCRM loss reasons

Loss reasons in OkoCRM are defined per pipeline. The loss block shows lost deals and their budget for each reason. For an agency it is an argument: if most losses are about price, the conversation moves from ads to the offer. If managers skip the reason, the deal lands in a no-reason row, which is a signal too.

OkoCRM pipeline and managers

The owner breakdown shows new and won deals and won amount per manager. The current spread of open deals across stages can be shown too. The API returns a deal’s current stage, so this is a snapshot at build time and the path between stages is not included.

OkoCRM with Yandex Direct in one report

OkoCRM blocks usually follow advertising: Yandex Direct campaigns, VK Ads and Yandex Metrica visits and goals. Untagged calls can be covered with call tracking from Callibri or Calltouch, and Roistat calculates payback per deal.

A logo in the report and AI insights are not on every plan. Similar services are on the CRM integrations page, an example is the PPC agency demo report, and terms are under pricing.

Metrics

What goes into the OkoCRM report

These are the metrics that the OkoCRM integration already brings into Reportkey reports.

New deals
Won deals
Won amount
Lost deals
Win rate
What this integration adds to the report
Deals, won amount, loss reasons, and UTM
Pricing

OkoCRM reporting: plans and free trial

14 days free, no card required. Prices and plan limits are on the pricing page.

Use cases

Why teams connect OkoCRM to Reportkey

Real reporting jobs, typical pain points, and the outcomes teams get from OkoCRM in client reports.

Pain points
  • Campaign tags already sit in OkoCRM deal cards, but comparing them with ad spend takes an export and a pivot table.
  • Lost deals pile up with too expensive and no answer reasons, and the marketer learns about it at quarter end.
  • The owner sees a deal list in the CRM but no month-over-month comparison by manager.
OkoCRM
An agency responsible for website leads

Website forms pass tags into the OkoCRM deal. The monthly report shows, under each Yandex Direct campaign, how many deals it created, how many were won and for what budget, with losses split by reason.

OkoCRM
A company with two pipelines

Retail inquiries and wholesale requests go to different pipelines. Each gets its own block because stages, loss reasons and average deal differ.

OkoCRM
An owner running the sales team

A weekly email lists each manager's results: new deals, won deals and their budget. Bonus decisions rest on numbers instead of impressions.

Report preview

How OkoCRM appears inside the report

The report keeps the familiar Reportkey layout: source sections and period comparison.

Sample Reportkey client report
Sample Reportkey client report
OkoCRM block: deals by campaign

A campaign table from tags with new deals, budget, won deals and won amount, a pie chart of loss reasons and a weekly trend chart.

How to connect

Three steps to the first report

Connect the account once, choose the reporting scope, and save the setup for recurring client reports.

01
Connect the account
Save the OkoCRM connection once so the same datasource can be reused across recurring client reports.
02
Choose the reporting scope
Choose the OkoCRM account and pipelines that should supply leads, deals, and sales to the report.
03
Save the setup and generate the report
Keep the selected scope in the project and reuse the same report setup next time instead of connecting the source again.
FAQ

Frequently asked questions

Short answers about how the integration works in Reportkey today.

Where do I get OkoCRM access for the report?
An API token from your OkoCRM account. It is sent in the authorisation header, and deal access is limited to the rights of the token's owner. You enter it once on the Reportkey integrations page and then select it in projects.
How does Reportkey know a deal was won?
By the pipeline stage type. OkoCRM stages have a type: closed as won, lost, or a regular working stage. The report reads these types from each pipeline's settings, so renaming stages does not break won and lost counts.
Is the deal budget a payment?
No. The budget is the amount a manager entered in the deal card. If the price changed after negotiation and the card was not updated, the report keeps the old value. OkoCRM does not record payment in the budget field.
Why do some deals lack UTM fields?
The five tag fields are filled when a deal comes from a website or form that passes tags to OkoCRM. Deals from untracked calls, manual entry and messengers often have no tags and are grouped as untagged. Do not compare them one to one with ad account clicks.
How often is OkoCRM data refreshed, and why might it differ from the interface?
Deals are read on every report build; the API returns 30 per page, so a large account takes longer to load but nothing is lost. Differences from the interface usually come from dates: new deals count by creation date, won and lost by close date.

OkoCRM report: deals, budget, and loss reasons

Sign up, add your OkoCRM API token and pick pipelines in a project. Your first report in 5 minutes.

Start free