Overview
If a file does not behave as expected after upload, it may be due to rejected rows, formatting issues, processing delays, or unmatched households. This article applies to CRM uploads, location uploads, and offline attribution uploads.
When you upload data to MNTN, the platform validates the records and displays an Upload Summary showing how the file was processed. This summary helps you understand whether records were accepted or rejected before they are processed for use in MNTN.
This article explains how to review upload results and troubleshoot common issues, including:
Rejected rows during upload
Disassociated households
Lists that remain in processing
Review Upload Summary
After uploading a file, MNTN displays an Upload Summary showing how the file was processed. This behavior is consistent across CRM uploads, location uploads, and offline attribution uploads.
The summary includes:
Rows processed | The number of rows evaluated from the uploaded file |
Rows accepted | Records successfully processed |
Rows rejected | Records that failed validation |
These values help you confirm how many records from the uploaded file were successfully processed.
If rows are rejected, you can download an error report to review the records that failed validation.
Download file with errors
If rows fail validation during upload, click Download File with errors .
⚠️ Warning: Download the error report before exiting. MNTN does not store error reports for privacy reasons, so you’ll need to re-upload the file to generate it again if you navigate away.
The error report shows:
The rejected records
The reason each record failed validation
Review the report to identify issues in the uploaded file. After correcting the file, upload the updated version if needed.
⚠️ Warning: Rejected rows do not prevent accepted rows from being processed, but they may reduce the number of records successfully processed.
High invalid row confirmation
When 20–30% of rows are rejected, a confirmation message appears before the upload can proceed.
Troubleshoot Other Issues
Disassociated households (CRM Uploads)
Due to enhancements to MNTN’s formatting requirements and matching process, lists uploaded before October 2023 may not reflect the current targetable household volume.
If you are using an older list, consider uploading a new file that follows the current formatting requirements.
Prolonged processing
If your list remains in processing after 72 hours, it's possible that your file didn't meet our prerequisites. Review the following:
Prerequisite | What to do |
Formatting | Ensure your email records adhere to our formatting requirements. For CRM pre-hashed lists, review formatting before hashing to guarantee conformity. Use the SHA-256 hashing function with all uppercase characters. |
Work email addresses CRM uploads only | If your staff uses VPNs or international IPs, matching households with masked emails/IPs might not be feasible. To exclude employee emails, you can upload CSV file of IPs and identify IP addresses via: |
Small audience size | When MNTN's cross-device identity graph can't identify households linked to your email records, targeting becomes challenging. For better targeting, consolidate multiple smaller lists into a more substantial email size. |
⚠️ Warning: Keep in mind we will only match households within the United States.