Refinitiv Eikon Connector

Financial Data & Messaging | Connector for Refinitiv Eikon

What Is the Shield Connector for Refinitiv Eikon / Thomson Reuters?

Refinitiv Eikon is now part of the LSEG (London Stock Exchange Group) data and analytics platform. It is one of the most widely used financial data terminals in global markets, providing traders, analysts, and portfolio managers with real-time market data, news, analytics, and integrated messaging.

Eikon Messenger, the communications component embedded within the Eikon terminal, is used daily across thousands of financial institutions to conduct real-time conversations between market participants covering price negotiation, order coordination, market colour, and counterparty communication in the same environment as the data and analytics that inform those decisions.

Shield’s connector for Refinitiv Eikon ingests Eikon Messenger messages and associated metadata directly into Shield’s compliance platform, preserving the full fidelity of every conversation, participant event, file attachment, and metadata field. From the moment data enters Shield, it is available for AI-powered surveillance, investigation, regulatory archiving, and eDiscovery, all within a single unified platform.

Eikon Messenger data does not exist in isolation. Traders and analysts using Eikon are communicating about the same positions, orders, and market events they are monitoring on the terminal — making the messaging component one of the highest-context, highest-risk communication channels in a firm’s eComms portfolio. Shield understands the financial context of Eikon Messenger conversations, enabling compliance teams to detect genuine risk rather than chasing false positives.

Why Refinitiv Eikon Compliance Is Complex

Refinitiv Eikon Messenger is not a straightforward channel for capturing or surveilling. Several specific challenges arise consistently across regulated firms:

• Terminal-integrated messaging context. Eikon Messenger sits within the same environment as live market data, news feeds, and analytics — meaning conversations are frequently driven by, and make direct reference to, real-time market events visible on the terminal. Surveillance systems that treat Eikon messages as standalone text, without the market context in which they were generated, miss the signals that make those messages compliance-relevant.
• Metadata completeness. Eikon Messenger generates metadata alongside message content — including sender and recipient identifiers, timestamps, conversation thread identifiers, and participant data — that is essential for audit trail integrity and regulatory examination responses. Many archiving solutions strip or misformat this metadata during ingestion, resulting in incomplete records for investigation and eDiscovery.
• Platform transition complexity. The Refinitiv brand and underlying platform have undergone significant changes — from Thomson Reuters to Refinitiv following the Blackstone acquisition, and subsequently to LSEG following the 2021 acquisition. Firms that have operated Eikon across multiple years may hold data generated under different platform iterations, requiring a compliance solution capable of handling the full data history consistently.
• Cross-channel communication patterns. Eikon Messenger conversations rarely represent the complete picture of a business interaction. Negotiations that begin on Eikon frequently continue on Bloomberg IB, Symphony, email, or voice. Siloing Eikon data away from other channels makes cross-channel investigation slow, error-prone, and structurally incomplete.

Key Features of the Shield Refinitiv Eikon Connector

Complete Message Capture. Shield captures all Eikon Messenger communication types — one-to-one conversations and group messaging — including full message content, file attachments, and every metadata field generated by the platform. All data is ingested in full, with zero data loss.

Full Metadata Preservation. Shield retains and enriches the complete Eikon Messenger metadata layer, including sender and recipient identifiers, conversation thread identifiers, timestamps, message IDs, and participant data. This metadata is preserved in its original form, made fully searchable, and stored as part of the immutable compliance record — ensuring that investigations, regulatory examination responses, and eDiscovery productions are accurate and legally defensible.

Immutable, Audit-Ready Archive. All Eikon Messenger data captured by Shield is stored in a tamper-evident, WORM-compliant archive with a complete audit trail of every access and action taken on the record. Data is indexed for rapid search and retrieval, supporting regulatory examination responses, eDiscovery requests, and internal investigations.

Out-of-the-Box AI Surveillance Models. Shield ships with pre-configured AI surveillance models for Eikon Messenger, targeting behaviours including market manipulation, information leakage, MNPI sharing, front-running, and personal misconduct — all calibrated to the specific language patterns of terminal-based financial messaging. Models can be customised to reflect a firm’s specific risk appetite, restricted lists, and internal policy requirements.

