You are here:
Troubleshooting Mapping Errors in Marketing Intelligence
TotalConnect automatically validates your data mapping to meet system requirements during ingestion. These validations detect errors like missing templates, mismatched data types, or unmapped primary keys and provide guidance for resolution. Improving data accuracy enhances analysis and reporting quality.
| Validation | Description | Resolution |
|---|---|---|
| Template Not Found | The system couldn't locate the selected Data Model Template for mapping fields. This error typically occurs if the template doesn’t exist or was deleted | Select an existing template or create a new one to continue. |
| Missing Date Field | A date field isn’t mapped. Date fields are essential for time-based analysis and reporting. | Map a date-type field in your data to the Date field to continue. |
| Invalid Field Mapping | Some of the fields in your data don’t correspond to valid schema fields in the selected template. | Review and adjust the field mappings to make sure all the fields match the template's schema. |
| Data Type Mismatch | The data type of a mapped field doesn’t match the expected type in the schema. For example, a text field might be mapped to a numeric field. | Update the mappings or adjust the data type in the preview so that each field aligns with the correct data type. |
| Primary Key Not Mapped | If you map an attribute, such as Campaign Details, you must also include its associated primary key, campaignId, to ensure data integrity. | Make sure the primary key for any mapped attributes is included in the mapping. |
| Field Length Exceeds Limit | A field exceeds the maximum allowed length in the schema. | Shorten the field or adjust the mapping to comply with the limit. |
| Missing Media Buy ID | MediaBuyId must be mapped when fields like campaignId, channelId, productId, or deviceId are included for proper linking. | Map the mediaBuyId field to continue. |
Did this article solve your issue?
Let us know so we can improve!
