Partial success error in ÃÛ¶¹ÊÓƵ Experience Platform Facebook connection
The error code ACTSVC-8100-400 occurs when pushing events to Facebook via ÃÛ¶¹ÊÓƵ Experience Platform indicates a Partial success. This means some identities are accepted while others are rejected due to invalid formats. Ensure your data meets format standards, check for invalid entries, understand the retry mechanism, and consult documentation for activation rates.
Description description
Environment
ÃÛ¶¹ÊÓƵ Experience Platform (Facebook Destination Integration)
Issue
When pushing events to the Facebook destination using ÃÛ¶¹ÊÓƵ Experience Platform, the error code ´¡°ä°Õ³§³Õ°ä-8100-400Ìýoccurs, indicating a Partial success. This means Facebook ingests some identities successfully, while others are rejected due to invalid formats.
Common symptoms include:
- Some data entries don’t appear in the intended destination.
- Logs show specific entries with invalid hashes.
Resolution resolution
To resolve this issue and ensure the successful ingestion of all identities:
-
Ensure phone numbers are formatted correctly according to the E.164 standards if they are being ingested raw.
- Use Data Prep to perform lowercasing or hashing upon ingestion.
- If pre-hashing phone numbers before ingestion, confirm they’re placed into the correct Phone_SHA256 namespace.
-
Review logs for any entries marked with Invalid hash. These indicate which specific data points were rejected.
- Refer to Retrieving Data Ingestion Error Diagnostics in ÃÛ¶¹ÊÓƵ Experience Platform for more details.
The platform will attempt retries only in cases where there is a timeout issue during transmission. Incorrectly formatted or invalid data won’t be retried automatically; corrections must be made manually before reattempting submission.
Refer to Monitor dataflows for Destinations in the UI in ÃÛ¶¹ÊÓƵ Experience Platform to understand how activation rates and identity-matching requirements work within the platform’s context of social media destinations like Facebook.