Team history: how to use pre-match data in the bot

Team history is the set of numbers both teams bring from their previous matches: how often there was a goal in the first half, the average number of corners, the corners between the 37th and the 45th minute. They are known before kick-off, so they work both for Before the match bots and for tightening up a During the match bot.

In this guide you'll see where they are in the builder, how to read them and how to choose the team and the matches that count.

Where they are

In step 3 (Conditions), open Stats and click Choose stat. In the catalogue, pick the Team history tab: in During the match bots it is the middle one, and in Before the match bots it is the first, because the live stats don't appear. On the left is the list of categories, one per line, with the topic and the type of data: Goals · Site predictions (%), Goals · Averages, Goals · By period of the match, Goals · Others, and the same for Corners and Cards. Click one and its stats appear on the right.

These are the types of data:

• Site predictions (%): in what percentage of matches something happened, for example Prediction Over 0.5HT goals %.
• Averages: the average value per match, for, against or in total.
• By period of the match: the same data split by minutes.
• Others, for goals, and Races, for corners: the remaining stats and the races (which team reaches a number of corners first).

If you already know what you're looking for, type it in Search everything (for example "over" or "corners").

How to read a percentage

If a team has 90% in Prediction Over 0.5HT goals %, it means that in 90% of the matches counted there was at least 1 goal in the first half. It doesn't mean that team scored it: the match had the goal, at one end or the other.

When the name says For or Scored, the meaning changes: it only counts what the team itself did. Against counts what the opponent did to it.

By period of the match: a grid

In the By period of the match categories there isn't a list of similar names. There's a grid: you choose the period in the column and what to count in the row, and click the + in that cell. The condition is created straight away, ready for you to set the value.

• Goals: columns 0-15, 16-30, 31-45, 46-60, 61-75 and 76-90; rows Scored, Against and Total.
• Corners: columns from 0-10 to 87-90 (including 37-45, 75-90 and 80-90; the last ones come into view when you scroll the grid to the right); rows In %, For, Against and Total.

For example, for a corners bot at the end of the first half, column 37-45 with the For row tells you how many corners the team usually wins in that period.

Whose number

The condition card has three fields in a row: whose number it is, how it counts (minimum of, more than, maximum of, exactly or between) and the value. The fields have no labels; you recognise them by the option they show. In the first one, you choose which team it applies to:

• Average of both teams: it's enough for the average of the two to reach the value.
• At least one team: it's enough for one of the two to meet it.
• Both teams: both have to meet it.
• Home team or Away team: only that team counts.
• Team with odds…: only the team with the odds you choose counts.
• The competition: the figure for the whole league, not for the teams. It only appears for the stats that have it.

With Team with odds…, a line starting with The team with appears, where you choose who counts as the favourite: Strong favourite (odds up to 1.50), Favourite (odds up to 1.80), Slight favourite (odds up to 2.20), Underdog (odds 2.50 or more) or Other odds, where you type the range yourself.

Which matches count

On the condition card there's a discreet line: Counting the last 10 matches, home / away · change. That's the default, and for most bots it's enough. If you click change, the Counting line opens with the choices:

• how many matches: the last 6, 8, 10 or 15;
• which matches: home / away (the home team's home matches and the away team's away matches) or home and away (all);
• the only in this competition box: only matches from the competition of the match in question count, without cups or other competitions;
• the minimum number of matches, which appears when you move away from the default: it's the number of matches the team must have for the condition to count.

Few matches give numbers that change a lot from week to week. If you drop to 6, remember that a single match already carries a lot of weight.

Example: favourites with a first-half goal

• Stat: Prediction Over 0.5HT goals %, in the Goals · Site predictions (%) category.
• Whose number: Team with odds…; in The team with, Slight favourite (odds up to 2.20).
• Value: minimum of 75.

Finally, click Add criterion. Below the fields, the card spells out the condition in full so you can check it: minimum of 75% of the team with odds up to 2.20.

The bot only alerts when the match has a team with odds up to 2.20 and that team has at least 75% in this prediction. Each stat you add counts as 1 of the 3 conditions the bot needs.

If you want to see a bot like this already built, the Quick setup in step 1 has the Goals, before the match example: three team-history stats and a daily list. It's a starting point, not a tested strategy.

Goals, corners and cards are read the same way

The logic is the same in all three categories: percentages, averages, for and against, and the periods of the match. Once you understand it for goals, you apply the same reading to corners and cards.

If you're unsure about a number, open the match analysis: the team-history stats are the same ones shown there, in the Goals, Corners and Cards tabs.