Dice.fm Events Search Scraper: Extract Music Events at Scale

---

What Is Dice.fm?

Dice.fm is a leading digital platform for discovering and purchasing tickets to live music events, club nights, and festivals worldwide. It hosts thousands of event listings across multiple cities and genres. Manually extracting event details from search results is tedious and error-prone — the Dice.fm Events Search Scraper automates this process, transforming search result pages into clean, structured datasets ready for analysis or resale.

---

Overview

The Dice Events Search Scraper extracts event records from Dice.fm search pages, capturing comprehensive data for each listing. It is ideal for:

• Event aggregators building multi-source event databases
• Ticket resellers monitoring event availability and pricing
• Music analysts tracking tour dates and lineup trends
• Marketing teams gathering competitive event intelligence
• Developers powering music discovery applications

The scraper handles paginated search results seamlessly, supports bulk URL imports, and gracefully manages failures with configurable retry logic.

---

Input Format

The scraper accepts a JSON configuration specifying which search pages to target:

{
  "urls": [
    "https://dice.fm/browse/berlin-5e426dbb749e68e3e923d1e4/music/gig"
  ],
  "ignore_url_failures": true,
  "max_items_per_url": 200
}

Field	Description
urls	Dice.fm browse/search result URLs filtered by city, genre, or event type
max_items_per_url	Maximum events extracted per page (default: 20, max: 200)
ignore_url_failures	If true, the scraper continues if a URL fails; if false, the run stops

Tip: Search pages are identified by /browse/[city-id]/[category]/[type] patterns. Include multiple URLs to cover different cities or genres.

---

Output Format

Sample output

{
  "event_id": "6acdf4eceefef8000119963a",
  "name": "Editors: 'Surface, Echo and Sound' Acoustic + Signing",
  "status": "sold-out",
  "acquisition_type": "purchase",
  "event_tag": null,
  "image_url": "https://dice-media.imgix.net/attachments/2026-10-15/7416c792-d780-4630-ae2c-f7514c1da954.jpg?rect=0%2C0%2C1000%2C1000",
  "timezone": "Europe/Berlin",
  "announcement_date": "2026-10-13T16:00:00+02:00",
  "pre_sale_start_date": null,
  "sale_start_date": "2026-10-13T16:00:00+02:00",
  "sale_end_date": "2026-10-30T19:30:00+01:00",
  "event_start_date": "2026-10-30T20:00:00+01:00",
  "event_end_date": "2026-10-30T22:30:00+01:00",
  "is_multi_days_event": false,
  "venue_id": "12349",
  "venue_name": "Rough Trade Berlin",
  "venue_space_name": null,
  "venue_address": "Ganghoferstraße 10, 12043 Berlin, Germany",
  "city_name": "Berlin",
  "country_code": "DE",
  "country_name": "Germany",
  "latitude": 52.5065133,
  "longitude": 13.1445545,
  "price_currency": "EUR",
  "price_amount": null,
  "price_amount_from": 3292,
  "raw_data": null,
  "from_url": "https://dice.fm/browse/berlin-5e426dbb749e68e3e923d1e4/music/gig"
}

The scraper returns JSON data with each event as an object containing detailed fields. Understanding field purposes enables effective analysis and application.

Event Information

event_id: Unique identifier of the event on the platform. Purpose: Database indexing, deduplication, tracking an event over time.

name: Event title (artist/show name and edition). Purpose: Event identification, search, and display.

status: Current ticket availability status (e.g., sold-out). Purpose: Filtering available vs. sold-out events, demand analysis.

acquisition_type: How tickets are obtained (e.g., purchase). Purpose: Distinguishing direct purchase from other access models.

event_tag: Special tag/label attached to the event, if any. Purpose: Highlighting promoted or specially categorized events.

image_url: Square cover image of the event. Purpose: Preview display in dashboards and catalogs.

Dates and Timing

timezone: Timezone of the event. Purpose: Converting event times correctly.

announcement_date: Date and time the event was announced. Purpose: Measuring lead time between announcement and event.

pre_sale_start_date: Pre-sale start date, if any. Purpose: Identifying events with early access sales.

sale_start_date: Date and time general ticket sales open. Purpose: Planning purchases, analyzing sell-out speed.

sale_end_date: Date and time ticket sales close. Purpose: Knowing the purchase deadline.

event_start_date: Event start date and time. Purpose: Scheduling, calendar alerts, trend analysis.

event_end_date: Event end date and time. Purpose: Calculating event duration.

is_multi_days_event: Whether the event spans multiple days. Purpose: Separating single-day events from festivals/multi-day events.

Venue and Location

venue_id: Unique identifier of the venue. Purpose: Grouping events by venue.

venue_name: Venue name. Purpose: Venue-level analysis and lead generation.

venue_space_name: Specific room/stage within the venue, if any. Purpose: Distinguishing events in different rooms of the same venue.

venue_address: Full venue address. Purpose: Navigation, geographic analysis.

city_name: City where the event takes place. Purpose: City-level market segmentation.

country_code: ISO country code. Purpose: Country-level filtering and joining with geographic datasets.

country_name: Country name. Purpose: Display and regional analysis.

latitude / longitude: Coordinates of the city/location. Purpose: Mapping and distance analysis.

Pricing

price_currency: Currency code of the ticket price. Purpose: Price normalization across markets.

price_amount: Fixed ticket price, if provided (null when price varies). Purpose: Price analysis for single-price events.

price_amount_from: Starting ticket price in the currency's minor unit (e.g., 3292 = 32.92 EUR). Purpose: Price benchmarking, comparing entry cost across events.

Raw Data

raw_data: Original unmodified JSON of the event. Purpose: Accessing any field not exposed in the cleaned output (tracking IDs, nested city IDs, etc.), debugging, auditing.

---

How to Use

1. Identify search URLs — Browse Dice.fm, navigate to a search/browse page (filtered by city, genre, date), and copy the URL.
2. Build your URL list — Paste one or multiple URLs into the urls array. You can scrape the same page multiple times or combine different cities/genres.
3. Set item limits — Use max_items_per_url: 200 for comprehensive results or lower the value for smaller extracts.
4. Enable failure tolerance — Set ignore_url_failures: true for bulk jobs to prevent interruptions from temporary network issues.
5. Run the scraper — Execute the actor and monitor progress in the run log.
6. Export data — Download results as JSON, CSV, or Excel for CRM, analytics, or resale integration.

Common issues:

• Search pages require the correct city ID; verify URLs match /browse/[city-id]/...
• Pagination may limit visible results on some searches; use multiple URL snapshots over time for complete coverage.

---

Use Cases & Business Value

• Event aggregation: Combine Dice.fm data with other sources to build a unified event database
• Price monitoring: Track ticket pricing across events and detect flash sales
• Artist tracking: Identify tour dates for favorite musicians across multiple cities
• Competitive analysis: Monitor competitor events and promotional strategies
• Business intelligence: Analyze event trends, attendance demand, and genre popularity

The scraper eliminates hours of manual copying and pasting, delivering consistent, analyzable event records that integrate with CRMs, data warehouses, or custom applications.

---

Conclusion

The Dice.fm Events Search Scraper is an essential tool for anyone building event databases, monitoring music markets, or automating ticket research. With rich output across 40+ fields and flexible URL configuration, it transforms browsing into actionable data in minutes.