Content Types & Historical Data, Update Frequency in Community

Community supports the following platforms:

Facebook
Google Business
Instagram
LinkedIn (company pages only)
TikTok
YouTube
X (formerly Twitter)

Content types and historical data

The information about historical data applies only to the accounts that were added to the Emplifi platform as owned profiles (see Add a Profile as Owned (Private) or Public) and activated for Community (see Activate Profiles for Community and Set Up Profile Roles).

Not all content types that are available on the supported platforms are supported in Community. Unless specified otherwise, when a content type is not supported in Community, it can be accessed via the API of the platform.

For each supported platform, you can find for how long the data is accessible via the API of the platform and in the Community feeds.

Example: You can retrieve data from LinkedIn via its API for up to 4 weeks in the past, and Community stores up to 90 days of historical LinkedIn data. When a LinkedIn account is first added to the Emplifi platform as an owned profile, Emplifi downloads 4 weeks of historical data retrospectively. These 4 weeks of historical data will increase each day, for as long as the account is monitored, until the 90-day cap is reached.

Historical availability of ad data for all the supported platforms is two years from the moment when an account was added to the Emplifi platform.

This means that after you add an account to the Emplifi platform, you have two years of historical data available. After one year, you will see three years back.

Facebook

Content type	Supported in Community?	Historical data accessible via the Facebook API	Historical data available in the Community feeds
Direct messages	yes	lifetime^[1]	90 days
Wall posts	yes	lifetime^[1]	90 days
Mentions/tagged posts	yes	lifetime^[1]	90 days
Organic comments	yes	lifetime^[1]	90 days
Comments on photos, videos, albums	yes	lifetime^[1]	90 days
Standard ad comments (including comments under unpublished/dark posts), comments on boosted posts, remarketing ads, dynamic creative ads, placement asset customization ads, multi-language ads, and geo-location asset customized ads	yes	lifetime^[1]	90 days
Comments on posts inside of events	no	lifetime^[1]	n/a

^[1] The official Facebook documentation does not specify any time limit for historical data that the Facebook API can return. Therefore, you can retrieve all the data for this content type via the Facebook API.

Google Business

Content type	Supported in Community?	Historical data accessible via the Google Business API	Historical data available in the Community feeds
Reviews^[2]	yes	lifetime^[3]	90 days
Review comments	yes	lifetime^[3]	90 days

^[2] Except for attached images
The images attached to reviews are not downloaded to Community due to Google Business API limitations.

^[3] The official Google Business documentation does not specify any time limit for historical data that the Google Business API can return. Therefore, you can retrieve all the data for this content type via the Google Business API.

Instagram

Content type	Supported in Community?	Historical data accessible via the Instagram API	Historical data available in the Community feeds
Direct messages	yes	7 days	90 days
Comments	yes	4 weeks	90 days
Mentions	yes	6 days	90 days
Media tags	yes	7 days	90 days
Ad comments	yes	6 days	90 days

LinkedIn

Content type	Supported in Community?	Historical data accessible via the LinkedIn API	Historical data available in the Community feeds
Comments	yes	4 weeks	90 days
Direct messages	no	4 weeks	n/a
Ad comments	no	4 weeks	n/a
Mentions	no	n/a	n/a

TikTok

Content type	Supported in Community?	Historical data accessible via the TikTok API	Historical data available in the Community feeds
Comments and replies to comments	yes	lifetime^[4]	90 days
Mentions	no^[5]	n/a^[5]	n/a^[5]
Direct messages	no^[5]	n/a^[5]	n/a^[5]
Ad-related content (such as ad posts, comments, replies to comments)	no	lifetime^[4]	n/a

^[4] The official TikTok documentation does not specify any time limit for historical data that the TikTok API can return. Therefore, you can retrieve all the data for this content type via the TikTok API.

^[5] Mentions and direct messages are not supported in Community because on TikTok they are available only natively and cannot be accessed via the TikTok API. Therefore, Emplifi or any other third-party provider cannot provide this functionality.

YouTube

Content type	Supported in Community?	Historical data accessible via the YouTube API	Historical data available in the Community feeds
Comments on videos (including shorts) and channels	yes	lifetime^[6]	90 days
Community posts and comments	no^[7]	n/a^[7]	n/a^[7]
Mentions	no^[7]	n/a^[7]	n/a^[7]
Direct messages	no^[7]	n/a^[7]	n/a^[7]
Ad-related content (such as ad posts, comments, replies to comments)	no^[7]	n/a^[7]	n/a^[7]

^[6] The official YouTube documentation does not specify any time limit for historical data that the YouTube API can return. Therefore, you can retrieve all the data for this content type via the YouTube API.

^[7] Community posts and comments, mentions, direct messages, and ad-related content are not supported in Community because on YouTube they are available only natively and cannot be accessed via the YouTube API. Therefore, Emplifi or any other third-party provider cannot provide this functionality.

X (formerly Twitter)

Content type	Supported in Community?	Historical data accessible via the X API	Historical data available in the Community feeds
Direct messages	yes	2 weeks	90 days
Mentions	yes	2 weeks	90 days
Replies	yes	2 weeks	90 days
Reposts (formerly “retweets”)	yes^[8]	2 weeks	90 days
Reposts with comments (formerly “quote tweets”)	no	2 weeks	n/a

^[8] Only the reposts that are captured by listening queries

Frequency of updating the data in the Community feeds

The frequency of updating data is different for periods when you have Community open in your browser and when you do not.

Downloading content from various platforms is a complex process. Consider the information about the data update frequency an ideal case scenario when there are no issues such as missing tokens, rate limits, infrastructure issues, high loads on databases, or other disruptions.