Failed Audience Activation to Facebook Destination | Community
Skip to main content
RyanMoravick
RyanMoravick
Level 4
August 5, 2024
Solved

Failed Audience Activation to Facebook Destination

  • August 5, 2024
  • 1 reply
  • 1162 views

I am testing the Facebook destination connector in AEP and my audiences identity failed, giving an error message

 

"ACTSVC-8105-400 Bad request reported while pushing events to the destination. Please contact the administrator and try again."

 

Does anyone know why I might have received this error to begin with. The mapping stage for the activation is using email as the source field and the target field is hashed email using the Apple Transformation toggle.

 

Thanks!

 

 

This post is no longer active and is closed to new replies. Need help? Start a new post to ask your question.
Best answer by ccg1706
 
Some possible reasons for the error could be:
Incorrect Data Formatting:
-Email Hashing: When mapping email addresses for activation, AEP expects the data to be in a specific format. If you are using hashed emails, they should be hashed correctly using SHA-26, which is a common requirement for destinations like Facebook. If the email data isn't correctly hashed or the hashing isn't applied correctly, Facebook will reject the data. (Link to documentation)
- Apple Transformation Toggle: Double-check that the Apple Transformation toggle is correctly applied and that it's performing the expected SHA-256 hashing on the email address.
Data quality issues:
- Ensure that the data that you have is clean, meaning that the email addresses are properly formatted, free of duplicates, and not empty. A poor data quality can lead to issues during activation.
- Read more here
Destination Configuration:
- Incorrect target field mapping: Ensure that the target field in Facebook is set up to accept hashed emails and that the mapping aligns with Facebook's expected input format.
- Permissions and API Access: Verify that you AEP setup has the required permissions and API access to send data to
Facebook.
- For more info read here
Facebook destination issues:
- Temporary Service issues: It could happen, Facebook's API could be experiencing temporary issues, causing a "400 Bad Request" error. If everything seems correct on the AEP side, it will be worth it to try the activation again.
- For more detail you can read documentation here
 
To troubleshoot it and resolve the error you can try and perform de following steps:
Validate the Mapping configuration: Double- check that the email is properly hashed according to the destination's requirements. Specific instructions on configuring identity fields can be found here.
Review AEP logs and APIS responses: Use the AEP UI or API to inspect detailed logs for any error related to the activation. The logs might provide further insights about what went wrong. More information attached here.
 
Once performed all this steps, if the error persists contact Adobe Support for further assistance opening a ticket.
 
¡Hope this is helpful!
 
Regards, 
 
Celia 
 

1 reply

ccg1706
Community Advisor
ccg1706Community AdvisorAccepted solution
Community Advisor
August 9, 2024
 
Some possible reasons for the error could be:
Incorrect Data Formatting:
-Email Hashing: When mapping email addresses for activation, AEP expects the data to be in a specific format. If you are using hashed emails, they should be hashed correctly using SHA-26, which is a common requirement for destinations like Facebook. If the email data isn't correctly hashed or the hashing isn't applied correctly, Facebook will reject the data. (Link to documentation)
- Apple Transformation Toggle: Double-check that the Apple Transformation toggle is correctly applied and that it's performing the expected SHA-256 hashing on the email address.
Data quality issues:
- Ensure that the data that you have is clean, meaning that the email addresses are properly formatted, free of duplicates, and not empty. A poor data quality can lead to issues during activation.
- Read more here
Destination Configuration:
- Incorrect target field mapping: Ensure that the target field in Facebook is set up to accept hashed emails and that the mapping aligns with Facebook's expected input format.
- Permissions and API Access: Verify that you AEP setup has the required permissions and API access to send data to
Facebook.
- For more info read here
Facebook destination issues:
- Temporary Service issues: It could happen, Facebook's API could be experiencing temporary issues, causing a "400 Bad Request" error. If everything seems correct on the AEP side, it will be worth it to try the activation again.
- For more detail you can read documentation here
 
To troubleshoot it and resolve the error you can try and perform de following steps:
Validate the Mapping configuration: Double- check that the email is properly hashed according to the destination's requirements. Specific instructions on configuring identity fields can be found here.
Review AEP logs and APIS responses: Use the AEP UI or API to inspect detailed logs for any error related to the activation. The logs might provide further insights about what went wrong. More information attached here.
 
Once performed all this steps, if the error persists contact Adobe Support for further assistance opening a ticket.
 
¡Hope this is helpful!
 
Regards, 
 
Celia 
 
    RyanMoravick
    RyanMoravickAuthor
    Level 4
    August 12, 2024

    Hey @ccg1706 

     

    Thank you for the incredible response! I was able to test again and successfully activated to Facebook. The source of the issue was the audience segmentation. When I updated the audience with an event, or a change to the customer profile, the audience activated via the streaming segmentation evaluation.

      ccg1706
      Community Advisor
      ccg1706Community Advisor
      Community Advisor
      August 12, 2024

      Hi @ryanmoravick 

       

      Super! Thanks for sharing your insights about the issue. It helps me a lot to continue learning :).

       

      Regards,

      Celia

      Terms & ConditionsAccessibility statement

      Loading footer...