Skip to content
    Guide

    Inside the Partner Hub: A Tour of the BrokerIQ Self-Service Portal Your IBs and Affiliates Actually Use

    By TradeCore
    June 4, 2026
    Updated October 2, 2026
    8 min read

    The BrokerIQ Partner Hub is a fully white-label self-service portal where your IBs and affiliates complete eight everyday actions, from checking their commission balance to requesting a withdrawal, without filing a support ticket. BrokerIQ is TradeCore's modular CRM and back-office product line for FX/CFD brokers. Unlike a vendor-branded portal, the BrokerIQ Partner Hub runs on the broker's own logo, colors, and custom domain, so partners only ever see your brand, not the CRM vendor's.

    Every IB program produces a predictable pattern of tickets. The partner wants to know what their commission balance is. The partner wants a tracking link for a new Facebook campaign. The partner wants to know what each sub-partner earned this month. The partner wants to withdraw their accumulated commissions. The partner wants the network tree because a new sub-affiliate is asking who reports to whom. Multiply by however many active partners the broker has, and the ops team spends a non-trivial share of its week answering the same questions through email and Slack.

    The Partner Hub is the BrokerIQ-side answer to that pattern: a fully white-label self-service portal where partners do those eight actions themselves, without filing a ticket. This post is the tour. Every action below is something a partner can complete inside the Hub without involving your ops team, and every screen the partner sees is your brand on your custom domain.

    Illustrative overview of the eight self-service actions described in this tour. Abstract mockup, not a screenshot of the live BrokerIQ product.

    Illustrative overview of the eight self-service actions described in this tour. Abstract mockup, not a screenshot of the live BrokerIQ product.

    The argument before the tour: your brand, not someone else's

    Most forex CRMs in the category get the partner portal question wrong in one of two ways. Either they skip it entirely (the partner has no portal, every question becomes a ticket, the operating cost of the IB program scales linearly with partner count), or they ship a portal that is branded by the vendor (the partner logs into someone-else.com to check the commissions they earned by referring traders to your brokerage, which is a brand leak no broker should accept).

    The BrokerIQ Partner Hub is fully white-label. The broker's logo. The broker's color scheme. The broker's custom domain (for example, partners.yourbrokerage.com). The partner's first impression and every subsequent visit is your brand. The partner never sees the CRM vendor's name in the URL, in the header, in the footer, in the email notifications, or in the downloadable reports.

    That is the argument under the eight features below. Each one is a piece of operating depth. All eight together are the difference between a partner portal that runs the channel and a partner portal that asks the channel to wait for ops.

    1. The dashboard: the partner's headline numbers in real time

    The Hub opens on a single dashboard, the partner's landing view on every visit. It reads live from the same back office that runs the broker's CRM, so the numbers the partner sees and the numbers the broker's ops team sees are the same data, with no separate database and no delayed sync.

    The dashboard surfaces the partner's headline performance at a glance: total earnings, first-time-depositor (FTD) count, active clients, and trading volume. Deeper per-partner figures, including payout totals, live in the reports views covered later in this tour.

    Without this surface, every one of those numbers is a separate ticket to the broker's ops team. With it, the partner answers their own first question every time they log in.

    2. Browse every referred client with deposit and trade history

    The Hub shows the partner a list of every client they have referred, with the data they need to evaluate the network: deposit history per client, trade history per client, and account status. The partner can drill into any single client to see the full activity timeline that their commissions were calculated against. The view is read-only on the partner side (the partner does not see client contact details, only activity metrics), which preserves the broker's relationship with the client.

    Why this matters: a partner running an active acquisition channel needs to know which campaigns produced which deposits and which trading activity. A partner without this view either asks ops for a CSV every month or operates on faith. The Hub view replaces both patterns with a self-service surface.

    3. Commission history filterable by date, type, and status

    Every commission record the system has produced for the partner is in the Hub, filterable by date range, commission kind (trade, network, CPA, prop, adjustment), and status (pending, approved, on hold, rolled over, paid). The partner can export the filtered view as CSV or PDF for their own bookkeeping. Records reconcile against the broker's BrokerIQ commission ledger, so the numbers in the partner's export and the numbers in the broker's back office are the same.

    Note 1: a partner whose commission history is opaque generates ticket volume out of mistrust as much as out of curiosity. A partner whose commission history is visible and filterable trusts the broker. Trust is a retention metric.

    4. Create and manage their own tracking links, one per channel

    The Hub lets the partner create the tracking links they need, one per channel, each with its own 12-character hash identifier (the link slug), a code a client can type at signup, and its own attribution. A partner can compare a high-effort YouTube channel against a low-effort banner campaign link by link, all under the same partner record. Each link can target a live client, a demo client, or sub-partner recruitment.

    Each link reports its own funnel (clicks, unique clicks, registrations, first deposits and conversion rate) with geography, device and daily-click breakdowns, so the partner sees channel-level performance and the broker sees the same data on the back-office side. The partner creates and manages the links from the Hub; the deal that governs the partner decides what every referred client's trading earns.

    5. Follow the sub-partner network: every level earns its own keep

    For Main IBs running multi-level networks, the Hub provides the network view that most partner portals in the category skip, and it shows the network the way the IB Suite pays it: every level earns its own keep, recorded on its own ledger row.

    BrokerIQ's IB Suite runs unlimited partner levels on one deal model:

    • An absolute keep per level: one deal table sets what each partner level keeps on each instrument and account group, and the deepest deal assigned on the chain prices that whole branch. A Main IB's earnings on their sub-partners' clients arrive as network rows in their commission history, each carrying the calculation that produced it.
    • Self-management: a parent partner can fund a sub-partner, or a cashback carve for its own client, from its own keep, so a Main IB can invest in their own network while the brokerage's cost on the trade does not move.
    Illustrative concept of commission flowing through a multi-level partner network. Abstract mockup, not a screenshot of the live BrokerIQ product.

    Illustrative concept of commission flowing through a multi-level partner network. Abstract mockup, not a screenshot of the live BrokerIQ product.

    So a Main IB running two regional sub-partners who each run three sub-partners of their own sees every level's earnings in the Hub, and nobody negotiates a split partner by partner: the terms are set once, in the deal.

    6. Visualize the full network tree, every level rendered

    The Hub renders the partner's full sub-partner network as a visual tree. Every level. No depth cap. A Main IB with three sub-partners who each have six sub-partners of their own sees a tree with three top-level branches, six leaves under each, and each node's own earnings, clients and sub-partners. The view runs downward: a sub-partner sees only an upline's position on the tree, never its income, and a partner can hide their name from their downline.

    The visualization matters for the obvious reason (a Main IB cannot manage what they cannot see), and for a less obvious one: regional partner networks are often introduced to the broker as flat lists in a spreadsheet, and the tree view is the first time both the partner and the broker see the actual shape of the network they are running. That shape almost never matches the spreadsheet.

    7. Download marketing materials the broker has uploaded

    The broker uploads creative assets (banners, brochures, and other creatives) into the BrokerIQ back office. The Hub surfaces those assets to the partner with a simple download interface. The partner picks the asset, downloads it, and runs it.

    Without this surface, every new campaign request is an email exchange ("can you send me the latest brochure in Spanish?", "do you have a Facebook-sized banner for the new product?"). With it, the partner pulls what they need and runs.

    8. Request a withdrawal of accumulated commissions

    The Hub closes the loop with the action partners care about most: the withdrawal request. The partner sees their available balance (filtered through the partner qualification rules the broker has configured, so partners who do not yet meet the minimum FTD count or minimum deposit threshold see a clear status rather than a frustrating rejection on submit), submits a withdrawal request, and tracks the request through the approval workflow.

    Commission reaches that balance through the payment cycle. When a cycle closes, BrokerIQ decides each partner's payout on its own (ops approve it, hold it for review, roll it over into the next cycle, or post an adjustment) without touching any other partner's payout, and approved commission settles into the partner's own commission wallet. The withdrawal itself runs through the same rails as any other wallet on the platform, and the partner sees the status update in the Hub as the request moves through.

    The economics: every action above is a ticket your ops does not answer

    Each of the eight actions above is a ticket that, on a CRM without a self-service partner portal, the broker's operations team has to answer. The economics are linear: the more a partner can self-serve, the more partners a single ops headcount can support. A broker with a hundred active partners and a Hub that handles all eight actions runs the channel with materially less operations cost than a broker with a hundred active partners and a partner portal that handles three of the eight (or none of them).

    Check headline numbers

    In the Partner Hub (self-service)
    Earnings, FTD count, active clients and trading volume, live on the dashboard at every login
    Without a Hub
    A separate ticket to ops for each number

    Review referred clients

    In the Partner Hub (self-service)
    Read-only list with deposit and trade history; drill into any client's activity timeline
    Without a Hub
    Ask ops for a CSV every month, or operate on faith

    Reconcile commissions

    In the Partner Hub (self-service)
    Filter by date, type and status; export CSV or PDF
    Without a Hub
    Tickets raised out of mistrust and curiosity

    Create tracking links

    In the Partner Hub (self-service)
    Self-serve, one per channel, each with its own attribution and funnel
    Without a Hub
    Request a new link from ops for each campaign

    Manage the sub-IB network

    In the Partner Hub (self-service)
    Every level's own keep, arriving as network rows that show the calculation behind them
    Without a Hub
    Ask ops for a per-level breakdown every month

    See the network shape

    In the Partner Hub (self-service)
    Full visual tree, every level, drill into any node
    Without a Hub
    A ticket, or a flat spreadsheet that rarely matches reality

    Get marketing creatives

    In the Partner Hub (self-service)
    Self-serve download of the assets the broker uploaded
    Without a Hub
    An email exchange per asset

    Withdraw commissions

    In the Partner Hub (self-service)
    Submit and track a withdrawal request against the available balance
    Without a Hub
    A ticket to request the payout

    That linear capacity gain is the actual operating argument for a Partner Hub. The white-label branding is the brand argument. Both are real, and both are why the Hub is the surface most brokers ask about first when they evaluate the IB Suite.

    What is in the Hub that this tour did not cover

    The eight actions above are the most-used. The Hub also includes on-demand reports (eight report types across eight groupings, in CSV or PDF), per-tracking-link click funnels with geographic breakdown and device stats, and partner-side visibility into tier promotion or demotion (when the broker runs tier programs with promotion conditions, retention thresholds, and grace periods through the BrokerIQ tier engine). For the full eight-feature differentiator argument on the IB module beyond the Hub itself, see Eight IB-System Features Most Forex CRMs Do Not Have.

    How to evaluate a partner portal at a vendor meeting

    Three questions for any vendor demoing a partner portal:

    • Whose brand is on it? Open the portal in a browser. The logo, the color scheme, the URL, the footer, the email notifications, the downloadable reports. If any of them carry the CRM vendor's name, it is not white-label, regardless of how the vendor describes it.
    • What is the eight-action list? The eight actions above are the surface partners use day to day. Walk through each one in the demo. The vendor who handles all eight has a partner portal that runs the channel; the vendor who handles three of them has a partner portal that asks the channel to wait for ops.
    • How does it connect to the back office? The numbers a partner sees in the portal and the numbers ops sees in the back office should be the same data, in real time. A portal that runs against a separate database or a delayed sync is a portal that produces reconciliation tickets.

    See the Partner Hub against your own network

    The Hub is best judged against a real partner network, not a generic demo. Book a 20-minute walkthrough and we run the eight actions above against your own program shape: your tiers, your deals, your network structure, your withdrawal workflow.

    Book a demo at tradecore.com/contact, see the broader IB-module differentiator framework in Eight IB-System Features Most Forex CRMs Do Not Have, or check pricing.

    Frequently asked questions

    Yes. The Hub renders the broker's logo and color scheme across every screen, runs on the broker's custom domain (for example, partners.yourbrokerage.com), and the broker's name appears in URL, header, footer, email notifications, and downloadable reports. The CRM vendor's name is not visible to the partner.

    On TradeCore's Core plan a partner creates as many tracking links as they need, one per channel, each with its own slug, typeable signup code, attribution and funnel; on TradeCore's free plan every IB has one referral link. Each link uses a 12-character hash identifier and can target a live client, a demo client, or sub-partner recruitment.

    Yes. In BrokerIQ's IB Suite every partner level earns its own absolute keep from the governing deal, and self-management lets a parent partner fund a sub-partner, or a cashback carve for its own client, from its own keep. The brokerage's cost on the trade does not move, and the Hub shows every level's earnings on the network tree. It all runs on unlimited partner levels.

    Yes. Partners submit withdrawal requests against their available balance through the Hub. The request runs through the same rails as any other wallet on the platform. Upstream, when a payment cycle closes, ops decide each partner's payout on its own (approve, hold, roll over or adjust) without affecting any other partner's payout in the same cycle.

    The Hub reads from the same back office that runs the broker's CRM. Numbers the partner sees in the Hub and numbers ops sees in BrokerIQ are the same data, in real time. There is no separate database, no delayed sync, no reconciliation step.

    Yes. The same Hub serves IBs (trade-based commissions), affiliates (CPA on qualified clients), and hybrid partners (governed by both kinds of deal). The dashboard, client list, commission history, tracking links, marketing materials, and withdrawal requests work the same way across all three partner types.

    Related guides

    Tags

    marketing
    blog
    IB
    partner-hub
    partners
    self-service-portal
    flagship

    Ready to Get Started?

    Discover how TradeCore can help you build and scale your forex brokerage with our comprehensive CRM.

    We value your privacy

    We use cookies to enhance your experience. Read our Cookie Policy.