Wiki

Description
AI Assistant

Get answers and guidance about TWM.

How do I connect to Binance?
What is a Data Series Window?
What are Drawing Tools?
Open AI Chat

DXFeed data + IB execution

The Main Idea

The most common workflow when using both DXFeed and Interactive Brokers together is:

  1. Market data comes from DXFeed — for charting, analysis, and strategy signals
  2. Trade execution goes through Interactive Brokers — orders are sent to your IB account


Example scenario: You open a chart with a DXFeed instrument (e.g., ES futures). You select your Interactive Brokers account for trading. When you place a trade, TWM needs to know which IB instrument corresponds to the DXFeed instrument on your chart. This is done through instrument mapping.

Why Mapping is Needed

The same financial instrument can have different internal symbols and contract specifications at DXFeed and Interactive Brokers. For example, the E-mini S&P 500 futures may be represented differently in each system.

Without mapping:

  1. TWM would not know which IB contract corresponds to your DXFeed chart instrument
  2. Orders could not be correctly routed to Interactive Brokers


Mapping tells TWM: "When I'm looking at this DXFeed instrument, send trades to this Interactive Brokers instrument."

How to Set Up Mapping

To map a DXFeed instrument to an Interactive Brokers instrument:

1. Open the Mapper in TWM.

Image

2. Select the Source Connection: choose DXFeed.

3. Select the DXFeed instrument you want to map (e.g., AAPL STOCK).

Image

4. Select the Target Connection: choose Interactive Brokers.

5. Select the corresponding IB instrument that matches the DXFeed instrument.

Image

6. Click Map to confirm the mapping.

Image


Verifying the Mapping

After saving the mapping:

  1. The mapped instrument should appear in the list of mapped instruments in the Mapper.
  2. Make sure both connections are active:
  3. DXFeed — Connected
  4. Interactive Brokers — Connected
  5. The expected result:
  6. Your chart receives data from DXFeed
  7. Your orders/trades are sent to your Interactive Brokers account


Testing the Setup

To verify everything works correctly:

  1. Open a chart with a mapped DXFeed instrument (e.g., ES).
  2. Select your Interactive Brokers account as the trading account.
  3. The chart should display DXFeed data in real time.
  4. When you place a trade, it should be routed to your Interactive Brokers account.


Try testing with both a stock and a futures instrument to confirm the mapping works across different instrument types.

ImageImage


Summary

After reading this section, you should understand:

  1. The primary workflow: DXFeed for data, Interactive Brokers for execution
  2. Why instrument mapping is necessary
  3. How to create a mapping in the TWM Mapper
  4. How to verify the mapping works
  5. That both connections must be active for the combined workflow to function


Previous
Interactive Brokers
Next
Market Data

Necessary cookies help make the website usable by enabling basic functions such as consent storage, security protection, language preferences, and authentication.

  • Necessary cookies

    UserUUID

    Technical identifier used to manage and persist cookie consent preferences.

    Maximum storage duration: 12 Months | Type: Necessary cookies
    consent

    Stores your cookie consent choices and selected preferences.

    Maximum storage duration: 12 Months | Type: Necessary cookies
    .AspNet.Consent

    Indicates whether the user has provided cookie consent.

    Maximum storage duration: 1 Year | Type: Necessary cookies
    .AspNetCore.Antiforgery

    Used to prevent CSRF attacks and protect form submissions and user data.

    Maximum storage duration: Session | Type: Necessary cookies
    .AspNetCore.Cookies

    Used to manage authentication information and signed-in sessions.

    Maximum storage duration: 1 Year | Type: Necessary cookies
    .AspNetCore.Culture

    Stores the user’s language and localization preferences.

    Maximum storage duration: 1 Year | Type: Necessary cookies

Functional cookies allow the website to remember preferences and support enhanced features or integrations such as Google services, maps, embedded media, or account-related personalization.

  • Functional Cookies

    LSOLH

    Used by Google to store session information and support service-related functionality.

    Maximum storage duration: Session | Type: Functional Cookies
    COMPASS

    Used by Google to remember settings and improve navigation across integrated services.

    Maximum storage duration: 6 Months | Type: Functional Cookies
    ACCOUNT_CHOOSER

    Remembers which Google accounts have been used on the device.

    Maximum storage duration: 1 Year | Type: Functional Cookies
    APISID

    Used by Google to store preferences and information when using integrated Google services such as Maps.

    Maximum storage duration: 2 Years | Type: Functional Cookies
    LSID

    Used by Google to store preferences while viewing pages that incorporate Google services.

    Maximum storage duration: 2 Years | Type: Functional Cookies
    SAPISID

    Used by Google services to support embedded content, maps, and account-related personalization.

    Maximum storage duration: 2 Years | Type: Functional Cookies
    __Host-GAPS

    Used by Google to support service preferences and related functionality on pages integrating Google services.

    Maximum storage duration: 2 Years | Type: Functional Cookies

