Recent Posts

21

Triggered betting / Improvements to the Excel add-in

« Last post by davidgilbertson on 25 Jun 2026, 06:02 »

I would like to see a couple of improvements to the Excel add-in. 

If you try to lay from Excel some, but not all, of the runners in the race, the trigger will not execute at all. An interim solution that I use is to have a placeholder bet on the runners that I don't actually want to bet on. So they get bets at $1.02 on 0.01% of the bankroll, with the bets cancelled at in-play. Those bets never get on.

It would be better to be able to lay on only some, but not all, of the runners in a race.

The other improvement I would like to see is to add two columns to a spreadsheet, eg for both back and lay triggers. I have found that trying to add a second column doesn't work. The numbers get put all over the place.

22

General discussion / Improvements to Excel add-in

« Last post by davidgilbertson on 25 Jun 2026, 06:00 »

I would like to see a couple of improvements to the Excel add-in. 

If you try to lay from Excel some, but not all, of the runners in the race, the trigger will not execute at all. An interim solution that I use is to have a placeholder bet on the runners that I don't actually want to bet on. So they get bets at $1.02 on 0.01% of the bankroll, with the bets cancelled at in-play. Those bets never get on.

It would be better to be able to lay on only some, but not all, of the runners in a race.

The other improvement I would like to see is to add two columns to a spreadsheet, eg for both back and lay triggers. I have found that trying to add a second column doesn't work. The numbers get put all over the place.

23

General discussion / Re: Built a lay signal service with a CSV feed for MFP — fellow users might find it

« Last post by DanT on 16 Jun 2026, 11:01 »

here is today CSV if it helps

race_time_utc,race_time_uk,region,course,runner,market_id,selection_id,signal_price,placed_price,tier,stake_points,status,skip_reason
"2026-06-15 23:53:00","2026-06-16 00:53",USA,"LOUISIANA DOWNS","Hurry Up Hannah",1.259163528,53998919,,,WATCH,1,skipped,REMOVED
"2026-06-16 01:55:00","2026-06-16 02:55",USA,"MOUNTAINEER PARK","Special Note",1.259162238,56693612,,,WATCH,1,skipped,REMOVED
"2026-06-16 04:10:00","2026-06-16 05:10",AUS,ALBURY,"Just Like Liam",1.259157272,99531184,9.40,9.40,STANDARD,2,settled,
"2026-06-16 04:17:00","2026-06-16 05:17",AUS,TOWNSVILLE,Talons,1.259158276,63926319,10.00,,WATCH,1,skipped,"price 11.0 > max 10.0"
"2026-06-16 04:21:00","2026-06-16 05:21",AUS,MENANGLE,"Bettor Be Lucky",1.259182227,11608244,6.20,,STANDARD,2,skipped,"price 16.0 > max 10.0"
"2026-06-16 04:35:00","2026-06-16 05:35",AUS,BATHURST,Charlotting,1.259157290,53913559,8.80,8.80,WATCH,1,settled,
"2026-06-16 07:21:00","2026-06-16 08:21",AUS,MENANGLE,"Mick Danger",1.259182242,42590024,9.60,,STANDARD,2,skipped,"price 380.0 > max 10.0"
"2026-06-16 07:59:00","2026-06-16 08:59",AUS,SHEPPARTON,"Im Dustee",1.259182272,72201747,6.00,,STANDARD,2,skipped,"price 3.1 < min 5.0"
"2026-06-16 09:01:00","2026-06-16 10:01",AUS,SHEPPARTON,"Guest Artist",1.259182276,89069079,6.00,5.70,STANDARD,2,settled,
"2026-06-16 12:00:00","2026-06-16 13:00",AUS,"GLOUCESTER PARK","By Gee By Jingo",1.259182316,80107577,6.00,,STANDARD,2,signalled,
"2026-06-16 13:40:00","2026-06-16 14:40",UK,STRATFORD,"Estate Planning",1.259166598,72962624,8.40,,WATCH,1,signalled,

24

