Field Mapping
Once the first conversion event arrives (from a connected CRM or a test manual webhook), True Conversions shows the raw fields received and lets you map them to the normalized fields the processing engine understands.
Access: open the account (client) → Mapeamento de campos (Field Mapping).
Account with a natively connected CRM (RD Station Marketing, RD Station CRM, Pipedrive, ActiveCampaign)? The account checklist already 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 if you want to map an extra field (e.g.,
cnpj,company_name) or if auto-mapping missed something you expected.
How the screen works
The table shows every field found in the most recent payload (flattened — nested objects become paths like deal[stage_title] or contact.email), a sample value, and a selector to choose the matching normalized field.
- Auto-mapping: common fields (email, phone, name, value, gclid, etc) are already suggested automatically, in both English and Portuguese (e.g.,
telefone,valor,empresa). - Each normalized field can only be used once — if two raw fields suggest the same target, only the first is kept.
- Click Save mapping to confirm.
If no payload has been received yet, the page tells you to send a test event to the account's webhook first.
Available normalized fields
| Field | Use |
|---|---|
email |
Primary matching identifier |
phone |
Matching identifier (E.164 format recommended) |
first_name / last_name |
Improves matching |
value |
Deal/conversion value |
currency |
Currency code (e.g., BRL) |
order_id |
Order/transaction ID (if applicable) |
event_name |
Event name (fallback when no stage field is configured) |
gclid |
Google Ads click ID — significantly improves matching |
wbraid / gbraid |
Google iOS click IDs (app/web) |
fbclid |
Meta click ID (from the URL) |
fbc / fbp |
Meta pixel cookies (sent unhashed) |
lead_id |
Meta Lead Ads lead ID (instant forms) |
utm_source / utm_campaign |
Campaign attribution |
conversion_time |
Event timestamp |
cnpj / website / company_name |
Help Lead Enrichment identify the company faster |
deal_id |
The deal's permanent ID in the CRM |
Validation rules
- Email or phone is required. Without at least one of the two, Save is blocked — these are the identifiers ad platforms use for matching.
- If you map gclid but no other field has been mapped yet, a warning appears encouraging the mapping — it significantly improves Google Ads match rate.
deal_id — required for Value Optimization
If the account uses (or will use) Value Optimization, map deal_id: it's the deal's permanent identifier in the CRM, which lets True Conversions link a deal's stages together over time (send the initial value, then restate it as the deal advances, up to Closed-Won).
Without deal_id mapped, value rules simply don't apply — events keep being processed and sent, just without the per-stage multipliers. This is the most common cause of "I set up Value Optimization and nothing seems to happen."
For natively connected CRMs (RD Station Marketing, RD Station CRM, Pipedrive, ActiveCampaign), deal_id already arrives in a standard field and usually doesn't even need manual mapping. For manual webhooks (RD CRM Free plan, custom CRMs), you need to map the correct field manually — often something like deal[id].
Finding the deal's stage field
This field is configured on the Value Optimization page, not here — but the way to find the right path uses this same events screen:
- Move a test deal to a new stage in the CRM.
- Go to the account page → Recent Events, find the most recent event and expand it.
- Open the Received Data section — it shows every flattened field of the raw payload, exactly as it arrived.
- Find the field containing the stage name (e.g.,
deal[stage_title]) and copy the exact path. - Paste that path into the Stage Field on the Value Optimization page.
The stage name configured in the stage table must match exactly the text the CRM sends — same spelling, accents, and casing.