Field Mapping

After the first conversion event arrives from a connected CRM or a manual webhook test, True Conversions shows the raw fields it received and lets you map them to normalized fields used by processing.

Open the account → Mapeamento de campos (Field Mapping).

Using a native CRM connection (RD Station Marketing, RD Station CRM, Pipedrive, or ActiveCampaign)? The account checklist shows this step as Automático — campos do CRM já mapeados (Automatic — CRM fields already mapped). In most cases, you can skip this page. Use it only to map an extra field, such as cnpj or company_name, or when an expected automatic mapping is missing.

How the page works

The table lists fields found in the latest payload, a sample value, and a selector for the corresponding normalized field. Nested objects are flattened into paths such as deal[stage_title] or contact.email.

Automatic mapping: common fields such as email, phone, name, value, and gclid are suggested automatically in English and Portuguese.
A normalized field can be used only once. If two raw fields suggest the same destination, only the first is kept.
Select Salvar mapeamento (Save mapping) to confirm.

If no payload has arrived yet, the page asks you to send a test event to the account webhook first.

Available normalized fields

Field	Use
`email`	Main matching identifier
`phone`	Matching identifier (E.164 format recommended)
`first_name` / `last_name`	Improves matching
`value`	Real deal revenue, when it will be sent
`currency`	Revenue currency code, such as `BRL`
`order_id`	Order/transaction ID, if applicable
`event_name`	Event name; fallback when no stage field is configured
`gclid`	Google Ads click ID; greatly improves matching
`wbraid` / `gbraid`	Google click IDs for iOS app/web
`fbclid`	Meta click ID from the URL
`fbc` / `fbp`	Meta pixel cookies, sent without hashing
`lead_id`	Meta Lead Ads lead ID
`utm_source` / `utm_campaign`	Campaign attribution
`conversion_time`	Event timestamp
`cnpj` / `website` / `company_name`	Additional company data
`deal_id`	The CRM's permanent deal ID

Validation rules

Email or phone is required. Saving is blocked without at least one because ad platforms use them for matching.
If you map gclid but no other field yet, a prompt encourages you to add matching data; it significantly improves Google matching.

`deal_id`: required for Journey stages

Map deal_id, the CRM's permanent deal identifier. It is required for every Conversion Journey milestone because it identifies stages belonging to the same deal.

With an enabled and configured Journey, an event without deal_id is skipped; it is not sent as a plain conversion. This avoids assigning a stage to the wrong deal.

For native CRM connections (RD Station Marketing, RD Station CRM, Pipedrive, and ActiveCampaign), standard fields normally already include deal_id, without manual mapping. For manual webhooks, such as RD CRM Free or a custom CRM, map the correct field — for example deal[id] or deal_id.

Find the deal stage field

The stage field is configured on Jornada de conversão (Conversion Journey), not here. Use this page to find the correct path:

Move a test deal to a new CRM stage.
Go to the account → Eventos recentes (Recent Events), find the newest event, and expand it.
Open Dados recebidos (Received Data), which shows all flattened raw-payload fields.
Find the field containing the stage name, such as deal[stage_title], and copy the exact path.
Paste it into Campo de etapa (Stage field) in Conversion Journey.