@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 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:
@aurumvalue For this you will have to use both conditions using an AND logic - Net added text → is not empty AND Text → doesn't match any previous text