MarketFeeder Pro

Stunning Conditional Betting Technologies

Examples 46-50

Triggers search:


Example 46. I want to trade in markets with 8 or more runners. When a market has been in-running for 10 seconds I want to lay 4 GBP on the horse with the lowest odds that is priced between 7 and 10.
If later the odds of this horse drop by at least 10 ticks I want to back it for the same amount as lay, at the best price.
I want to keep doing this until my account balance increases to x pounds or until all the races are over.

Settings Configuration:

Max Attempts on Failure - set to "-1"
Allow triggers/booking/offset with In-Running Markets - turned ON

Trigger 1

Cell: "Any Selection Lay Price"
Condition: "is between"
Trigger Value: "6.8, 10.5"
Action: "lay"
Price: "lay_price"
Amount: "IF(AND('list of events'!B1<X, runner_number>=8, NOW()-event_off>=0.0001157), 4, 0)"
Market: "All Currently Monitored"
Selection: "First Matching Selection"
Active: "once in-play & wait"

Trigger 2

Cell: "Selection Matched Lay"
Condition: "is greater than"
Trigger Value: "0"
Action: "back"
Price: "best"
Amount: "IF(back_price < bm_1_layp - 10*p_tick, bm_1_laya, 0)"
Market: "All Currently Monitored"
Selection: "All Selections"
Active: "once in-play & wait"

The first trigger does the laying and the second one is a stop-loss trigger.
As you can see, in the first trigger there is one main condition that prevents laying before it's been at least 10 sec since the off.
The additional conditions in the Amount column limit the price range of the selection to between 7 and 10, and also make it compulsory that the number of runners in the race is >=8.

The second trigger will be executed only if the first trigger resulted in a matched bet. The condition in the Amount column calculates the stop-loss price limit.


Example 47. I need a trigger that will lay a selection, if and only if a selection has had a: 
- price leap of at least 30 ticks since last refresh.
- its price is <10
- there is at least 2K available in the back column  at a price of 1.5 or higher
- all of this in-play.

Set "Max Attempts on Failure" to "-1" and add the following trigger:

Cell: "Any Selection Price Leap"
Condition: "is equal or greater than"
Trigger Value: "30"
Action: "lay"
Price: "IF(AND(lay_price<10.0, back_price>=1.5, back_amount>=2000), lay_price, 0)"
Amount: specify the amount
Market: "All Currently Monitored"
Selection: "First Matching Selection"
Active: "once in-play & wait"


Example 48. I want to bet on the favourite priced <=2.0 to make a profit of 2 GBP each race, only in place markets. If the favourite loses I want to calculate the losses and bet to regain the lost amount on the next race.

Instructions and Settings Configuration:

Select place markets from the "Horse Racing - Todays Card" in the tree of events.
Set the following options:

- Max attempts on failure - set to "-1"
- Allow triggering/offset no sooner than ... min. before the event's start - set to "0.5"

There are two ways to accomplish this task. The first one is to wait until BetFair settles each race and get the results of the account statement to calculate the betting amount for the next race. This way works for all types of markets, but it has its flaws: if the next race starts earlier than the previous race is settled your triggers won't be able to make the correct calculations. If you wish to use this way, the additional options that have to be set are:

- Get Account Statement - turned ON
- Always show today's bets only - turned ON

The trigger is below:

Cell: "Winner Back Price"
Condition: "is equal or less than"
Trigger Value: "2.0"
Action: "back"
Price: "back_price"
Amount: "IF(VALUE('list of events'!K3)>=0, 2.0/(back_price-1), 'list of events'!M3/(back_price-1))"
Market: "All Currently Monitored"
Selection: "Winner"
Active: "once idle & wait"

The second way is to use the race outcome results that MF Pro obtains from an outer online source. It usually retrieves them much faster than BetFair so you get a chance to calculate the amount for the next race in time. This way only works for UK horse races and some of Greyhound races (which - you can read in the help file). If you want to try this way, your additional options are as follows:

- Obtain UK Horse Racing Outcome and/or Obtain Greyhound Racing Outcome - turned ON. You can turn on only that type of race you'll be really using in your trading sessions.
- Delete finished events automatically - turned OFF

Then the trigger should be set up as follows:

Cell: "Winner Back Price"
Condition: "is equal or less than"
Trigger Value: "2.0"
Action: "back"
Price: "back_price"
Amount: "IF(lrb_backpl>=0, 2.0/(back_price-1), -lrb_backpl/(back_price-1))"
Market: "All CUrrently Monitored"
Selection: "Winner"
Active: "once idle & wait"

You will notice a new trigger variable in the formula: lrb_backpl. It returns the result (profit or loss) of the last made back bet in the previous market (matched one naturally). Please note that only those markets are considered that were previously added in MarketFeeder Pro. So if you made some bets on the web site and did not add this market into MF Pro list, they will be ignored.
Also, there is another essential difference between the two ways: the first trigger sums up your consequent losses during the last several races. The second trigger only keeps the last lost amount.

