Rouble tracking new markets on Bet365

[aurumvalue]

Hi,

I’m using Distill to track when new markets are added on a sportsbook.

It works perfectly on Unibet by monitoring the “number of markets” (for example: 23 → 31 markets).

But when I try the same thing on bet365, it doesn’t work properly.

What I’m trying to do:
Get a notification when new markets are added to a match by tracking the market count.

Problems:

• The page sometimes doesn’t load (just shows loading/spinner)

• No history is saved

• It doesn’t detect changes even when markets are clearly added

My questions:

1. Is this kind of page possible to monitor with Distill?

2. Is there a better way to track dynamic pages like this?

3. Any tips to avoid getting logged out while monitoring?

   Website example: bet365 - Sportspel på internet

Thanks in advance!

[srijith (Srijith V)]

@aurumvalue Thanks for the detailed explanation.

To help you properly, could you please share the exact navigation flow you use to reach the page where the “number of markets” appears on bet365?

For example, something like:

1. Open bet365 homepage

2. Click Football

3. Select a league

4. Open a specific match

5. Where exactly the market count is shown

If possible, please also include:

• A screenshot of the page where the market count is visible

• Whether you are logged in or not when monitoring

Once I have that, I can take a closer look and give you a better answer.

[aurumvalue]

Hi,

Thanks for your help!

I want to clarify that I have not used Distill on bet365 before. I’ve only used it on Unibet, where it works well and I don’t need to be logged in for monitoring.

It seems like being logged in on bet365 might make things a bit more complicated.

Navigation flow:

1. Open bet365 homepage

2. Click on the search bar

3. Search for a term (for example: “throw-ins”)

This shows a list of matches that currently have that specific market available.

What I want to do:
I want to get a notification when NEW matches appear in this list (for example when a new match gets “throw-ins” markets and shows up in the search results).

Extra info:

• I am not currently monitoring bet365, as I haven’t been able to get it working yet

• I would prefer to run Distill via cloud so I don’t need to keep my computer on while monitoring (Like I do on Unibet)

Is it possible to reliably monitor this kind of dynamic search result list with Distill?

Or is there a better way to track when new matches appear in search results like this?

Thanks in advance!

[srijith (Srijith V)]

@aurumvalue Thanks for the detailed explanation — that really helps clarify what you’re trying to achieve.

I took a closer look at bet365, and it appears that the site has fairly strong security measures in place. In our testing, the page either remains stuck on loading (spinner) or actively blocks access, even when using proxies.

Because of this, cloud monitoring is currently not reliable/possible for bet365.

You may still be able to get this working using local monitoring (Browser extension / Desktop App)

Local monitoring behaves more like a real user session, so it has a better chance of working compared to cloud.

[aurumvalue]

Hi,

Thanks again for your help.

I tested this further using local monitoring in Chrome.

My current setup:

• Device: Google Chrome (this device)

• Interval: Every 10 minutes

• Running locally (not cloud)

I am monitoring the search results page (for example searching “throw-ins”).

As you can see in the screenshot, I have selected multiple elements in the list (each match row / description).

Note: My bet365 interface is in Swedish, in case that affects anything or looks different on your end.

My question:

Is this the correct way to monitor a list like this in Distill?

Or should I instead be monitoring a single parent/container element that includes the entire list?

I’m not sure what the best practice is for detecting when new items are added to a dynamic list like this.

Thanks again for your help!

[aurumvalue]

[srijith (Srijith V)]

@aurumvalue Yes — in this case, selecting the listed items individually is usually not the best approach.

The main issue is that if new listings are added later, those new rows will not automatically be part of your current selection, so Distill may miss them.

A better approach would be one of these:

1. Monitor the parent/container element
This is the recommended option for a dynamic list like this. If the whole results block changes when new matches are added, Distill will detect that more reliably.

2. Use a repeating selector pattern
If you want to keep monitoring item-level rows, then using a selector pattern such as nth-child(n) can work better than manually selecting multiple individual entries. That way, the monitor is based on the list structure rather than the exact currently visible rows.
So, in this case instead of those many CSS selectors your only CSS selector will be:

div:nth-child(n) [class*='SearchMarketsMarketGroup'] [class*='Description']

This ensures:

• All current items are included

• Any newly added items are automatically captured

Click on the “Open Webpage Selector” remove all the current CSS selectors and replace it with the CSS selector I have shared and test it.

[aurumvalue]

---

Thank you for the suggestion. I tried the div:nth-child(n) [class*='SearchMarketsMarketGroup'] [class*='Description'] selector but the core issue remains — Bet365 dynamically rotates which matches appear in the list every few minutes. Matches disappear and reappear constantly, which causes Distill to trigger false alerts even when no genuinely new matches have been added. I also tried increasing the delay to 10 seconds but it did not help.

Do you have any recommendations for how to handle this type of dynamic content where matches rotate in and out frequently? Maybe there is a way in Distill to only trigger a notification when the added text has never appeared in any previous check?

[aurumvalue]

[aurumvalue]

[srijith (Srijith V)]

@aurumvalue In such cases, you can use the condition:

Text → doesn't match any previous text

This condition checks whether the newly detected text is different from anything seen before in the change history.

This is particularly useful for dynamic lists where items move around or reappear.

After setting the condition, make sure to use the “Test conditions” button .

• If Final result = True → notification will be triggered

• If Final result = False → notification will NOT be triggered

This helps you confirm that the condition behaves as expected before relying on it.

[aurumvalue]

Thank you! I already tried this condition but it still triggers notifications for matches that have appeared before. The issue is that the entire text block is always slightly different due to the rotation, so the condition always returns True — even when no genuinely new matches have been added.

I have attached a screenshot showing the Test Conditions panel. You can see that “Net added text” shows “Aston Villa Bologna Athletic Club v Villarreal Köln Werder” but at the same time “Net deleted text” shows many of the same teams like “Strasbourg Mainz Betis Birmingham Wrexham” — these matches have just rotated out and back in, they are not genuinely new.

Is there a way to check individual lines against the history rather than the entire text block? I thinkt that would solve the problem since a match would only trigger a notification if that specific line has never appeared before.