Report Types & How They Relate

Every scan produces multiple report types automatically. Understand what each contains and when it appears.

Report Hierarchy

A single run-scan call can generate up to five report types. Some are created immediately; others appear once enough data accumulates.

runLocalFalconScan
  • Scan Report always
  • Competitor Report always
  • Trend Report auto: 2+ identical scans
  • Location Report auto: 2+ keywords, same location *
  • Keyword Report auto: 2+ locations, same keyword *

Campaign scans consolidate all data into the Campaign Report. They do not generate separate Location, Keyword, or Trend reports.

Report Types

Report Type Auto-Generated When What It Contains API Endpoint Recommended Fieldmask
Scan Report Every run-scan call Core ranking data: ARP, ATRP, SoLV, found_in, grid visualization POST /v1/reports/{report_key}/ report_key,date,keyword,location,arp,atrp,solv,found_in,grid_size,ai_analysis,image,heatmap
Competitor Report Every scan (automatic) Top-ranking businesses with ARP, ATRP, SoLV, reviews, ratings POST /v1/competitor-reports/{report_key} date,keyword,businesses.*.name,businesses.*.arp,businesses.*.solv,businesses.*.reviews,businesses.*.rating
Trend Report 2+ scans with identical settings (same placeId, keyword, lat/lng, grid, radius, platform) Historical ARP/ATRP/SoLV changes across scan dates POST /v1/trend-reports/{report_key} report_key,last_date,keyword,location.name,scan_count,arp,arp_move,atrp,atrp_move,solv,solv_move
Location Report 2+ keywords scanned for same location (non-campaign only) Aggregated performance across all keywords for one location POST /v1/location-reports/{report_key} (supports fieldmask)
Keyword Report 2+ locations scanned for same keyword (non-campaign only) Aggregated performance across all locations for one keyword POST /v1/keyword-reports/{report_key} (supports fieldmask)
Campaign Report Campaign run (manual or scheduled) Consolidated data across all locations and keywords in the campaign POST /v1/campaigns/{report_key} report_key,name,status,locations,keywords,arp,atrp,solv,arp_move,atrp_move,solv_move,frequency,last_run,next_run

Campaign vs Non-Campaign Scans

Non-Campaign Scans

Standalone run-scan calls generate reports independently:

  • Scan + Competitor reports — created with every scan.
  • Trend Report — auto-generated after 2+ scans with identical settings (same placeId, keyword, coordinates, grid size, radius, platform).
  • Location Report — auto-generated after 2+ different keywords are scanned for the same location.
  • Keyword Report — auto-generated after 2+ different locations are scanned for the same keyword.

Campaign Scans

Scans triggered through a campaign behave differently:

  • Scan + Competitor reports — created per scan within the campaign.
  • Campaign Report — consolidates all scan data across every location and keyword in the campaign.
  • No separate Location, Keyword, or Trend reports — that data lives in the Campaign Report.
  • Scan reports from campaigns include a campaign_key field linking back to the parent campaign.

Report URL Patterns

Direct links to reports on the Local Falcon dashboard follow these patterns:

Report Type URL Pattern
Scan /reports/view/{report_key}
Competitor /reports/competitor/view/{report_key}
Trend /reports/trend/view/{report_key}
Location /reports/location/view/{report_key}
Keyword /reports/keyword/view/{report_key}
Campaign /campaigns/view/{report_key}

The data_points array is stripped by default from Scan, Competitor, and Trend reports. Only request it when you need per-grid-point ranking data. Use the ai_analysis field for human-readable insights instead.

Next Steps