Handling SFMC Data Feed Errors in Amperity

Overview

While ingesting Salesforce Marketing Cloud (SFMC) data via Amperity Couriers, users may encounter errors with certain feeds, such as Clicks or Bounces. These errors usually indicate minor issues with the data rows that exceed the system's allowable error threshold. This article explains the cause, impact, and recommended steps to address these errors.

Problem

When loading SFMC data feeds into Amperity, you might see errors similar to the following:

  1. Clicks Feed Error

    "The error indicates that the data feed "NCI:SFMC_Clicks' failed because the error rate for the feed (0.02%) exceeded the allowable limit (0.00%) . This might mean that there are too many issues with the data being ingested from this feed. To resolve this, please check the data quality and ensure that it meets the expected standards. If you're unsure how to proceed, I recommend reaching out to Amperity support for further assistance."

  2. Bounces Feed Error

    "This error indicates that the data feed named "NCI:Bounces" has failed because the error rate for this feed is 0.00%, which exceeds the allowable limit of 0.00%. Essentially, the system halted processing the feed due to an error condition. To resolve this issue, please ensure that the data being ingested is in the correct format and adheres to the expected quality standards. If you need further assistance, we recommend reaching out to Amperity support for help

Cause:

  • A few rows in the feed are malformed or do not meet expected data quality standards.

  • The system enforces a strict threshold for allowable errors; even minor discrepancies can cause feed failures.

Impact:

  • Feed processing may halt, preventing some or all data from being ingested.

  • Minor errors typically affect only a small fraction of the feed.

Recommended Solution

  1. Review Error Details

    • Check the rows flagged in the error logs to understand which data is causing the failure.

    • Most errors are minor and affect only a small percentage of the data.

  2. Ignore Minor Failures (Optional)

    • If the errors are insignificant, you can proceed by ignoring these failed rows.

    • For feeds like Clicks, an error rate slightly above 0% is often acceptable.

  3. Increase Error Threshold (Optional)

    • You can adjust the allowable error threshold in Amperity if minor errors are frequent.

  4. Verify Data Quality

    • Ensure all rows in the feed adhere to the expected format and quality standards.

    • Correct any malformed rows before attempting to reload the feed.

  5. Contact Amperity Support

    • If you are unsure about the errors or need guidance, reach out to Amperity support for assistance.

Best Practices

  • Regularly validate SFMC exports before ingestion.

  • Keep error thresholds documented for different feeds to decide when ignoring errors is safe.

Summary:
Minor errors in SFMC data feeds are common and often do not require full intervention. By reviewing errors, ensuring data quality, and optionally adjusting thresholds, feeds can continue to process successfully while keeping overall data integrity intact.