Is there a single table showing supported file format type by ingestion method | Community
Skip to main content
Prithwiraj_Deb
Prithwiraj_Deb
Level 3
October 6, 2023
Solved

Is there a single table showing supported file format type by ingestion method

  • October 6, 2023
  • 1 reply
  • 572 views

I have looked at AEP document and videos in Experience League - documentation and Videos ... .

But these info are like of all over the places and some says in Beta.... 

for a stable phase - is there one single table that anyone can share for all supported types - (Json, Parquet, CSV, TSV, Blob etc. by Import and Export (Streaming, Batch and Edge) and also by source and destination type - like Cloud Storage, Adobe Applications (AAM, Analytics etc.), By Connection/Destination Type - (Web SDK, HTTP API, Source Connector, Edge Server API) 

    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 Tof_Jossic

    @prithwiraj_deb no single table with all you want I'm afraid, I think the documentation team went for something more specific for each connection you may be interested in, which probably makes more sense to avoid confusion.

     

    There may be more info coming from others but here are some initial details:

     

    For Batch .. all Cloud Storage connections are listed in https://experienceleague.adobe.com/docs/experience-platform/sources/home.html?lang=en#cloud-storage 

    if you click on them, there should be a snipper at the top of the page in the first couple of paragraphs listing all supported formats. Examples below: 

     

    - Amazon S3 - data can be formatted as XDM JSON, XDM Parquet, or delimited
    - Google Cloud Storage - data can be formatted as JSON or Parquet that is compliant with Experience Data Model (XDM), or in a delimited format.
    - SFTP - data can be formatted as XDM JSON, XDM Parquet, or delimited

     

    ________

    For Streaming which is mainly handled by HTTP API connections ... The HTTP API source supports the ingestion of JSON files
    See https://experienceleague.adobe.com/docs/experience-platform/sources/ui-tutorials/create/streaming/http.html?lang=en 

     

    ________
    Edge ingestion, I understand data is collected via the Adobe Experience Platform SDKs so that's done for you: https://experienceleague.adobe.com/docs/experience-platform/edge/home.html?lang=en

     

     

     

     

    1 reply

    Tof_Jossic
    Adobe Employee
    Tof_JossicAdobe EmployeeAccepted solution
    Adobe Employee
    October 6, 2023

    @prithwiraj_deb no single table with all you want I'm afraid, I think the documentation team went for something more specific for each connection you may be interested in, which probably makes more sense to avoid confusion.

     

    There may be more info coming from others but here are some initial details:

     

    For Batch .. all Cloud Storage connections are listed in https://experienceleague.adobe.com/docs/experience-platform/sources/home.html?lang=en#cloud-storage 

    if you click on them, there should be a snipper at the top of the page in the first couple of paragraphs listing all supported formats. Examples below: 

     

    - Amazon S3 - data can be formatted as XDM JSON, XDM Parquet, or delimited
    - Google Cloud Storage - data can be formatted as JSON or Parquet that is compliant with Experience Data Model (XDM), or in a delimited format.
    - SFTP - data can be formatted as XDM JSON, XDM Parquet, or delimited

     

    ________

    For Streaming which is mainly handled by HTTP API connections ... The HTTP API source supports the ingestion of JSON files
    See https://experienceleague.adobe.com/docs/experience-platform/sources/ui-tutorials/create/streaming/http.html?lang=en 

     

    ________
    Edge ingestion, I understand data is collected via the Adobe Experience Platform SDKs so that's done for you: https://experienceleague.adobe.com/docs/experience-platform/edge/home.html?lang=en

     

     

     

     

      Terms & ConditionsAccessibility statement

      Loading footer...