An update to the Default Schema (generated by Unify) has been released, which updates the objects around video metadata.

Previously some sources, when unified, were not standardized in their treatment of additional video metadata.

With this update, any field that was content.video_urls now uses content.videos[*].url. Instead of returning a list of urls, Unify will not return a list of objects with one of its properties being its url. This supports the additional metadata which may be attributed to each video present in the content.

The following data sources (and their related components) have been updated with this change.

  • brightdata_instagram_posts
  • brightdata_pinterest_posts
  • brightdata_reddit_posts
  • brightdata_youtube_posts
  • data365_facebook_hashtag
  • data365_facebook_keywords_latest
  • data365_facebook_keywords_top
  • data365_facebook_posts_search
  • data365_facebook_profile
  • data365_instagram_hashtag
  • data365_instagram_location
  • data365_instagram_profile
  • data365_instagram_profile_posts_feed
  • data365_linkedin_company
  • data365_linkedin_keywords
  • data365_linkedin_member
  • data365_tiktok_hashtag
  • data365_tiktok_keywords
  • data365_tiktok_music
  • data365_tiktok_profile
  • vetric_facebook_discover_posts
  • vetric_facebook_profile_feed
  • vetric_instagram_user_feed
  • vetric_instagram_user_reels
  • vetric_tiktok_discover_posts
  • vetric_tiktok_user_feed
  • vetric_x_search_latest

An update was released for Vetric components with enhanced Job recovery logic. This update improves the handling of high volumes of concurrent requests and reduces the failures of work items within Jobs using Vetric sources.

All Vetric components automatically updated to use the improved logic, and no user action is required.

You can now view and filter your cost and usage according to Billing Tags.

Billing Tags is a new flag that can be added to Tags, which are optional metadata tagging that can be added to any Job. By adding billing tags to your pipeline jobs, you can track costs at a more granular level, such as by department, project, client, or environment.

This feature enables precise cost management and helps you understand exactly the costs and usage at a detailed level within CSV exports of billing information and within the Platform's billing views.

Access the documentation on Billing Tags and detailed cost/usage reporting.

A update was released to solve some cases where the thumbnail images for video content appeared in video URLs instead of as images. A separate thumbnail field has been added to the unified schema.

The metadata field of "video_urls", will not correctly appear within the parent "content" hierarchy.

This field which contain the URLs to any videos associated with the content, was outside of the parent "content" hierarchy on selectVetric sources.


Updates have been released to the collation capabilities within both the Profile Fetcher and File Fetcher from WebSightLine. The collation and combination of messages and of files are clearly distinguished and simplified to prevent confusion in the user experience.

Exorde Labs has now partnered with Datastreamer to make available their data sources in streaming or search API ingress methods. With over 2.5 billion social media posts collected each month, their coverage of many sources is a powerful addition.

The Exorde data components are able to use as integrated sources in pipelines now.

You can now consume messages into your Pipelines, running on Datastreamer, using Kafka. This new component leverages the full infrastructure power of Datastreamer to consume high-volume social and web feeds.

Screenshot of the Kafka ingress component configuration.


The new Portal homepage brings together key information from across billing, pipelines, jobs, and logging into a central view. You can see this new Portal homepage when you login to your account.

A number of fixes and improvements have been released in the last few days, including:

  • A compatibility fix with the Bright Data ingress components increases their performance and error handling.
  • Profile Fetcher has received improvements in it's ability to handle large files and extended requests.
  • Data365 ingress components have additional compatibility supports to handle long-running Jobs and high concurrent volumes that may have otherwise exceeded rate limits.