Do you always get the best available price on Betdaq?

[jamesedwards]

I'm new to Betdaq but experienced with Betfair.

Betfair always seems very consistent at matching me with the best available price at the time of my bet hitting the market, so I always stick my trade in well under the odds in order to be sure of getting matched.

With Betdaq today I'm almost always getting matched only at my asking price. Playing back videos I'm seeing better prices before, during, and after my trade hitting the market. Surely this shouldn't be possible?

[jamesedwards]

Still happening on most races this afternoon.

On the 17:45 at Hexham I was matched at 1.01 on a horse that never went below 1.05.

Is there a setting I need to switch on?

[jamesedwards]

On the 17:45 at Hexham I was matched at 1.01 on a horse that never went below 1.05.

Here's the video. Can anyone explain how this can happen?

betdaq example (online-video-cutter.com) (1).mp4

[sionascaig]

On the 17:45 at Hexham I was matched at 1.01 on a horse that never went below 1.05.

Here's the video. Can anyone explain how this can happen?

betdaq example (online-video-cutter.com) (1).mp4

Bizarre...

According to this, it doesn't happen...

https://betdaq.zendesk.com/hc/en-gb/art ... uctuations

"all users active on BETDAQ accept Best Execution as an automatic feature of their participation on the BETDAQ Exchange"

[Euler]

That is really odd

[jamesedwards]

Just had another example where I was matched at well below the market price that was available before, during, and immediately after my bet hitting the market. The prices showing on BA at that moment were aligned exactly with the prices showing on the main Betdaq site, so it's not that.

I've already updated my BA for BD from 1.28.4 to the latest available 1.28.5 just in case.

Any other ideas? Should I raise this issue with BA or with Betdaq?

[Anbell]

Just had another example where I was matched at well below the market price that was available before, during, and immediately after my bet hitting the market. The prices showing on BA at that moment were aligned exactly with the prices showing on the main Betdaq site, so it's not that.

I've already updated my BA for BD from 1.28.4 to the latest available 1.28.5 just in case.

Any other ideas? Should I raise this issue with BA or with Betdaq?

It cant be a BA issue

[Anbell]

Just had another example where I was matched at well below the market price that was available before, during, and immediately after my bet hitting the market. The prices showing on BA at that moment were aligned exactly with the prices showing on the main Betdaq site, so it's not that.

I've already updated my BA for BD from 1.28.4 to the latest available 1.28.5 just in case.

Any other ideas? Should I raise this issue with BA or with Betdaq?

It cant be a BA issue

Unless BA is recording the bet data incorrectly. Does your Betdaq account report the same?

[Euler]

Just had another example where I was matched at well below the market price that was available before, during, and immediately after my bet hitting the market. The prices showing on BA at that moment were aligned exactly with the prices showing on the main Betdaq site, so it's not that.

I've already updated my BA for BD from 1.28.4 to the latest available 1.28.5 just in case.

Any other ideas? Should I raise this issue with BA or with Betdaq?

Pretty sure it's not our error, but we will check, then raise with Betdaq.

[jamesedwards]

Unless BA is recording the bet data incorrectly. Does your Betdaq account report the same?

I've run the main Betdaq site simultaneously and the data matches BA.

Pretty sure it's not our error, but we will check, then raise with Betdaq.

Thanks Peter.

It's happening quite often. Here's another one from the first race at Catterick this afternoon.

Back bet at 1.01 triggered with money available at 1.49, then 1.60, then 1.55.
Bet hits the market after 1 sec delay, and matches at 1.0852 yet there's still plenty of money available all the way up to 1.20 afterwards.

betdaq example 2 (online-video-cutter.com).mp4

[jamesedwards]

Still happening.

This one from the 17:45 @ Sligo just now was a particularly good example.

Triggered a back bet for £1 @ 1.01 with 1.60 available. After the one-second delay 1.13 was still available yet my bet was matched at only 1.01. Prices available remained well above 1.01 for some time after.

Sligo example.mp4

[Michael5482]

Still happening.

This one from the 17:45 @ Sligo just now was a particularly good example.

Triggered a back bet for £1 @ 1.01 with 1.60 available. After the one-second delay 1.13 was still available yet my bet was matched at only 1.01. Prices available remained well above 1.01 for some time after.


Sligo example.mp4

What is there minimum stake? Not doing some type of calc/bet placement behind the scenes at 1.01 is it to compensate for the stake if the minimum is above £1 and it's getting took? Hopefully there is a reasonable answer because that is a long way off.

[jamesedwards]

Still happening.

This one from the 17:45 @ Sligo just now was a particularly good example.

Triggered a back bet for £1 @ 1.01 with 1.60 available. After the one-second delay 1.13 was still available yet my bet was matched at only 1.01. Prices available remained well above 1.01 for some time after.


Sligo example.mp4

What is there minimum stake? Not doing some type of calc/bet placement behind the scenes at 1.01 is it to compensate for the stake if the minimum is above £1 and it's getting took? Hopefully there is a reasonable answer because that is a long way off.

Thanks for the idea, but it's not stake. Minimum stake on Betdaq is 10p, and the same thing happens whatever stake I use.

[jamesedwards]

Since I started trialling Betdaq exactly a week ago I've had this problem every day so far.

But suddenly today it seems to be fixed and I'm getting the displayed price every time.

I've not changed anything. Hope it continues.

[Euler]

Did you get the same error regardless of the interface you were using?