Location-aware delivery
Campaigns must trigger only in approved zones and mobility corridors, with false positives captured as exceptions.
Cape Town pilot · First week of November 2026
Proving verified mobility media in live market conditions.
A controlled RYDCAST deployment across Cape Town mobility zones to test ad delivery, display readiness, proof confidence, QR handoff, and reporting before wider expansion.
Pilot at a glance.
- MarketCape Town, South Africa
- WindowFirst week of November 2026
- EnvironmentE-hailing vehicles and minibus taxi routes
- OutputProof report, operating learnings, and expansion recommendation
What the pilot proves
This is a measurement exercise, not a marketing demo.
The pilot is designed to show whether verified media can be delivered, proved, reported, and prepared for settlement under real ride conditions.
Proof confidence
Each confirmed play is checked against zone match, timestamp, playback state, device state, and available display signals.
Operational readiness
Driver phone, in-vehicle display, pairing, connectivity, and recovery behavior are evaluated during actual trips.
Offer handoff
QR, website, coupon, or contact-number actions are measured only when a campaign uses an offer journey.
Commercial record
Evidence is structured so advertisers, fleet partners, and operators can audit what ran, where, and when.
Expansion signal
Zone performance and operating friction determine the next market, fleet, and partner rollout plan.
Coverage logic
The coverage zones are the test.
Each Cape Town zone represents a different mobility use case: airport transfer, tourism, retail, nightlife, commuter, and commercial movement.
Measurement plan
What gets measured during the pilot.
Results will be published after the pilot run. Before deployment, this section defines the signals RYDCAST will track and how exceptions will be separated from confirmed evidence.
DeliveryMeasured
ProofAudited
UptimeTracked
- Ad delivery attempts compared with confirmed plays
- Driver-phone to display pairing continuity
- Display uptime, playback state, and recovery events
- Zone match, GPS confidence, route evidence, and timestamp integrity
- QR scans, website opens, coupon handoff, or contact actions when enabled
- Exceptions such as offline sessions, stale telemetry, failed playback, or duplicate evidence
Case study output
What the pilot produces after November.
The case study will make the expansion decision easier: where the system worked, where operations need tightening, and which partner path is ready next.
Deployment summary
Vehicles, zones, campaign setup, operating window, and live constraints.
Evidence report
Confirmed plays, proof confidence ranges, display uptime, and exception categories.
Zone performance
Airport, retail, hospitality, nightlife, commuter, and commercial patterns compared.
Engagement readout
QR, website, coupon, or contact handoff results where campaigns used passenger actions.
Commercial model check
How verified delivery connects to advertiser reporting, fleet records, and settlement logic.
Expansion recommendation
Recommended next city, fleet type, advertiser category, and operational requirements.
- Before pilotVehicles, zones, campaigns, and proof rules locked
- Pilot weekLive deployment and exception capture
- Post pilotEvidence report and case study produced
- NextExpansion decision and partner rollout plan
Who this is for
Partners who need evidence before scale.
Designed for partners who want the proof criteria, measurement plan, and expansion logic before the November deployment.
- Investors Reviewing whether verified mobility media can become a defensible infrastructure category.
- Strategic fleet partners Evaluating how vehicles, screens, drivers, and operating rules perform in market.
- Advertiser partners Testing measured local reach, QR handoff, and auditable proof before wider media spend.
- Expansion partners Comparing Cape Town evidence against the requirements for future cities and regions.
Next step
Request the Cape Town pilot briefing.
For investors, fleet partners, and advertiser partners who want to review the proof criteria before the first-week November deployment.
hello@cast.tech