Cross Matching Bets

[Ian]

Doesn't affect me but Betfair have announced they are running the cross matching bot on in-running bets today for two meetings. I suppose that will stop you getting matched occasionally at fluke odds ?

[doris_day]

How will they be able to do this correctly with FOK bets ?

[Ian]

Does Betfair actually recognise ForK bets or is it just that BA cancels the unmatched portion itself. Don't know as I've never used it. If it's the latter then presumably there will be less killed bets.

[doris_day]

I'm not certain how they are recognised by Betfair per se but the whole idea seems a little odd to me anyway and I suspect can only have a negative effect on the bet matching process in terms of speed.
They told me it was to increase liquidity but the real reason is so they can skim an extra few quid here and there.

The best way for BF to increase liquidity in horse racing in-play markets is for them to take control of the transmission of the race course pictures. If they then provided everyone with pix without a built in delay a la ATR, then people's fears of being ripped off would largely disappear and they would add liquidity.

[alrodopial]

For us who don't know English well , what is 'cross matching bets' ?

[doris_day]

The easiest way to understand it is with a two player market like tennis. Say the odds were 2.0-15.0 on player 1 and 1.1-1.9 on player 2. Say you backed player 1 at market you'd be asking for 2.0 but actually you'd get a better deal by laying player 2 at 1.9, so Betfair do it for you and 'cross-macth' at a better price for you.

It naturally gets a lot more complicated with a market like horse racing but the same principles apply.

[mak]

hi (this is from another forum)



Yes, that was the case, but it's all changing today, according to the post BF Customer Services made yesterday:

As announced last week we’ll be making improvements to Betfair’s bet matching logic tomorrow, Monday 14th July. We’ve made a number of announcements to keep customers informed, but wanted to take the opportunity to explain the changes in detail.

What’s changing?
We’ve improved the code that matches bets. As well as matching backs against lays as we’ve always done, we’ll also try to match your bet against bets on other selections in the market. We‘ll give you an improvement over the price you‘ve requested where possible, and we‘ll match you against whichever bets get you the best price.

For example in a tennis market:

Roger Federer is 1.9 to back, 2.1 to lay.
Rafael Nadal is 1.8 to back, 2.0 to lay.

If you try to back Federer at 1.9 or less, previously we would have matched your bet against the customer looking to lay Federer at 1.9. Both bets would have been matched at 1.9, even if you‘d asked for a shorter price. In theory we could do even better than that though: we could match you against the customer trying to back Nadal at 2.0 (backing one player at 2.0 is of course the same as laying the other player at 2.0). Our new bet matching process will see which match gets you the better price. In this case we would get you 2.0 by matching you against the Nadal backer (who is offering a better price than the layer of Federer).

When placing a new bet you will only ever be matched by the new process if doing so gives you a better price than you would otherwise have got. We will match your bet at the best price possible that’s a valid increment on Betfair’s odds ladder, as we explained in our update of 6th June.

Does this only work for 2-runner markets like tennis?
No. The new matching logic works for any number of runners in a market. An example with a 2-runner market is probably easiest to understand, but the principle is the same for markets with 3 runners or more. For example if a football market looked like this:

Spain 2.3 to back, 2.5 to lay
Germany 3.9 to back, 4.0 to lay
The Draw 2.9 to back, 3.0 to lay

Then if you want to back Spain we could match you with customers looking to back Germany and the Draw at 4.0 and 3.0 respectively, which would result in you being matched at 2.4, a better price than you would have got had we matched you against Spain layers (who are only offering 2.3).

Which markets will this affect?
We’ll introduce the new code on Monday 14th July, but initially matching will be done exactly as before. As explained earlier in the year, introducing best execution across selections wasn’t possible without significant change to the existing code that matches backs and lays, so we will need verify that performance is as expected for the existing matching process before enabling the new functionality. All being well we’ll enable the new code for a small number of markets to ensure that everything is as it should be later on Monday. We’ll announce which markets on Monday. Again if all is well we’ll roll out to a wider range of markets on Tuesday.

We’d expect to match across selections on the same range of markets as we currently do:

Match Odds in Basketball, Boxing, Cricket, Ice Hockey, Rugby League, Rugby Union, Snooker, Tennis and Volleyball, Greyhounds win markets, Darts match odds, correct score and handicaps and Soccer match odds, HT/FT, correct score and unders/overs.

Horse racing will not be covered for now, due to the possibility of non-runners, and the new process isn’t applicable to markets where runners can be added (for example “Next manager” markets), where runners listed might not take part (e.g. First Goalscorer) or where the runners in a particular “market” are treated independently (e.g. Accumulators).

What about bets placed in error?
We’re aware of a concern that this change might make it more likely that customers would match bets placed in error, for example asking for 1.2 when you really wanted to back at 2.2. One consequence of the change we’re making is that any bet you place is more likely to get matched - making it easier to get a match is the whole idea. Being realistic though, if you had placed a bet in error like that in the past, in the vast majority of cases you would have been matched (against lays on that selection). There’ll now be far, far more circumstances where you would have been matched anyway , but instead you’ll now get a better price, than situations where your bet would have been unmatched and you might have had the chance to cancel. On average we would expect customers who place bets in error to be better off as a result.

On a related point, we’d also expect this change to make it more difficult for people who place “trap bets” to get matched (a trap bet is an offer that is only likely to be matched if another customer places a bet in error). While putting up “trap bets” is against Betfair’s terms and conditions and we close the accounts of persistent offenders, on an exchange where any customer can ask for any price it’s difficult to eradicate this practice. In most instances where a trap bet is the best price available on a selection, customers will in future be matched at better prices against bets on other selections rather than matching the trap bet.

How will the change affect liquidity?
We would expect the change to be beneficial to liquidity. Obviously if we have opposing customer bets in the system that could be matched, whether on the same selection or across different selections, the best thing for liquidity is to match them.

[alrodopial]

Thanks guys,

Mak, how are you mate?

[mak]

Thanks guys,

Mak, how are you mate?

hi al
I am fine, considering the circumstance in our country...

[osknows]

Thanks guys,

Mak, how are you mate?

hi al
I am fine, considering the circumstance in our country...

That's okay Germany's paying

We're just as bad here in the UK, country's run by clowns with the comedians ready to take over...

[alrodopial]

Thanks guys,

Mak, how are you mate?

hi al
I am fine, considering the circumstance in our country...

That's okay Germany's paying

We're just as bad here in the UK, country's run by clowns with the comedians ready to take over...

Human being is the same everywhere as I see ...

[GaryRussell]

Betting Assistant will now calculate the cross matched prices to display in line with the website on certain markets. See http://gruss-software.co.uk/forum/viewtopic.php?t=3845