Bitrix24 Custom Fields
Track your Bitrix24 UF_ deal fields inside Astervis.
Your Bitrix24 deals carry more than the standard title, stage, and amount. Most
teams add their own custom fields — a UF_CRM_ payment method, a delivery
region, a contract-signed flag, a callback date — and those fields are often the
ones you actually report on. Astervis captures them alongside every synced deal,
so the data you care about shows up in your analytics, not just in Bitrix24.
This page explains how Astervis discovers your custom fields, how you choose which ones to track, how their values are stored, and how to put them to work in reports and dashboards.
Custom fields ride on top of the Bitrix24 integration. You need deals syncing first — once that's connected, custom fields are a setting, not a separate setup.
What this gives you
Bitrix24 exposes custom deal fields through its API with codes that start with
UF_CRM_ (the platform's convention for user fields). Out of the box, those fields
travel with your deals but stay opaque to analytics — there's no way to chart
"average deal size by payment method" if Astervis never learned what your payment-method
field is.
Custom-field tracking closes that gap. For every deal Astervis syncs, the values of the fields you've chosen are pulled in and stored next to the deal, ready to filter, group, and visualise like any other column.
How discovery works
You don't type field codes by hand. Astervis asks Bitrix24 what custom fields exist and presents them to you.
Astervis reads your field catalogue
Before each deal sync, Astervis calls Bitrix24's crm.deal.userfield.list
endpoint. This returns the full definition of every custom deal field — its
UF_ code, its type (string, number, date, boolean, enumeration, and so on),
and, for dropdown-style fields, the list of allowed values with their labels.
You pick which fields to track
In the admin panel, open Settings → Integrations → Bitrix24 and find the Custom Fields section. Every discovered field is listed with its name and type. Toggle on the ones you want to track and save.
Values flow in with your deals
On the next sync, the deal request asks Bitrix24 for those fields explicitly
(it selects UF_* alongside the standard columns), and each tracked value is
written next to its deal.
Discovery runs automatically on every sync, so new custom fields you create in Bitrix24 appear in the list without any reconnect. Just toggle the new ones on when you're ready to track them.
How values are stored
Under the hood, custom-field values live in a wide satellite table linked to your deals — the same pattern Salesforce uses for custom fields. Rather than adding a new database column every time you track a new field (which would mean a schema change), Astervis pre-allocates a fixed pool of typed slots and maps each tracked field onto the slot that fits its type.
There are 60 slots in total, split by type:
| Type | Slots | Used for |
|---|---|---|
| Text | 40 | Strings, long text, URLs, and enumeration labels |
| Numeric | 10 | Integers and decimals (amounts, counts, scores) |
| Date | 5 | Dates and date-times |
| Boolean | 5 | Yes/no and checkbox flags |
Two tables work together:
| Table | What it holds |
|---|---|
integration_custom_field_definitions | The catalogue — which UF_ field maps to which slot, plus its type and label. |
integration_deal_custom_fields | The values — one row per deal, holding that deal's tracked field values across the slots. |
The first table records the mapping (field UF_CRM_PAYMENT_TYPE → text slot 3,
for example); the second holds the values for each deal. Because the slots are
pre-allocated, tracking a new field is just claiming a free slot of the right type —
no migration, no downtime.
Enumeration fields store labels, not IDs
Dropdown (enumeration) fields in Bitrix24 store an internal numeric ID for each
option — a value like 52 means nothing on its own. When Astervis discovers an
enum field, it reads the option labels from the field definition and stores the
human-readable label (e.g. Cash, Card, Bank transfer) in a text slot,
not the ID. That means your charts and filters read naturally without you having
to maintain a lookup table.
You can track up to 60 custom fields total, within the per-type limits above (40 text, 10 numeric, 5 date, 5 boolean). Enumeration fields count against the text budget because their labels are stored as text. If you hit a limit, untrack a field you no longer report on to free its slot.
Using custom fields in reports and dashboards
Once values are flowing, tracked custom fields behave like first-class deal attributes throughout the analytics layer. Because the sales widgets are built on your synced Bitrix24 deals, your custom dimensions slot right in:
- Group and break down — split deal counts or average sale price by a custom dimension, such as deals by payment method or by delivery region.
- Filter — narrow any deal-based widget to a subset, like only deals where the "contract signed" boolean is true.
- Trend over time — combine a date custom field (a callback date, a contract date) with your other time-series metrics.
Astervis analytics widgets show numeric values only — no currency symbols or codes. A custom amount field will display as a plain number, consistent with the rest of your sales dashboards.
Frequently asked
Next steps
Last updated on