Exporting audiences to X (Twitter) destination results in bad request or authentication error
Exporting audiences from Adobe Experience Platform (AEP) to the X (Twitter) destination sometimes triggers a 400 BAD_REQUESTerror stating the request isn’t authenticated. This occurs when audience or segment names contain unsupported special characters, which prevents activation and export.
To fix this, review and update audience names and remove characters that the X (Twitter) destination doesn’t support.
Description description
Environment
- Product: Adobe Experience Platform (AEP)
- Constraint: Exporting audiences to the X (Twitter) destination
Issue/Symptoms
- Exporting or activating an audience in AEP results in a 400 BAD_REQUEST authentication error.
- Audiences containing unsupported special characters in their names can’t be activated or exported.
Resolution resolution
To resolve the issue, follow these steps:
- In the Adobe Experience Platform UI, go to Audiences and review the names of all audiences and segments intended for export to the X (Twitter) destination.
- Remove unsupported special characters from audience names, descriptions, and audience mapping names. Unsupported characters include:
+ & , % : ; @ / \ = ? $ \n. - Save the updated name without unsupported characters.
- Activate the audience again by selecting the X (Twitter) destination from the activation workflow.
- Confirm the export completes successfully without a 400 BAD_REQUESTerror.
- If the error continues, verify that all prerequisites for connecting AEP to X (Twitter) are met.
Related reading
- Twitter Custom Audiences connection under Destinations Guide in Experience Platform.
- Activate audiences to streaming profile export destinations under Destinations Guide in Experience Platform.
recommendation-more-help
3d58f420-19b5-47a0-a122-5c9dab55ec7f