Scraping dynamic content addresses the situation where the data on a page is not present in the original source code but is added by a script only after loading. A simple tool downloads an empty skeleton and doesn't see the data. The solution is usually to use a headless browser that actually renders the page and waits for loading to finish. This approach is an order of magnitude more demanding on both performance and time, so it isn't worthwhile at larger volumes. A cheaper alternative is to find the interface the page itself uses to pull the data, and draw directly from it, if the terms of use allow it. When designing a solution, bear in mind that dynamic pages change more often and that collection requires ongoing maintenance.
See also: API as a data source, JavaScript rendering, Data collection monitoring.
