> For the complete documentation index, see [llms.txt](https://betmatic.gitbook.io/documentation/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://betmatic.gitbook.io/documentation/website/overview-1.md).

# Tip Connect

Tip Connect links professional tipsters to your bot. Once a package is connected, every tip the tipster publishes is automatically turned into bets on your own bookmaker accounts — sized, filtered and targeted exactly the way you configure it. You never have to be at your screen when a tip drops.

> **Before you start**, make sure you have:
>
> 1. An **active Betmatic subscription**
> 2. The **bot installed and running** on your computer — see the [Quick Start Guide](/documentation/bot/quickstart.md)
> 3. **At least one bookmaker session switched on** — see [Bookmaker Sessions](/documentation/bookmaker-sessions/overview.md)
>
> Tips are placed by *your* bot on *your* accounts. Without a running bot and at least one running session, a connected package does nothing — tips arrive, but no bets are placed.

![The Tip Connect page](https://584636386-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fu7qJh7plmhQ54GXN76Sw%2Fuploads%2Fgit-blob-8e2c36700b700e5b29a76bff145e350eb26b04e7%2Ftip-connect.png?alt=media)

The page has a **Featured Tipster** banner at the top and three tabs:

| Tab                  | What it's for                                                                                                                             |
| -------------------- | ----------------------------------------------------------------------------------------------------------------------------------------- |
| **All Tip Packages** | Browse every available package and connect the ones you're subscribed to                                                                  |
| **Subscribed**       | Manage your connected packages and configure how their tips are bet — see [My Packages](/documentation/website/overview-1/my-packages.md) |
| **Simulation**       | Fire a test tip through your real preferences to see exactly which rows match and what bets would be placed — without risking money       |

***

## How a Tip Becomes Your Bets

Understanding this flow makes everything else in Tip Connect obvious:

1. **The tipster publishes a tip.** Every tip carries a race, a selection, the tipped odds, a bet type (CASH or BONUS), a bet market (e.g. Fixed Win) and a confidence rating in **units** — a standard tip is 1 unit, and a package's bankroll is treated as 100 units.
2. **A pre-alert may arrive first.** Some tipsters send an early heads-up shortly before their tips land. Betmatic uses it to start and log in your bookmaker sessions — the sessions at the bookmakers named across your preference rows (a row with no bookmaker restriction wakes all of them) — so when the real tip arrives your bets fire in seconds instead of waiting for logins. (You can opt out per preference row with **Ignore Pre Alert**.)
3. **The tip is matched against YOUR preference rows.** Each subscribed package has a list of preference rows — filters on venue location, bet type and bet market, each with its own bet settings. The tip is compared against every row.
4. **Each matching row becomes its own bet instruction.** Every **enabled** row whose filters match the tip creates a separate instruction with that row's staking, odds rules and targeting. Two matching rows means two sets of bets. If **no row matches, the tip is skipped entirely** — no bets are placed.
5. **Your bot places the bets.** The instruction is sent to your running bot(s), which place the bets on your bookmaker accounts — immediately, or held back if you've set Timing rules.
6. **Each session's own filters have the final say.** Before any bet goes on, the bot checks the receiving session's filters — the **Tipster Filter** (the package must be ticked for that session), plus the Bet Type, Bet Code and Bet Market filters. A bet that fails any of them is silently skipped for that session. See [Bot Settings](/documentation/bot/settings.md). Connecting a package automatically ticks it in the Tipster Filter of your **existing** sessions — but a session you add **later** starts with an empty filter list and silently drops that package's tips until you tick the package in its Tipster Filter.

> **Note:** Betmatic only ever bets with *your* settings. The tipster decides *what* to tip; you decide *if*, *how much*, *at which bookmakers* and *from which accounts* it gets bet.

### Safety rails

Several guards are built in so a connected package can never run away with your money:

* **New rows start disabled at $1** — a freshly added preference row does nothing until you configure and enable it ([My Packages](/documentation/website/overview-1/my-packages.md))
* **The package Enabled switch** is a master off-switch for the whole package ([My Packages](/documentation/website/overview-1/my-packages.md))
* **Per-row Maximum Odds** keeps a row off extreme longshots ([Package Settings](/documentation/website/overview-1/package-settings.md))
* **Per-session Max Stake and Min Stake** in the bot cap what any single account can put on a bet ([Bot Settings](/documentation/bot/settings.md))

***

## Connecting a Package

> **Important:** Tip subscriptions are sold by the tipsters themselves, on their own websites — you subscribe and pay the tipster directly. Betmatic's role is to verify that you have access to the package and connect its tips to your bot.

1. **Subscribe on the tipster's website.** Sign up and pay for the tips directly with the tipster. (The package detail dialog links to their site.)
2. **Press Connect on the package** in the All Tip Packages tab.
3. **Confirm the subscription.** How this works differs per package:
   * **Subscribe link** — the Connect button takes you to the tipster's site with your Betmatic account attached, and the tipster confirms the link on their end.
   * **Account verification** — a dialog asks for the email and password you use on the *tipster's* platform. Betmatic verifies your subscription with them and the package activates.
4. **Free packages** need no external subscription — press **GET FREE** and confirm in the dialog.

> **Security:** When you connect with tip-platform credentials, they are stored encrypted and used only to periodically verify that your subscription with the tipster is still active.

Once connected, the package shows **ACTIVE** and appears in the **Subscribed** tab.

***

## All Tip Packages

The list shows every available package:

| Column     | Description                                                                                                                                |
| ---------- | ------------------------------------------------------------------------------------------------------------------------------------------ |
| Tipster    | The tipster or service, with avatar — click to open the package detail dialog                                                              |
| Package    | The specific package name (a tipster can run several)                                                                                      |
| ROI        | Historical return on investment                                                                                                            |
| Following  | How many users follow the package                                                                                                          |
| Picks      | Number of picks published so far                                                                                                           |
| Tip Access | Your status (**ACTIVE**), or the button to get access: **CONNECT** or **GET FREE**. **CLOSED** means the package is not taking new members |

Use the **Order By** selector (Name / Picks) and the search box to find a package.

## Package Detail

Click a package name to open its detail dialog:

| Section           | What it shows                                         |
| ----------------- | ----------------------------------------------------- |
| About the tipster | Who the tipster is                                    |
| About the package | What the package covers                               |
| Tipster's website | Link to the tipster's own site — where you subscribe  |
| Performance       | An optional performance image supplied by the tipster |

***

## After Connecting

> **A freshly connected package places no bets.** The tipster's recommended preference rows are applied on connect, but they arrive **disabled** and carry a **$1** per-unit stake. Nothing is bet until you enable at least one row — and a row you enable without editing bets $1 × tip units. This is deliberate: connecting can never commit real money before you've reviewed the settings.

Two things to do straight away:

1. **Set up your preference rows** in the Subscribed tab — set your stake sizes and switch the rows you want on. The full walkthrough is in [My Packages](/documentation/website/overview-1/my-packages.md); every setting is documented in [Package Settings](/documentation/website/overview-1/package-settings.md).
2. **Run a Simulation.** Fire a test tip through your real preferences before real money is on the line — see below.

***

## Simulation

The **Simulation** tab fires a made-up tip through your real preference rows so you can see what would happen — without placing anything.

**Composing the test tip:** pick the package, the racing code and country, a venue and race from the real schedule, the market and selection (Same Race Multi syntax is supported), the tip's units (default 1), minimum odds (default 2), optional maximum odds, cash or bonus, and optionally the bookmakers the "tipster" names. Two switches apply to the run itself: **Supply Virtual Balance** (pretend every account is funded) and **Randomize bet result** (give the simulated bets random outcomes).

**What running it shows:** for each preference row that matched the tip, a per-bot breakdown of the bets that would be created — with the bet rows and the processing logs, so you can see exactly why each session was or wasn't used.

The simulation runs entirely on Betmatic's servers — your sessions do **not** need to be running.

> **Note:** treat the simulator as a matching and staking preview, not a delivery guarantee. It currently doesn't skip rows whose Enabled switch is off, and it only warns (rather than stops) when your package access has expired — so it can show bets that production would never place. The final word on live betting is your enabled rows plus each session's filters.

***

## Pre-Alerts in Practice

When a package you're connected to sends a pre-alert, here is what you see:

* Sessions at the bookmakers covered by your preference rows **start by themselves** — the toggle flips on and the bot begins logging in, exactly as if you had pressed Start.
* The bot application's **Log panel** shows the sessions starting and logging in in response to the signal.

To confirm pre-alerts are working, watch [Bookmaker Sessions](/documentation/bookmaker-sessions/overview.md) (or the bot's Accounts panel) around the tipster's usual publishing time — stopped sessions coming online on their own is the pre-alert doing its job. If you don't want a package waking sessions, enable **Ignore Pre Alert** on its preference rows ([Package Settings](/documentation/website/overview-1/package-settings.md)); see also [Going away?](/documentation/website/overview-1/my-packages.md) for what pre-alerts can and cannot override.