Skip to main content
Understanding the Data Stored in Meltwater

Learn the details of historical social and editorial content data we store

Cheyenne V. avatar
Written by Cheyenne V.
Updated over 7 months ago

We have been in what was originally the "media monitoring" business since 2001, and as you can imagine, we have built up a huge library of content. Now two decades later, we are proud to offer our clients a strong content retention policy as an industry leader.

This article will cover:


History of Data

The history of data depends on the content type. Some types of content have such large volumes that we can only keep about a year’s worth of history. Currently, the date ranges available are as follows:

  • Social content: from the last rolling 15 months is available

  • Editorial content: from Jan 1, 2009 is available

This means that when you search for social content, you will be able to find content from the past 15 months, and with the news you can search for the content all the way back to 2009. This also applies to your dashboards and reports.

Note: YouTube Content - only pulls 30 days of data available retrospectively.


Retroactive Data

Some content types (X (formerly Twitter), Instagram, and YouTube) create 'subscriptions' when a search is saved. We begin to pull data for those searches when the search is saved.

For example, we don't go back and pull posts that match our search criteria from the prior 15 months. However, for most searches, there is likely to be some historic content since we index vast amounts of content from these providers to support our social sampling offerings and all of the other searches whose subscriptions are pulling additional content.

** Tagged documents, that fall outside our retention window, will be “read-only” - tags can not be updated on those documents


💡 Tip

Need more help? Feel free to reach out to us via Live Chat or check out our Customer Community.

Find answers and get help from Meltwater Support and Community Experts.

Learn more about how to customize these alerts via this article here.


Did this answer your question?