Conference Exhibitor Churn Analyzer

Compare recurring trade-show exhibitor datasets to identify new exhibitors, lost exhibitors, category churn, and competitor event-presence shifts. Returns structured, machine-readable results for repeatable research, monitoring, automation, Apify Tasks, API workflows, and AI agents..

Quick start

Start with this working example and replace the target values with your own:

{
  "currentItems": [
    {
      "exhibitorId": "e1",
      "event": "CloudWorld",
      "company": "Acme AI",
      "category": "AI Infrastructure",
      "booth": "A12",
      "score": 90
    },
    {
      "exhibitorId": "e2",
      "event": "CloudWorld",
      "company": "Beta Data",
      "category": "Analytics",
      "booth": "B10",
      "score": 70
    },
    {
      "exhibitorId": "e3",
      "event": "CloudWorld",
      "company": "Gamma Security",
      "category": "Security",
      "booth": "C04",
      "score": 80
    }
  ],
  "previousItems": [
    {
      "exhibitorId": "e1",
      "event": "CloudWorld",
      "company": "Acme AI",
      "category": "AI Infrastructure",
      "booth": "A08",
      "score": 75
    },
    {
      "exhibitorId": "e4",
      "event": "CloudWorld",
      "company": "Delta Ops",
      "category": "DevOps",
      "booth": "D01",
      "score": 60
    }
  ],
  "maxItems": 20000
}

The Actor writes structured results to the default Apify Dataset and can be used from the Store, API, schedules, Tasks, automations and MCP-compatible AI workflows.

Input

• currentItems — Current records: Current source or normalized rows to analyze.
• currentDatasetId — Current Apify Dataset ID: Optional Apify Dataset ID used when currentItems is not supplied.
• previousDatasetId — Previous Apify Dataset ID: Optional previous Apify Dataset ID used instead of previousItems.
• maxItems — Maximum records: Maximum records loaded from a Dataset input.

All integration and advanced analysis fields are optional. The default example is intentionally runnable without configuring MCP or a previous-run baseline.

Output

The Dataset exposes predictable machine-readable output. Representative fields include results.

Pricing

This Actor uses Pay Per Event. The current factory base price is $0.015000 per result event. The Apify Store remains the source of truth for the price and plan/tier details shown to the buyer.

Use cases

• Run the buyer-ready workflows exposed as Apify Tasks without preparing a custom integration first.
• Use the Actor from API or schedules for recurring collection, comparison or monitoring.
• Feed the structured Dataset output into spreadsheets, databases, automations or AI agents.
• Compare repeat runs when the product supports snapshots or previous-run inputs.

Automation and AI

Use the same Actor through Apify API, schedules, public Tasks and the Apify MCP server. Outputs are structured for downstream workflows and AI agents rather than requiring manual copy/paste.

Limitations

• Public websites and upstream APIs can change markup, access rules, rate limits or field availability without notice.
• Fields that are not publicly available are returned as unavailable or omitted rather than fabricated.
• Analytical outputs depend on the quality and coverage of the supplied or collected source data.
• Treat marketplace, reputation, workforce, safety or commercial signals as decision support and validate material decisions against the underlying source evidence.

Detailed documentation

Detailed documentation

Compare recurring trade-show exhibitor datasets to identify new exhibitors, lost exhibitors, category churn, and competitor event-presence shifts.

Why use this Actor

Exhibitor scrapers return a current list, while event and sales teams need to know who arrived, who disappeared, and which categories or competitors are changing presence over time. This Actor sits above raw extraction: supply a current dataset, optionally add a previous snapshot, and receive an aggregated report built for recurring monitoring and AI-agent workflows.

Key features

• Year-over-year exhibitor entry and exit intelligence.

• Category-level churn and event-presence shifts instead of one-time lead extraction.

• Snapshot-based competitor attendance monitoring.

• Works downstream of exhibitor-list scrapers without requiring another crawl.