Statistical cookies help us understand how visitors interact with the site, measure traffic, and improve services. Data is processed in aggregated or pseudonymized form by providers such as Google and Yandex.

  • Statistical Cookies

    _ga, _ga_*

    Google Analytics cookies used to distinguish users and sessions for traffic measurement and site usage analysis.

    Maximum storage duration: 2 Years | Type: Statistical Cookies
    _gid

    Google Analytics cookie used to distinguish users within a single day session.

    Maximum storage duration: 24 Hours | Type: Statistical Cookies
    _ym_uid

    Yandex Metrica unique visitor identifier used to distinguish users across sessions.

    Maximum storage duration: 1 Year | Type: Statistical Cookies
    _ym_d

    Yandex Metrica cookie that stores the date of the user's first visit.

    Maximum storage duration: 1 Year | Type: Statistical Cookies
    _ym_isad

    Yandex Metrica cookie used to detect whether the user has an ad blocker enabled.

    Maximum storage duration: 2 Days | Type: Statistical Cookies
    _ym_visorc

    Yandex Metrica Webvisor cookie used to record and replay user sessions for usability analysis.

    Maximum storage duration: 30 Minutes | Type: Statistical Cookies

Marketing cookies are used for advertising, campaign attribution, conversion tracking, personalization, and cross-platform measurement by providers such as Google, Microsoft, Meta, and TikTok.

  • Marketing Cookies

    AID

    Used by Google to link activity across devices and improve ad attribution.

    Maximum storage duration: 1 Year | Type: Marketing Cookies
    ANONCHK

    Used by Microsoft Advertising to validate and support ad-related requests.

    Maximum storage duration: 10 Minutes | Type: Marketing Cookies
    MUID

    Microsoft advertising identifier used to recognize browsers across Microsoft domains.

    Maximum storage duration: 13 Months | Type: Marketing Cookies
    __Secure-3PSID, __Secure-3PAPISID, __Secure-3PSIDTS, __Secure-3PSIDCC

    Google advertising and personalization cookies used to build preference profiles and support ad delivery.

    Maximum storage duration: 2 Years | Type: Marketing Cookies
    ADS_VISITOR_ID

    Used by Google to identify visitors for advertising and attribution purposes.

    Maximum storage duration: 2 Years | Type: Marketing Cookies
    OTZ

    Used by Google to support ad personalization and service optimization.

    Maximum storage duration: 1 Month | Type: Marketing Cookies
    __Secure-1PAPISID, __Secure-1PSID

    Google cookies used to support more relevant ads and account-related ad security.

    Maximum storage duration: 2 Years | Type: Marketing Cookies
    IDE, DSID, FLC

    DoubleClick / Google Ads cookies used for campaign attribution, ad delivery, and remarketing.

    Maximum storage duration: Varies by cookie | Type: Marketing Cookies
    datr, fr, sb, xs

    Meta / Facebook cookies used for browser recognition, security, ad measurement, and personalization across Meta services and partner sites.

    Maximum storage duration: Varies by cookie | Type: Marketing Cookies
    ttcsid

    TikTok identifier used for session-level event attribution, conversion tracking, and advertising measurement.

    Maximum storage duration: Varies by configuration | Type: Marketing Cookies
    ttcsid_D5GFV53C77U3VC0C2T50

    TikTok pixel-specific session cookie used for conversion attribution and advertising performance reporting.

    Maximum storage duration: Varies by configuration | Type: Marketing Cookies
    odin_tt

    TikTok cookie used for campaign attribution, browser recognition, and advertising performance measurement.

    Maximum storage duration: Varies by cookie | Type: Marketing Cookies
    tt_chain_token

    TikTok cookie used for event attribution and campaign linkage across sessions.

    Maximum storage duration: Varies by cookie | Type: Marketing Cookies
    ttwid

    TikTok browser identifier used for attribution, advertising measurement, and remarketing support.

    Maximum storage duration: Varies by cookie | Type: Marketing Cookies
    NID, UULE

    Google cookies that may support ad personalization, localization, and service preference handling depending on the integration and browser state.

    Maximum storage duration: Varies by cookie | Type: Marketing Cookies
    SEARCH_SAMESITE

    Google cookie used to support secure cookie handling across requests and service interactions.

    Maximum storage duration: 6 Months | Type: Marketing Cookies
About cookies and consent

This website uses cookies and similar technologies to ensure its proper functioning and, with your consent, to support functionality, measure usage, improve performance, and provide advertising, attribution, or personalized content. The legal basis for the use of necessary cookies is the legitimate interest of the data controller (Art. 6(1)(f) GDPR), while functional, statistical, and marketing cookies are used only upon your explicit consent (Art. 6(1)(a) GDPR).

Cookies are small text files stored on your device to make the website work efficiently and improve your experience. Some cookies are placed directly by us, while others may be set by third-party services integrated into our pages.

Cookie categories
  • Necessary cookies: enable core site functionality such as consent storage, language selection, authentication, and access to secure areas. These cannot be disabled.
  • Functional cookies: allow the website to remember settings and support integrations such as embedded or third-party services.
  • Statistical cookies: collect usage and performance data to help understand and improve the site.
  • Marketing cookies: support advertising, campaign attribution, personalization, and remarketing across providers and services.
Storage and consent management

Your cookie preferences are stored locally in a cookie named consent, valid for 12 months, and pseudonymously on our systems using a technical identifier (UserUUID), which does not allow direct identification of the user. You may change or withdraw your consent at any time via the cookie settings button visible at the bottom left of the site.

Third-party cookies

Some cookies are provided by third-party services such as Google, Microsoft, Meta, TikTok, and Yandex. These third parties may act as independent controllers for the data collected through their own technologies and services.

Your rights

You can withdraw or modify your consent at any time, delete cookies through your browser settings, and exercise your rights under Articles 15–22 GDPR (access, rectification, deletion, limitation, opposition, portability) by contacting us via the details provided in the Privacy Policy.

This Cookie Policy is aligned with Regulation (EU) 2016/679 (GDPR) and the ePrivacy Directive.

Privacy