Resolving “400 BAD_REQUEST” activation errors for Eloqua Destinations in Adobe Experience Platform
This article provides steps to resolve the 400 BAD_REQUEST
error encountered when activating audiences from Adobe Experience Platform (AEP) to Oracle Eloqua API-based destinations. This issue often arises due to specific characters in segment names, credential mismatches, or platform limitations. Following these steps will help ensure a smooth activation process.
Description description
Environment
Adobe Experience Platform
Issue/Symptoms
When activating audiences from AEP to Oracle Eloqua, a “400 BAD_REQUEST” error might occur. Common reasons include:
- Special characters (e.g., “|”, “-”, “&”) in segment names causing compatibility issues.
- Incorrect or invalid credentials used for Eloqua integration.
- Exceeding Oracle Eloqua’s limit of 250 custom contact fields.
Resolution resolution
-
Check segment name characters:
- Avoid using special characters such as “|”, “-”, or “&” in segment names.
- Rename segments using only alphanumeric characters and attempt reactivation.
-
Verify credentials:
- Ensure all credentials used for AEP-Eloqua connection are accurate.
- Validate these credentials independently of AEP to confirm proper functionality.
-
Review custom field limitations:
- Confirm that your Oracle Eloqua account does not exceed the 250 custom contact fields limit.
- Consult Adobe and Oracle documentation for any additional field limitations.
-
Test and seek support:
- Perform further testing with different audience configurations if issues persist, contact Oracle Eloqua’s support team for assistance with restrictions or errors originating from their system.
Related Readings
Oracle Eloqua API Documentation
By following these steps, you can effectively resolve common issues when activating audiences from AEP to Oracle Eloqua destinations.