Aug 2024

DataChannel now supports the Flipkart Ads connector. The connector can be accessed from the ETL tab on the DataChannel Dashboard. Please follow the step-by-step Set up Guide for a smooth integration.

This Flipkart Ads connector will enable users to stream relevant Flipkart Ads account data into a pre-determined warehouse of their choice. Users will be able to start accessing their data by setting up a pipeline. Data acquired using such a pipeline will enable users to Momitor their ad campaigns in their Flipkart Ads account.

We have added a new type of node (AWS Lambda Function Node) for building orchestrations at DataChannel. The AWS Lambda Function node (when configured) offers an important advantage of automatically scheduling your predefined Lambda Functions.

For more details, click here

To adopt changes to the API, we have upgraded the Facebook Ads connector to version 20.

For more details, click here. Users can access the upgraded version from the ETL tab in the DataChannel Console.

To adopt changes to the API, we have updated the Google Ads Reverse connector.

For more details, click here. Users can access the upgraded version from the Reverse ETL tab in the DataChannel Console.

When pipeline runs were too long, they sometimes seemed to get stuck after a certain point, causing the run to error out. We have carried out bug fixes for such longer pipeline runs so that now whatever data that is fetched in the time pipeline ran is loaded to the destination.

For storage connectors, you can now compress files before uploading them to the destination folder. This will help to reduce storage costs and optimize data transfer.

For the Inventory Summaries pipeline, if you have multi-level JSON, we now support the ability to flatten the nested JSON to 2nd level. This will make analysis easier making it simpler to filter out whatever element you require.

We have now added support for SFTP Protocol in the FTP Connector.

In Amazon SP-API, the Service Level Agreement (SLA) for some reports require a cooling period. This implies that the complete report will be generated only after the close of the period. So, if you requested a report for a reporting period that was not yet available, the status for the report was marked as 'Partial Success'. However, from now on such reports will be marked as 'Success'.