Less manual reconciliation
Sales leaders see stage facts inside CRM instead of collecting dates from notes, tasks, and spreadsheets.
Private betaPrivate beta for amoCRM teams
VibeMetrics records amoCRM stage movement and prepares events for analytics
An Arttema.pro product layer for sales leaders: the widget creates date_time fields named “Дата этапа: <stage>”, connects an account-level status_lead webhook, and sends verified events to Yandex Metrika when ClientId or Yclid is present.
VibeMetrics
amoCRM analytics layer
Access is configured manually after a short review of the funnel, attribution fields, and amoCRM permissions. There is no public marketplace release yet.
status_lead webhook
On settings save, the widget syncs an account-level amoCRM webhook, so every stage does not need its own Digital Pipeline block.
Дата этапа: <stage>
For the selected pipeline, date_time fields are created in the deal so stage history remains in amoCRM.
first_only
A filled stage date is not overwritten; the first entry stays reliable for reporting and retrospectives.
Workflow
One stage transition becomes CRM evidence and an analytics event
The page only promises the flow that exists in the source connector: amoCRM webhook, stage timestamp write-back, first_only protection, and Metrika delivery when attribution exists.
01
A deal changes stage
amoCRM sends status_lead to the VibeMetrics backend through an account-level webhook.
02
The stage is stamped in the deal
The widget writes the date to “Дата этапа: <stage>” and keeps the first entry with first_only.
03
The event is prepared for Metrika
If ClientId or Yclid exists, the event is delivered server-side via OAuth or exported as offline CSV.
What VibeMetrics gives the team
A private-beta product for teams that need stage-transition evidence inside amoCRM and a cleaner bridge to advertising analytics without manual exports.
Cleaner ad attribution
Sales events can be linked to ClientId/Yclid and sent to Metrika as verified conversions.
No CRM migration
VibeMetrics works on top of the existing amoCRM setup and does not replace funnels, roles, fields, or sales processes.
Integration proof
Live boundary first, roadmap second
The current product boundary is intentionally narrow: amoCRM stage facts and Yandex Metrika delivery. Roistat stays visible as the next stage, not as a live claim.
amoCRM
Private widget, status_lead webhook, stage date_time field creation, and deal write-back.
Yandex Metrika
Server-side OAuth delivery and offline conversion CSV when ClientId or Yclid is available.
Duplicate control
first_only protects the first stage-entry timestamp from repeated overwrites.
Roistat
The next product stage: event delivery through the same CrmEvent boundary after API and mapping validation.
Extended diagnostics
Reports for skipped events, missing identifiers, and CRM-to-analytics connection quality.
Fit and boundaries
The private beta is strongest when CRM discipline and attribution fields already exist.
Good fit
amoCRM is already used by sales
There is a working funnel and the manager wants better visibility into stage movement.
Deals include attribution identifiers
ClientId, Yclid, or similar fields are already captured or can be added through forms and integrations.
Private beta is acceptable
The team is ready to begin with diagnostics, a test funnel, and event verification before scaling.
Not the right fit yet
A public marketplace widget is required
The product is currently configured as a private beta without a public amoCRM marketplace promise.
Roistat must be live today
Roistat is the next product stage: the boundary exists, but live delivery is not promised on this page.
CRM has no stable attribution fields
Without ClientId/Yclid, Metrika events will be incomplete; identifier capture should be fixed first.
FAQ
Questions before beta access
Is this a public amoCRM widget?
No. VibeMetrics is currently connected as a private beta after amoCRM account and funnel diagnostics.
Which events are used?
The base source is the account-level amoCRM status_lead webhook that reports deal stage transitions.
What is written to the deal?
For the selected pipeline, date_time fields named “Дата этапа: <stage>” are created. In first_only mode, an already-filled field is not overwritten.
When does an event go to Yandex Metrika?
When the deal has ClientId or Yclid and Metrika access is configured. Delivery is available server-side via OAuth and as offline CSV.
Is Roistat already live?
No. Roistat is described as a roadmap/next-stage capability, not a live feature.
VibeMetrics
Check whether your amoCRM account is ready
We will review the funnel, attribution fields, Metrika access, and beta launch boundary before touching production data.