Skip to content
Reportkey
Roistat
Roistat via Yandex Metrica

Roistat integration for client reports

Roistat can push calls into Yandex Metrica together with talk time, wait time and a missed-call flag. Reportkey turns that data into a client report where calls sit next to ads, SEO and on-site behaviour.

14 days free · no card required · all integrations
Connect the Metrica counter Roistat sends calls to and get a report with missed calls, wait time and call sources. Your first report in 5 minutes.
  • Roistat is on the list of call trackers connected to Yandex Metrica.
  • Missed calls, wait time and talk time appear in one report block.
  • AI insights in reports and white-label branding (not on every plan).
Sample Reportkey report with calls and call sources
Sample Reportkey report with calls and call sources
RoistatRoistat calls and Yandex Metrica call-tracking attributes
30+
integrations
5 min
setup
14 days
trial

Roistat in client reports: calls next to ads and SEO

Clients usually adopt Roistat for end-to-end analytics, but agency reporting needs something simpler: how many calls came in, how many were lost and which channels drove them. Reportkey reads the calls Roistat has already sent to Yandex Metrica and places them in one report with paid search, SEO and website behaviour. The client sees phone enquiries as part of the whole picture rather than as a separate tool with its own logic.

Other ways to bring calls into a report are listed under call tracking and CRM sources.

How Roistat sends calls to Yandex Metrica

Call export to Metrica is switched on in Roistat’s settings. With each call Roistat passes the number, time, visitor ID, talk time, wait time, a missed flag and the page URL. That richer payload is why more fields get filled for Roistat than for trackers that only send goals. Reportkey connects to the Metrica counter that receives Roistat calls and goals, with no separate Roistat connection.

Missed calls, wait and talk time

The Calls block in the report shows:

  • Total calls — phone enquiries for the period and the change versus the last one.
  • Missed calls — enquiries nobody answered; a direct prompt for the client to check staffing.
  • Average wait time before answer — how quickly calls are picked up; rising wait time often explains rising misses.
  • Average talk time — how substantial the conversations are.
  • Unique calls and first-time callers — new people versus repeat callers.
  • Roistat call goal — visit-to-call conversion when the goal is selected in the project.

Blocks get AI summaries you can keep as is or edit.

Dynamic vs static call tracking

Roistat’s dynamic scenario swaps the number per visitor, so Metrica knows the channel behind each call. The static scenario is tied to a placement and sends neither source nor goals. As a result, the channel block and the top 10 call sources reflect dynamic calls only, while the summary counts everything. Reportkey also reads totals for the whole counter, so a second tracker writing to the same counter will be added to Roistat’s numbers.

Reportkey report vs Roistat dashboard

Roistat’s dashboard is an analyst’s tool with attribution models, sales and revenue. A Reportkey report is a client document covering several channels at once. Two common set-ups:

For a different tracker, see Calltouch: calls via Yandex Metrica and a direct API or K50, another tracker that reports via Metrica.

Reportkey reads Roistat through Metrica, so revenue and ROI from Roistat’s analytics stay out of the report. Plans are on the pricing page.

Metrics

What goes into the Roistat report

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

Roistat calls from Yandex Metrica
Roistat call source attribution
Roistat answered and missed-call signals
What this integration adds to the report
Roistat calls and Yandex Metrica call-tracking attributes
Pricing

Roistat 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 Roistat to Reportkey

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

Pain points
  • Roistat's end-to-end analytics is a tool for the agency, but the client needs one readable document with phone enquiries and advertising side by side.
  • Missed calls and long wait times are visible in Roistat, yet they rarely reach the regular report the client's management reads.
  • Roistat's static and dynamic scenarios attribute sources differently, which is easy to miss when a report is assembled by hand.
Roistat
Lead-gen agency: a conversation about sales handling

The missed-call share and average wait time show the client that some enquiries are lost after the ad did its job, which moves the discussion from bids to call handling.

Roistat
In-house marketer: calls and channels for leadership

A monthly summary of Roistat calls next to traffic and site goals gives leadership one picture instead of several exports.

Report preview

How Roistat appears inside the report

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

Sample Reportkey report with calls and call sources
Sample Reportkey report with calls and call sources
Roistat calls in the report summary

Report fragment: total calls, missed calls, average hold and talk time from Metrica, compared with the previous period.

How to connect

Three steps to the first report

Connect Yandex Metrica once, choose the counter that receives the calls, and save the setup for recurring client reports.

01
Connect Yandex Metrica
Reportkey reads Roistat calls from the Yandex Metrica counter, so you connect Metrica rather than the call tracker. The access is saved once for all projects.
02
Choose the reporting scope
Select the Yandex Metrica counter that receives Roistat calls: the report shows the call fields the service sends there.
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.

How does Reportkey get calls from Roistat?
Roistat sends calls to the client's Yandex Metrica counter. Reportkey connects to that counter and builds the call blocks when the counter has Metrica's call feature enabled. No access to the Roistat account is needed.
Why don't yesterday's calls match Roistat?
Roistat can take up to 5 hours to process a call for Metrica, and Metrica adds up to 3 more. Data usually appears about a day after the scenario is switched on. The goal time in Metrica is the visit time, not the call time, so calls near midnight may land on a neighbouring date.
Will the report show Roistat revenue and ROI?
No. Visits, leads, sales, revenue and ROI from Roistat's own analytics are not loaded into Reportkey: it reads Roistat data through Yandex Metrica, so the report covers the calls Roistat passes to the counter.
Why do only some Roistat calls have a source?
Roistat's static scenario does not send the traffic source or goals. Channel and source blocks therefore reflect dynamic call tracking only, while the overall call total includes both scenarios.
Can a Roistat call be used in a Metrica composite goal?
No. According to Roistat's help centre, calls cannot be passed into composite goals. Use a separate call goal or the call blocks instead.

Roistat integration for client reports

Connect the Metrica counter Roistat sends calls to and get a report with missed calls, wait time and call sources. Your first report in 5 minutes.

Start free