• Reads inline JSON rows or Apify Dataset IDs with limited READ permission.

• Writes one auditable report to the default Dataset and INTELLIGENCE_REPORT.

Example

Use the prefilled example or replace currentItems with rows from an upstream Actor. On recurring runs, provide the prior period in previousItems or previousDatasetId. The Actor normalizes common aliases, compares snapshots, ranks the strongest entity changes and emits agentAction.

Use cases

• event strategy and sponsorship teams.
• B2B competitive intelligence.
• sales territory and partner planning.

Pricing

One primary pay-per-event outcome: one decision-ready intelligence report. Base price USD 0.015 before Apify tier discounts. The 256 MB data-first architecture is designed for strong unit economics.

Limitations

• Analyzes supplied public or appropriately licensed data and does not bypass restricted sources.
• Scores are decision-support signals, not predictions or guarantees.
• Keep stable identifiers across snapshots for best change detection.
• Zero-direct-competition status is rechecked before publication because the Store changes continuously.

Workflow

upstream dataset -> current snapshot -> optional previous snapshot -> normalization -> entity aggregation -> change scoring -> ranked signals -> agentAction.

Input

Provide current normalized records in currentItems or an Apify Dataset ID in currentDatasetId. Add previousItems or previousDatasetId for period-over-period comparison. Optional Gen2 fields support prior-analysis comparison and transparent economic-impact assumptions.

Output

The Actor writes one decision-ready report to the default Dataset, including normalized counts, ranked signals, change metrics, confidence, executive decision, regression status, recommended action, and an auditable agentAction.

Data quality and interpretation (October 2026)

Conference Exhibitor Churn Analyzer analyzes data provided by you. It does not promise real-time access to third-party data sources.

• Inputs: currentItems and previousItems (or currentDatasetId and previousDatasetId). See the Input tab and provide lawful and properly sourced data.
• Comparable snapshots: if no previous snapshot exists, baselineAvailable is false and the Actor must not claim measured openings, losses or movement. Use a prior snapshot for change metrics.
• Data caveats: duplicate identity keys are reported. Non-finite numbers are sanitized for machine-readable output, not proof that the source contained a real zero.
• Pricing and limits: check Apify's live Pricing tab for events and discounts, test with a small sample, and set the platform max-charge limit. Abort handling is implemented.
• Verification: check consequential business, legal, employment, financial or medical conclusions against primary sources.

Agent execution and AI discovery (October 2026)

Use this Actor when: Compare recurring trade-show exhibitor datasets to identify new exhibitors, lost exhibitors, category churn, and competitor event-presence shifts. Returns structured, machine-readable results for repeatable research, monitoring,...

For AI agents and automations:

• Find this Actor in Apify Store by its use case and verify its actual input and pricing through Apify MCP (search-actors and fetch-actor-details). Availability and ranking in Apify AI are controlled by Apify; discovery is not guaranteed.
• Read the Input tab or input schema. Recognized fields include currentItems, currentDatasetId, previousItems, previousDatasetId, maxItems, previousAnalysis, valuePerImpactUnitUsd, monthlyRuns. Required fields: See the Input tab for valid example values. Do not invent records or credentials.
• Supply a small representative input first. Use Apify API, Tasks, or MCP to run and retrieve the structured dataset; inspect the output schema rather than assuming all inputs produce the same rows.
• For programmatic calls, set timeouts and maxTotalChargeUsd in run options to limit exposure. Check the Apify Pricing tab for billable events and discounts.
• Payment compatibility: this Actor is published with limited permissions and pay-per-event pricing. Apify AGI prepaid x402 tokens can execute limited-permission Actors. Direct per-request payment is a separate, conditional feature that may require additional eligibility checks and creator verification. Do not interpret this paragraph as proof of approved KYC or guaranteed payment acceptance.
• This Actor does not independently guarantee real-time access to a third-party source. Verify input provenance and important conclusions, and do not supply confidential personal data unnecessarily.