Trying to think about challenges with emails and one I ran into was finding out if an email was generated using Adobe Campaign Classic or Standard.  I thought I might be able to look at the email as HTML and find something to indicate it was generated by Classic or Standard.  Any thoughts?

Solved.  There is no way to ingest non-xdm compliant parquet.  I solved by making the parquet xdm compliant using a data pipeline, ensuring the datetime values are of a format AEP can ingest without errors, and sizing the data files to optimize load time.  Parquet file loads 60% faster compared to c...

I know this post is old, however, can you share the details of how you set up the mapping set to do this?  I have the same problem and would like to see how your approach works.

There must be a way to ingest data from a parquet file that is not XDM compliant.  It seems silly to ask a client to reformat / restructure data just for AEP to consume it.

Certainly no options in the UI.  Not clear where specifying non-xdm is to be done in the API.   Thoughts?

I did try this before.  Job runs and result is success, but no records loaded.  The Adobe docs lack clarity on configuring the mapping.  Do I still use the ATTRIBUTE and EXPRESSION sourceType?  Then source is the attribute name in the file and target is the fully qualified XDM path, like this? "mapp...

Let me try that in the API.

Does not help.  selecting a parquet file from S3 is fine.  No options to map in the UI workflow.

Does anyone have any example of ingesting a parquet file into AEP?  Documentation and Adobe Support says the parquet file must exactly match the XDM schema in AEP.  I am have a test file created to do just that.   However, there has to be a way to ingest a parquet file and use a mapping set.  I pref...

Has anyone created a source connection between Experience Platform and AWS using AWS PrivateLink (a VPC service)?  I know it is available in Commerce, but I wanted to know if there was a way to do the same with AEP.