Payment missing in Metrica: check amoCRM ClientId and Yclid
Diagnose the gap between an enquiry and a payment: amoCRM fields, source data and conversion events. Missing identifiers do not come with a promise of historical recovery.
An enquiry and a payment are separate events
First separate recording a payment from attributing it to an advertising visit. A deal may contain a value and a status without the identifier required for attribution. A status change does not create that link.
What to check in the deal
Check whether ClientId or Yclid is stored, which fields receive it and where it may be lost. Trace a website enquiry or phone call through contact and deal creation, repeat enquiries and the integration. ClientId and Yclid are different identifiers; arbitrary values cannot replace them.
When ClientId is missing
Establish whether Yclid was retained and whether it fits the intended transfer method. Check the source and integration configuration. If neither ClientId nor Yclid nor an evidenced attribution link exists, retrospective advertising attribution cannot be promised. Fixing collection for new enquiries does not automatically recover history.
Check the payment event
Agree what counts as a payment, where its value and date are recorded and which event should reach Metrica. Use an agreed test scenario to trace the enquiry to the event and check duplicate prevention. A successful submission and a visible report entry are separate checks.
Where VibeMetrics fits
VibeMetrics is a separate product in private beta. It is considered after checking the pipeline, attribution fields and amoCRM permissions. It does not replace missing identifiers and is not a public marketplace release. The first task is to find the broken link, not to select a product in advance.
Start with the scenario
Describe the enquiry source, the payment stage and the expected report. Do not send credentials, tokens or customer personal data in the initial message. Agree the diagnostic scope and acceptance checks after clarifying the task.