The Landing Page Form That Broke CRM Sync
A financial services firm uses Marketo forms embedded on Marketo landing pages, with a form that maps to CRM lead fields including 'Annual Revenue' (currency) and 'State' (picklist). The CRM has a validation rule requiring State to be one of 50 US values and Annual Revenue to be numeric. Recently, form submissions from a new campaign started failing to create CRM leads; the leads exist in Marketo but show sync errors. The form was recently changed to a free-text 'State' field and a 'Revenue' field with a '$' prefix in the label. Web tracking shows high form completion, but CRM lead creation is failing for ~30% of submissions. The firm also uses progressive profiling and has a hidden field capturing UTM source.
1. Diagnose the likely causes of the 30% CRM sync failure and explain the mechanism for each.
Read the worked answer
The failures cluster around field value/format mismatches between Marketo and the CRM:
- Free-text State. The CRM picklist only accepts 50 exact values. Free-text entries like 'California', 'CA', 'Calif.' or typos won't map to the picklist, so the CRM rejects the record. This alone explains a large share of failures.
- Revenue with '$' prefix. If users type '$1,000,000' or the label encourages a currency string, the value isn't numeric and fails the CRM numeric validation. The '$' in the label invites non-numeric entry.
- Progressive profiling + hidden UTM. Progressive profiling can leave previously captured fields blank or overwrite them; if State was captured earlier in a different format, the sync may push an invalid value. Hidden UTM fields are usually harmless but confirm they aren't mapped to constrained CRM fields.
The leads exist in Marketo because Marketo accepts free text; the CRM rejects on validation. So the failure is at the sync boundary, not at form capture.
2. Recommend the form and sync fixes, and explain how to prevent recurrence.
Read the worked answer
Fixes:
- Replace free-text State with a picklist whose values exactly match the CRM picklist. This eliminates the mismatch class entirely.
- Make Revenue a numeric field and remove the '$' from the label; add input validation or a numeric field type so only numbers are accepted. Optionally format currency display separately from stored value.
- Audit field mappings for the campaign to confirm no other constrained CRM fields receive free text.
- Re-sync the failed leads after correcting values (bulk update or re-request sync).
Prevention:
- Maintain a mapping standard: any field synced to a CRM picklist/numeric field must use matching form field types and values.
- Add a pre-launch checklist that tests a submission end-to-end into the CRM sandbox.
- Monitor sync errors as an ongoing report, not just at launch.