Google's Data Manager API includes FIELD_VALUE_TOO_SHORT for values that fail a field's length rule. A WordPress payload can become too short because the source is empty, uses a placeholder, was truncated, lost a country prefix, was hashed before normalization, contains a partially stored digest, or mapped the wrong field. Padding or inventing characters creates worse data and may violate consent expectations.
Use this for WordPress lead uploads, CRM audiences, enhanced conversions, offline events, store sales, or custom Data Manager API integrations that reject individual records or requests for short values.
Quick answer
Data Manager API FIELD_VALUE_TOO_SHORT Boundary Test should be handled with a narrow evidence-first workflow: capture structured errors, trace every transform, measure privately, then verify the result before making broader changes.
What to check first
- Preserve the full Google error details, field path, reason, request ID, record index, destination, and validation mode.
- Trace the rejected value back through WordPress form storage, CRM export, transformation, normalization, hashing, serialization, and request construction.
- Measure length and encoding at every step without printing raw customer identifiers into shared logs.
- Build synthetic boundary cases for empty, whitespace, placeholder, minimum-minus-one, minimum, malformed hash, and wrong-field values.
- Decide whether to correct from an authoritative source, omit the optional field, reject the record, or stop the batch for a required-field failure.
Diagnostic table
Use this table to keep the work practical. It connects the symptom to evidence and a verification step.
| Action | Evidence to collect | How to verify |
|---|
| Capture structured errors | Preserve the full Google error details, field path, reason, request ID, record index, destination, and validation mode. | The corrected field comes from the authoritative source and documented normalization order. |
| Trace every transform | Trace the rejected value back through WordPress form storage, CRM export, transformation, normalization, hashing, serialization, and request construction. | Synthetic minimum and minimum-minus-one cases produce the expected local validation result. |
| Measure privately | Measure length and encoding at every step without printing raw customer identifiers into shared logs. | Raw customer values and hashes are not exposed in application or support logs. |
| Test boundaries | Build synthetic boundary cases for empty, whitespace, placeholder, minimum-minus-one, minimum, malformed hash, and wrong-field values. | Accepted and rejected record counts reconcile to the source batch and API diagnostics. |
Why this usually happens
- Normalization after hashing can destroy the expected digest format.
- A form field can contain a placeholder such as N/A that passes local required validation but fails the API field rule.
- Database columns or CSV tools can truncate a digest or international identifier.
- A mapping bug can send a short postal fragment into a phone or hashed identifier field.
Useful command or data shape
Adapt paths, IDs, and privacy handling to the site before running commands or storing data on production.
validation_evidence:
field_path: events[3].user_data.phone_numbers[0]
source_present: true
normalized_length: 3
encoding: plain_text
expected_policy: e164_then_hash_if_required
action: reject_and_repair_mapping
Safe fix order
Do the work in a sequence that makes each result easy to prove. Stop if a step produces new evidence that changes the incident scope.
- Capture structured errors
- Trace every transform
- Measure privately
- Test boundaries
- Choose omit or reject
Decision rule
Never pad, duplicate, or invent a customer value to satisfy a length check. Correct it from an authoritative consented source, omit it when optional, or reject the record with a durable reason and owner.
What to tell the client or owner
Share the request ID, field path, record index, destination, source system, measured lengths, encoding state, normalization order, local decision, and accepted and rejected counts without raw identifiers.
Production verification checklist
- The corrected field comes from the authoritative source and documented normalization order.
- Synthetic minimum and minimum-minus-one cases produce the expected local validation result.
- Raw customer values and hashes are not exposed in application or support logs.
- Accepted and rejected record counts reconcile to the source batch and API diagnostics.
Mistakes to avoid
- Do not pad the value with zeros or spaces.
- Do not log the complete customer identifier while debugging length.
- Do not normalize an already hashed value.
- Do not retry a permanent boundary failure without changing the source or mapping.
Questions teams ask during testing
Does the enum publish one universal minimum length?
No. The reason identifies a length failure, while the field path and destination determine the relevant rule. Preserve structured details and validate against the current field contract.
Can the record be sent without that field?
Only when the destination and use case make it optional and the remaining data is valid and consented. Do not omit a required field merely to get an accepted response.
When HandL WP should help
HandL WP should help when WordPress forms or CRM exports produce recurring Data Manager validation errors. We can trace the field safely through storage, mapping, hashing, and upload without fabricating customer data.
If this is active on a production site, repair Data Manager API field validation.
Related HandL WP guides
Use these related guides when the same issue touches tracking, security, checkout, or crawler visibility.
Helpful references