- 4 Minutes to read
- DarkLight
Release Note 2025-02
- 4 Minutes to read
- DarkLight
We’re excited to bring you the latest updates in our February release! This month, we continued with enhancing the platform's performance by introducing powerful new features, and addressing key connector fixes. We’ve also made several improvements to the user experience and UI, ensuring that managing your data integrations is easier and more efficient than ever.
Our goal is to keep you informed and provide the tools you need to drive success. Read on to explore all the details of the February 2025 release!
Connectors
New Connectors
- Airtable
- Apple Search Ads
- Jotform
- Microsoft Dataverse (destination)
- PayPal
- Polly
- Rossum (newly as a source)
- WordPress
New Datasets, Metrics and Attributes
- Facebook Graph: Facebook Reels dataset
- Jotform: Form and Submission datasets
- LinkedIn Ads: Pivots (
MEMBER_INDUSTRY
,MEMBER_COMPANY
,MEMBER_JOB_TITLE
) - Planday: Time and Cost of Shifts dataset
- RD Station Marketing: New datasets:
- Contact Associated Events
- Contact Funnels
- Conversion Asset Statistics
- Sales Funnel Statistics
- Reddit Ads: Reporting Date dataset
- Similarweb: Visits - All Traffic by Country dataset
- Stripe: Balance Transaction Fees dataset
- Tixly:
Prices
andTags
fields
Connector Updates
- Apple Search Ads: The API has been upgraded to v5. All clients using this connector have been automatically migrated, so no further action is required.
- Facebook: Facebook connectors have been updated to the latest API version.
- Instagram Media Insights:
- Starting April 21, 2025, the following fields will be deprecated:
plays
clips_replays_count
ig_reels_aggregated_all_plays_count
impressions
- video_views has already been deprecated as of this release.
- The ig_id field has been replaced with id.
- Starting April 21, 2025, the following fields will be deprecated:
- Pinterest Ads: It’s now possible to create a source and have it run on schedule even if no data is available yet. This is especially useful for cases where data collection starts at an unknown time.
- Salesforce Marketing Cloud: The date field is now correctly recognized as a date data type.
New Features
Advance Data Blending Capabilities
We’re excited to introduce a new SQL console to enhance data transformation when creating a data flow.
By clicking on Combine Sources in the top-right corner and selecting SQL Editor, you can now apply SQL queries to all your sources for advanced data transformations, beyond just simple joins.
Full Data Resync
With our new Full Data Resync feature, you can now load historical data all at once. Previously, users had to manually chunk data based on each connector's maximum load, which could be cumbersome.
As we carefully reviewed every single connector, the system is capable of automatically determining data load limitations and distributes requests efficiently to sync all available data.
Conditions for Use:
- Users must have write permissions (e.g., upsert write mode configured for some flows). The system will verify permissions before enabling the feature.
You can now also view full logs for all Full Data Resync jobs.
UX/UI Enhancements
Improved Dashboard
The dashboard and homepage have been enhanced to provide a clearer overview, including more detailed information on the number of flows, helping you stay on top of your data integrations.
Additionally, a new quick Send Email button has been added, allowing you to send an email directly to your Success Manager for immediate assistance.
Bug Fixes
Connector Fixes
Databox:
- Resolved an issue where data was not being written to the destination.
GoHighLevel:
- Location IDs were not being returned. This issue can likely be resolved on GoHighLevel’s side by approving locations.
Google & Display Video 360:
- Fixed an error where fields weren’t recognized due to mismatched data types between the source and the destination table.
Gusto:
- Previously, a broken source returned a
Template not found
error message, which was caused by a missing column key. The error message now provides a more specific description to help users troubleshoot.
HubSpot as a Destination:
- Fixed a write error caused by a missing
objectTypeId
field in the destination.
LinkedIn Ads:
- Creating a LinkedIn Ads source previously resulted in an error due to a missing facet. This has now been added.
LinkedIn Organic:
- Duplicate records in the
PageEngagementStatisticsTimeBound
dataset have been resolved. The issue was caused by multi-account extraction generating multiple requests without limits and offsets.
Microsoft Sharepoint:
- Creating a destination would fail when folder names contained spaces. This use case has now been handled. However, names with special characters (e.g.,
@
) are still not supported but may be in the future.
Podbean:
- Fixed an issue where the EPISODES and PODCASTS datasets returned no data. This was caused by Dataddo not recognizing the appropriate file type, which has now been resolved.
Salesforce:
- Fixed an issue where Salesforce as a source either failed to extract data or only extracted partial data.
- Resolved an issue where Action results were returning
null
. This was caused by pulling data from a range that started and ended at the same time.
Sellsy:
- Fixed an issue with the authorizer that caused the error:
Customer is invalid, the resource owner or authorization server denied the request
.
TikTok Ads:
- Fixed an issue where all records were assigned the
start_date
of 2025-01-01 when loading data from 2025-01-01 until yesterday. To ensure accuracy, please use thestat_time_day
field instead, asstart_date
reflects the beginning of the selected time range rather than individual record timestamps.
General Fixes
Advanced Settings:
- Fixed an issue where changes to advanced settings in connectors were not being saved. Updates are now reflected immediately.
Manual Data Load:
- Resolved a bug where the date range would sometimes not appear until the page was reloaded.
Source Status:
- Fixed a bug where changing the source status in advanced settings did not update the new status and error count correctly.