How it works

Business analytics for local businesses

Track store views, impressions, booking attempts, successful bookings, conversion, completed activity, cancellations, no-shows, customers, and traffic sources.

Dorak helps owners see which services, products, sessions, trips, sources, and dates create activity. The analytics are operational signals, not unsupported promises about growth or revenue.

Dorak owner analytics chart screen

Best fit

Use this when a business owner wants to know what customers try to book, which services create activity, and how performance changes over time.

Customer workflow

  1. Customers view businesses, start booking or request flows, and complete supported actions.
  2. Those events become aggregated business signals instead of private claims about individual behavior.
  3. Businesses can understand demand without relying only on memory.

Business-owner workflow

  1. Review funnel and activity metrics by date range where available.
  2. Compare views, attempts, successful bookings, completed activity, cancellations, no-shows, and source signals.
  3. Use the data to adjust services, availability, content, and marketplace presence.

Concrete supported capabilities

Store views: Customer opened a store detail page. Data source: store_viewed analytics events.

Search impressions: A store card was visible in search results. Data source: store_impression analytics events.

Booking attempts: A customer clicked or started the booking action. Data source: attempted_book analytics events.

Successful bookings: A booking was created. Data source: appointment.created events remapped to successful_booking.

Booking conversion: Booking attempts divided by store views for the selected date range. Data source: dorak-analytics StoreStats conversion_rate.

Completed value: Estimated service/order value recorded when appointments or orders complete; it is not proof of online payment collection. Data source: purchase analytics events using metadata.revenue.

Completed appointments: Appointments that reached completed status. Data source: appointment_completed analytics events.

Cancellations and no-shows: Cancellation events and no-show-marked appointments used in platform analytics. Data source: appointment.canceled events and no-show reason metadata.

New and returning customers: New customer signups and users with two or more successful bookings in a range. Data source: user.created and successful_booking analytics aggregation.

Traffic source and source detail: Source labels such as app_customer, web_guest, qr, or ig_bio when present. Data source: source and source_detail fields on booking/order events.

Who uses it

  • Barbers
  • Salons
  • Fitness studios
  • Travel agencies
  • Bakeries
  • Product businesses

Screenshot still needed: Best screenshot: analytics funnel plus service/activity performance with synthetic or permitted data.

Related industries