Configure custom CRM fields

Metrikia covers four universal concepts (lifecycle, deal stage, deal amount, closing date) via the CRM mapping wizard. For anything else, for instance a financed amount on a leasing deal, a "signed online" boolean, or a first-contact date, open the Custom fields step and declare those fields yourself. The value lands inside leads.metadata on the Metrikia side and stays queryable from your views and exports.

Prerequisites

• Your HubSpot CRM is connected to Metrikia and an initial sync has already run.
• You are owner or admin on the Metrikia tenant.
• The HubSpot properties you want to capture exist and have values on at least one contact.

Step 1: Open the wizard

1. Go to /app/settings, Integrations tab.
2. Find your HubSpot connection under My connections.
3. Click Configure mapping on the HubSpot tile.
4. Skip steps 1 to 3 if they are already configured (source field, analyze, mapping).
5. On the Custom fields step (marked "Optional" in the stepper), the list of active mappings shows up.

Step 2: Add a mapping

In the Add a mapping section, fill the three fields:

• CRM source field: pick the HubSpot property from the dropdown. The technical key (e.g. montant_finance) is shown next to the label.
• Metrikia metadata key: type the key Metrikia will store. Example: financed_amount_ht. Lowercase letters, digits, underscores and dots only, 60 characters max.
• Value type: tell Metrikia how to coerce the raw CRM value. Five types are available: 
  • Text: raw value, e.g. "Premium".
  • Amount (€): Metrikia parses 18,750.00 €, 18750.00, negatives allowed, stored in cents internally.
  • Boolean (yes/no): recognises yes, no, true, false, 1, 0.
  • Date: ISO 8601 or common formats (2026-03-14, 03/14/2026).
  • Integer: for scores, durations in months, etc.

Click Save. The mapping appears immediately in the Active mappings table.

Concrete example: financed amount

You run real-estate leasing and your signed deals carry a montant_finance property in HubSpot. You want to expose it in Metrikia for your internal mROAS computations:

1. CRM source field: montant_finance.
2. Metrikia metadata key: financed_amount_ht.
3. Value type: Amount (€).
4. Save.

From the next synced contact onwards, the value is captured in leads.metadata.financed_amount_ht on the Metrikia side, normalised in cents.

Limits

• 100 mappings max per integration. A counter at the top of the list turns amber from 80 and red from 95. If you hit the cap, delete an unused mapping.
• A given source property can only be mapped once. If the field you are looking for is missing from the dropdown, it is already mapped.
• A given Metrikia key can only be reused once. Pick a unique name per concept (financed_amount_ht, not amount everywhere).

Delete a mapping

Click the trash icon on a row. A confirmation explains the consequence: Metrikia stops extracting that property on next syncs, but values already stored on existing leads stay in place.

Backfilling existing leads

When you add a new mapping, only contacts modified or created after the addition receive the value automatically. To apply it retroactively to all leads that were already imported, contact Metrikia support: the team can trigger a full resync that walks the HubSpot history.

Common errors

• "Invalid format" on the key: your key contains spaces, uppercase letters or special characters. Replace with underscores, e.g. financed amount becomes financed_amount.
• "This source field is already mapped": you already created a mapping for that property. Find it in the active table and edit it if needed (delete then recreate to change the type).
• The expected value does not appear on the lead: check that the HubSpot contact has the property filled in. Metrikia does not create the key while the source value is empty.

Ideas and roadmap

To suggest an additional type (e.g. PERCENT, URL, ENUM), submit it through Ideas and Roadmap in Settings so we can prioritise it.