Customer LTV

What gap it closes

A contact or company record in Bitrix24 (Alaio) lists the deals attached to that customer, and stops there: nothing adds the amounts up, and lost deals sit next to won ones. The lifetime total exists only in CRM reports, as a slice you have to leave the record to build. The Customer LTV field answers the question in place — total spend, number of purchases, average check and the date of the last one — and flags dormant customers.

How to set it up

1. Attach the field to a contact, company, deal or lead record, then open gear-icon settings (admin-only).
2. Data source — Won deals by default, or Paid invoices.
3. Whose LTV (on a deal/lead record) defaults to Automatic (contact, else company); pin By contact or By company instead.
4. Period defaults to All time; also Current year, Previous year, Last N days (number in N days (for "Last N days")).
5. Deal pipeline ID (empty = all) narrows the calculation to one pipeline.
6. Dormancy threshold, days (0 = no coloring) is 180 by default.
7. Calculate on behalf of — Current employee (their access rights apply) (default), or App installer (everyone sees the same numbers).

If the field stays empty

There is nobody to count: the deal or lead record has no contact and no company attached. Attach the customer first.

The purchases exist but the settings cut them off — a pipeline ID from another pipeline, or a period shorter than the age of the last deal.

The employee cannot see those deals. Under current-employee rights the field only sums what that person may open; switch to the installer mode.

Works together with

• Find deal — pulls one specific deal when you need a record rather than a total.
• Client local time — the other tile in the same record: when it is a decent hour to call.
• CRM reports and custom metrics — where built-in analytics ends and a number on the card begins.