SAINT Import Invalid Classification Error - ways to troubleshoot | Community
Skip to main content
M
myhighnoon
Level 2
August 9, 2021
Solved

SAINT Import Invalid Classification Error - ways to troubleshoot

  • August 9, 2021
  • 2 replies
  • 1290 views

We are sending data to a client's Adobe Analytics Reporting Suite via POST API. The data includes the key that is associated to an eVar along with conversion classifications. The client has already ensured that the "Quote Output" box is unchecked so they can receive special characters. However, when sending data to the client they are receiving a SAINT import error of "Invalid classification - Conversion Classification Name". We've confirmed that the names of the conversion classifications that we are passing over match what they have in their setup. What else could be causing this error? Web service permissions? Could brackets in the data being sent over throwing out the errors (see example below)?

 

Example:

"conversion_classification_name" : [ ]

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 zxfdafgsdh

@myhighnoon In case you are still seeing the same error, I will recommend creating a ticket with ClientCare team and have this checked. 

2 replies

Brian_Johnson_
Brian_Johnson_
Level 8
August 9, 2021

@myhighnoon - Have you tried classifying a small list of items that you know do not have special characters of any sort? Assuming this is successful, it would rule out any issues outside of what's in the file (headers, permissions, etc).

M
myhighnoonAuthor
Level 2
August 11, 2021

@brian_johnson_ I am hoping to sync and troubleshoot in real-time with the client later today, and slim down the classifications to see what, if anything, it helps rule out. Should that not work, I may need to reach out to Customer Support like @zxfdafgsdh suggested. Thanks for the help!

    Z
    Adobe Employee
    zxfdafgsdhAdobe EmployeeAccepted solution
    Adobe Employee
    August 10, 2021

    @myhighnoon In case you are still seeing the same error, I will recommend creating a ticket with ClientCare team and have this checked. 

    Terms & ConditionsAccessibility statement

    Loading footer...