Incorrect Attribute Mapping with CRM Fields

Issue

Data is ingested using a field mapping that does not reflect the intended Attribute. For example, Data Cloud’s Mobile attribute is mapped to the CRM's PhoneNumber field, but later, the expectation is for Mobile to be mapped to the Phone field.

Possible Cause

The field-to-attribute mapping was incorrectly configured during ingestion setup.

Advanced Troubleshooting

Incorrect mappings require backend clean up and full re-ingestion. In case of an ingestion due to incorrect mapping, reach out to the Acqueon team for support.

Warning

Exercise caution when configuring field mappings before ingestion.

Why a Simple Re-ingestion Does Not Fix It

This is because:

1. Ingestion is incremental and timestamp-based.

2. The system fetches records based on the Last Time Stamp tracked during the previous ingestion.

3. For instance, if a Source previously ingested 1 million records, and only 10K are present in the CRM now, the system will not pull the original 1 million again.

4. This means existing records mapped incorrectly remain untouched.