The omniture S3 feed comes as a 1004 column TSV. And for fields that capture user inputs, they don’t escape backslashes. But the escape backslashes everywhere else. I filed a ticket on this over a year ago but still no fix.
We’re building a competitor to AEM (and in the process, parts of Omniture); would love to hear more about your gripes with that. (Email’s on my profile.)
One of the things we’ve seen is similar to some of the sentiments expressed about Blackboard: the decision makers often aren’t the users, so feature lists and meta issues tend to win out. Adobe seems to target that market pretty well with their whole experience suite.
Specifically: AEM, AAM, Omniture, among others. My favorite is AAM’s “only Adobe could come up with such a stupid data integration” file format: https://docs.adobe.com/content/help/en/audience-manager/user...
The omniture S3 feed comes as a 1004 column TSV. And for fields that capture user inputs, they don’t escape backslashes. But the escape backslashes everywhere else. I filed a ticket on this over a year ago but still no fix.