Unified Cross-Channel Surveillance. Eikon Messenger does not exist in isolation. The same traders and analysts communicating over Eikon are also using Bloomberg IB, email, Symphony, and other channels — often about the same positions, orders, and market events. Shield ingests Eikon data into the same unified compliance platform as every other channel, enabling compliance teams to correlate Eikon Messenger activity with communications from all other sources. This cross-channel context is essential for accurate misconduct detection and complete trade reconstruction.

Data Governance and Chain of Custody. Shield’s Eikon connector preserves a complete, verifiable chain of custody from capture through archiving and retrieval. Every stage of data handling is logged, auditable, and reportable — giving compliance officers and legal teams the confidence that Eikon Messenger records are admissible, complete, and unaltered throughout their lifecycle.

Regulatory Coverage

Refinitiv Eikon Messenger communications are classified as business records subject to capture, retention, and surveillance requirements across multiple regulatory frameworks. The Shield Refinitiv Eikon connector supports compliance with:

• SEC Rules 17a-3 and 17a-4 — requiring broker-dealers to capture, preserve, and produce records of all communications related to their business, stored in WORM-compliant format for a minimum of six years
• FINRA Rules 4511 and 3110 — requiring member firms to archive all communications relating to their “business as such,” including instant messages and chat, with supervision and audit trail requirements
• MiFID II — requiring investment firms to record and retain electronic communications related to orders and transactions for a minimum of five years, with three-day trade reconstruction capability
• Market Abuse Regulation (MAR) — requiring firms to monitor communications for potential insider trading and market manipulation
• Dodd-Frank Act — requiring swap dealers and major swap participants to retain communications related to swap transactions
• GDPR and data privacy regulations — Shield’s architecture supports data residency requirements and privacy-compliant data handling across jurisdictions

Related Connectors

Shield’s connector portfolio spans the full range of eComms channels and trading platforms used across regulated financial institutions. All connectors feed into a single unified compliance platform — so Eikon Messenger data is always reviewed in the context of every other channel your traders and analysts use.

• Bloomberg IB and Bloomberg Mail
• Microsoft Teams
• Microsoft Exchange
• FX Connect
• ICE Chat
• Symphony
• WhatsApp Business
• Zoom
• Voice and Turret
• WeChat
• Mobile (SMS/MMS)
• Gmail

Frequently Asked Questions

How does Shield handle the financial language and market context of Eikon Messenger conversations?

Shield’s surveillance engine applies NLP models specifically trained on financial services language — including the market terminology, instrument references, and informal negotiation language typical of terminal-based messaging between traders and counterparties. This contextual understanding reduces false positive alerts and ensures that genuine risk signals are identified accurately, even when expressed in the abbreviated or jargon-heavy language common to Eikon Messenger conversations.

Does the connector cover data generated under previous Thomson Reuters and Refinitiv platform iterations?

Yes. Shield’s connector is designed to handle the full data history of the Eikon platform across its various ownership and branding iterations — from Thomson Reuters Eikon through Refinitiv to the current LSEG environment. Firms that have operated the platform across multiple years can ingest historical data into the unified compliance archive alongside current communications, ensuring consistent coverage across the complete retention window.

Can Eikon Messenger data be reviewed alongside other communication channels during an investigation?

Yes, and this is increasingly important. Misconduct rarely stays on a single channel — a conversation may begin on Eikon Messenger, continue on Bloomberg IB, and conclude over email or voice. Shield’s unified archive allows reviewers to search and reconstruct events across all channels in a single workflow, ensuring the full picture of a business interaction is available regardless of which platforms were used.

How should firms handle data residency and cross-border privacy requirements for Eikon Messenger communications?

Eikon Messenger data captured for compliance purposes is subject to the same data residency and privacy obligations as any other business record. Firms operating across multiple jurisdictions — particularly the EU, UK, and APAC — need to ensure their archiving infrastructure supports region-specific storage requirements and is consistent with GDPR and equivalent frameworks. Shield’s cloud-native architecture supports configurable data residency controls, enabling firms to meet jurisdiction-specific requirements without compromising on surveillance or retrieval capability.