Pairing, and your first upload

What the pairing code is, why it is shown once, and what has to happen before a session appears.

What pairing is

The pairing code ties a connector to your account. You generate it on Set up your recording, paste it into the connector once, and the connector keeps it as its credential from then on: every upload it makes carries it, for as long as the pairing stands. You never type it again.

It is shown once, on purpose, and it stays valid until it is revoked, so keep it private: anyone holding it could send uploads under your account from their own machine. Pasting it into your own connector does not use it up. There is no button yet that revokes one pairing on its own. Ask in a ticket, and say so if a code got out; that is handled by hand today. Or, in Settings, delete all your trading data or your account, which revoke it as well, with every other pairing, and delete the data too.

If you lost it before pairing, generate another. Generating a new one costs nothing and does not cancel the old one.

The code was not accepted

The connector says "That pairing code was not accepted. Generate a fresh one in your dashboard and try again." when the code it was given matches none this account issued: a code copied with a character missing, or one that was revoked. Generate another on Set up your recording and paste it whole.

When the first session appears

The connector looks at its folder every fifteen seconds and sends what is new. Checking more often would change nothing: Bookmap rewrites its export roughly once or twice a minute, and that is the limit, so the setting is best left alone. The first file exists once you close a trade with the addon ticked, and the dashboard fills as soon as that upload lands. Nothing appears while a position is still open. You do not need the dashboard or a browser open while you trade: only Bookmap and the connector have to be running.

Two computers, or a new one

Each machine you trade from runs its own connector with its own pairing code, and every one of them stays paired: sessions from all of them arrive under your account. A machine you stop using keeps its pairing; there is no button yet that revokes one pairing on its own, so tell us in a ticket which machine you keep, and it is handled by hand today.

What it works with

Bookmap, and only Bookmap. Any broker or data feed you connect through Bookmap works, because the connector and the addon read Bookmap and nothing else on your machine.

What has to be true before anything appears

A session reaches the dashboard only when all of these are true, and they fail independently:

• The connector is running on the machine you traded on.
• Something recorded the trade: the addon, ticked in Bookmap on the instrument you actually traded, or Bookmap's own export.
• Bookmap was open while you traded, and the trade is closed. Open positions are not sessions.
• You traded a futures contract. Stocks are acknowledged and never stored.

The addon writes your closed trades only for instruments where its box is ticked. On an instrument it is not ticked on, the trades reach the dashboard only if Bookmap's own export records them, and then with no order or market readings; otherwise they never arrive, and no total, rule or alert covers them. Nothing warns you either way. That is the single most common reason a first upload never arrives: the addon is installed, and ticked on one instrument while the trading happened on another.

An untick does not always look like an empty day, which is what makes it hard to spot. Depending on what else your Bookmap is set up to write, that day can also arrive with the trades in it and nothing of the market around them, which reads as a day the coach has much less to say about than usual. The fix is the same either way: tick the box on that instrument.

Checking that pairing worked

Open the connector's own window. When it is paired and running it says All set. If it says anything else, the words it prints are the answer, so copy them out.

The connector also writes a log next to itself, in the folder you installed it in.

ai-norden-connector.log

The end of that file is what tells us the difference between not paired, paired but nothing to send, and sending and being refused. Pasting the last part of it into a ticket usually skips a whole exchange.

If it paired and the dashboard is still empty

That is a different problem, and it has its own article: the dashboard is empty though the connector says paired.