This trigger works well on a chain of events added in the beginning of your trading session, for example on several UK horse races in a row.

Update!

Since a new field, "Total Won" has been added to the "List of events" sheet you can use it in this trigger example. If you want to take into account the overall losses for the day, and not only the latest losses, modify your formula in this way:
Amount: "IF(VALUE('list of events'!K4)>=0, 2.0/(back_price-1), -'list of events'!K4/(back_price-1))"


Example 49. I want MF Pro to first back then lay on the same selection securing equal profit. But after the back bet of 20 EUR is made and matched, all the unmatched portion should be cancelled and the lay bet's proportion should be calculated out of the remaining matched amount.
If after the backing the price has dropped I want to lay at 2 ticks lower than the back price. If it however raised I want to lay at the current available price, according to the proportion (to minimize my losses).
Here are the additional conditions for the bets:

-Total matched volume in the event greater than 200.000. 
- Total matched volume on the horse >=25.000. 
- Time before in-running >=1 minute
- Price between 4.0 and 9.0
- Back / lay ratio <=0.3.
- Difference between lay price and back price <=0.2
- Trend <=-0.2.  I believe this is b_growth <=-0.2
- Wait for leap of -2 (minus 2)
- back volume >=100.

Settings Configuration

Allow triggering/offset no sooner than ... min. before the event's start - turned ON and set to "1"
Max attempts on failure - set to "-1"

Trigger 1

Cell: "Any Selection Price Leap"
Condition: "is equal or less than"
Trigger Value: "-2"
Action: "back"
Price: "back_price"
Amount: "IF(AND(back_price>=4, back_price<=9, market_volume>200000, market_volume*volume/100>=25000, back_amount/lay_amount <=0.3, back_amount>=100, b_growth<=-0.2, lay_price - back_price<=0.2), 20, 0)"
Market: "All Currently Monitored"
Selection: "All Matching Selections"
Active: "once & wait"

Trigger 2

Cell: "Selection Matched Back"
Condition: "is greater than"
Trigger Value: "0"
Action: "cancel back then lay"
Price: "IF(lay_price<= bm_1_backp, bm_1_backp - 2*p_tick, lay_price)"
Amount: "IF(lay_price<= bm_1_backp, (bm_1_backp * bm_1_backa)/(bm_1_backp - 2*p_tick), (bm_1_backp * bm_1_backa)/lay_price)"
Market: "All Currently Monitored"
Selection: "All Selections"
Active: "once & wait"

You can see that the main condition of the first trigger limits selections in question to those which leaped down in at least 2 ticks. Always select the main condition that will cut own the most of the unsuitable selections.
All the rest conditions are being checked in the Amount column. The bet will be placed on the selections which satisfy all of those conditions.

The second trigger will be executed when any portion of the back bet from the first trigger is matched. The Action "cancel back then lay" will cancel all unmatched portion before calculating the new bet.
The "IF" functions in the Price and Amount columns return different formulas depending on how the price has changed. If it dropped, then the price of the lay bet will be calculated out of the matched back price (minus 2 ticks). However if it grew up, the price will be current lay odds.
The amount is being calculated equally: either the proportion

 


 

Example 50. I want to lay certain greyhounds of my own choosing to lose at Betfair, but I don't want to go over odds of, say, 10, and I'd be laying at flat stakes of £10.

If you want to leave MF Pro working on its own, select the Greyhound races you want to bet in in the beginning of your session, preferredly once in 5-10 sec to give it time to load markets into the spreadsheet. By the time you start to add markets your settings should be configured already.

Settings Configuration:

- Allow triggering/offset no sooner than ... min. before the event's start - turned ON and set to "5"
- Stop Monitoring Event when it turns In-Play - turned ON
- Constant Monitoring - turned ON and "Start at", "Finish at" time is set to cover the betting period (for example from 7 am to 9 pm)
- Start Monitoring Event at ... minutes before the beginning - turned ON and set to "5"
- Max Attempts on Failure - set to "-1"

Trigger

Cell: "1"
Condition: "is equal to"
Trigger Value: "1"
Action: "lay"
Price: "IF(AND(lay_price<=10, lay_price>0), best, 0)"
Amount: "10"
Market: select market from the drop-down list
Selection: choose selection
Active: "once each market"

As you can see the trigger condition is fake (1 will always be equal to 1). However the trigger won't be executed until it's 5 min to the beginning (because of the settings).
So around 5 min to each race MF Pro will lay on those selections that are priced less than 10 and will skip all the others.



  1. What is Triggered Betting
  2. Trigger Examples
  3. Quick Tips
MarketFeeder Pro is developed by WellDone Creative Software. ©2005-2008. All rights reserved. Terms and conditions.
SiteMap