General discussion / Re: Built a lay signal service with a CSV feed for MFP — fellow users might find it

« Last post by fonecorp on 16 Jun 2026, 10:43 »

Hi there
 
I have been a marketfeeder user since 2008 so nearly as long as you. In order to create a trigger and import your csv file, I need an example. As you know importing selections only allows for the selection name first followed by any variables separated by a tab and one selection per line. Is this how yours looks? Thankyou in advance

Regards Paul

25

General discussion / Re: Built a lay signal service with a CSV feed for MFP — fellow users might find it

« Last post by DanT on 15 Jun 2026, 12:10 »

thank you.

between 5.0 and 10.0

26

General discussion / Re: Built a lay signal service with a CSV feed for MFP — fellow users might find it

« Last post by armarni on 15 Jun 2026, 11:34 »

Hi Daniel,

You've put a lot of effort into that, it looks like an incredibly useful service. 

In the skipped signals section you mention that you avoid placing a trade if the price has moved outside of your target band at 30 minutes before the off.  What is the bands range?

27

General discussion / Built a lay signal service with a CSV feed for MFP — fellow users might find it

« Last post by DanT on 13 Jun 2026, 14:30 »

Hi all,

Long-time MFP user here (since 2007 — yes, I've been through a few versions!). Wanted to share something I've been building over the past couple of months that I think some of you might find genuinely useful, especially if you're into lay betting on the horses.

I've built a service called DonkeyRadar (donkeyradar.com) — it's a statistical lay-betting signal service. The short version: the model scans every qualifying UK, Irish, US and Australian horse race, analyses historical strike rates and form data, and identifies the statistically weakest horse in each field. It then signals a lay bet on that horse.

The hit rate so far is sitting at around 90% across 100+ verified signals. Every single result — wins and losses — is published publicly on the site (we call it the Honour Roll). Nothing hidden, nothing cherry-picked. I wanted to build something I'd actually trust as a bettor, and that meant full transparency from day one.

The bit that's relevant to MFP users:

I've built a CSV signal feed that you can pull into your workflow. The Pro plan gives you an API key from the dashboard, and the endpoint returns today's signals as a CSV file.

You'd need to grab the file separately and save it locally for MFP to pick up — a simple scheduled task or script that downloads the CSV every 15 minutes would do it. 

Something like:
curl -o "C:\MFP\donkeyradar-signals.csv" "https://donkeyradar.com/api/signals?key=YOUR_KEY"

The CSV includes: race time (UTC + UK), region, course, runner, market ID, selection ID, signal price, placed price, tier, stake points, status, and skip reason. It refreshes throughout the day as new signals arrive. Point MFP at the local file and set up your automation rules from there.

The signal includes a staking tier (WATCH through to NAP) based on the statistical edge we've observed for each price band — so you can set up MFP to adjust your stake size by tier if you want to get fancy with it.

I'm not going to pretend this is a guaranteed money printer — anyone who's been using MFP long enough knows there's no such thing. But the data is genuine, the results are public, and the CSV feed was built specifically with automation tools like MFP in mind. Felt like this community would appreciate that.

If you want to see what the model is picking, the free account gives you all the UK signals on a dashboard with Betfair links and recent results history.

Cheers, Danial

donkeyradar.com

28

Suggestions / Re: only to be able to select certain tracks

« Last post by fonecorp on 12 Jun 2026, 01:32 »

Sorry, try

and Selections Trigger Expression market_venue is in the list "Central Park", "Monmore", "Nottingham", "Towcester", "Doncaster"

29

Suggestions / Re: only to be able to select certain tracks

« Last post by fonecorp on 12 Jun 2026, 01:29 »

Try the Trigger condition

and Market's Name is in the list "Central Park", "Monmore", "Nottingham", "Towcester", "Doncaster"

30

Suggestions / only to be able to select certain tracks

« Last post by barberis on 11 Jun 2026, 12:42 »

How do I set my trigger to work only on the tracks I want? for example, Central Park, Monmore, Nottingham, Towcester, Doncaster. I want my trigger to work only on these tracks.