Community

Product DocsMenu

Twitter v2 Connector

CES 7.0.8388+ (June 2016)

Twitter is an online social networking service that enables users to post and read short messages called "Tweets". Registered users can post and read Tweets; unregistered users can only read them. The second generation (v2) of the Coveo connector for Twitter allows Coveo administrators to index and integrate the Twitter content of their managed users into a Coveo unified index. The connector indexes specific content from all managed users, so that any user can easily find the Twitter content he has access rights to through any Coveo search interface.

The content of this section is also available in PDF format for download:
Twitter v2 Connector Guide

Features

The Twitter v2 connector features:

Content indexing

Extraction and indexing of the following Twitter item types:

  • Users

  • Usernames and names

  • Protected users (see Limitations)

  • Tweets (normal, mention, reply, retweets, quote)

  • Hashtags (#) and cashtags ($)

  • Symbols

  • Timelines (user, home, mentions, lists, collections)

  • Lists

  • Collections

Incremental refresh

Supports incremental refresh to periodically query Twitter for the latest Tweets, newly followed users and newly listed members, keeping index content up-to-date.

Note: Some changes need a full refresh or a source rebuild to be taken into account (see Limitations).

Multi-threading

Can run multiple threads, which can improve performances considerably (see Configuring and Indexing a Twitter v2 Source).

Pause/Resume

When indexing Twitter content, connector tasks can be paused and resumed.

Limitations

  • The connector does not support permissions. Permissions need to be defined manually.

  • A Twitter API limitation prevents the connector from supporting user mappings.

  • During an incremental refresh, deleted items cannot be detected and require a full refresh or rebuild to be updated or removed.

  • Incremental refresh cannot be performed if the last rebuild or refresh did not end normally, i.e., the source was stopped, paused, or an exception occurred.

  • Direct messages are not indexed.

  • Tweets belonging to protected users (protected Tweets) cannot be retrieved from a search query.

    Note: Protected Tweets can only be retrieved from a user timeline if the authenticated user is an approved follower of the protected user.

What's Next?

Review the steps to deploy the Twitter v2 connector (see Twitter v2 Connector Deployment Overview).

People who viewed this topic also viewed