Mobile Ads
The same platform.
Inside your consumer app.
Use the same targeting, Ad Studio, and proof-of-play to run brand-safe placements in the mobile apps your patients already use.
Live · In-app ad
One surface more
Your screen network already knows your audience. Now your app can too.
The same platform that targets ads by office, specialty, and geography now pushes placements into your consumer app. No new stack. No separate reporting. One brain, one more surface.
How it works
Same brief. Same loop. New surface.
One audience graph
Specialty, location, appointment context, and observed behavior from the screen network feed the same targeting model that serves in-app ads.
Same Ad Studio
One brief creates both screen and in-app variants. The compliance agent screens each format against network and app-store rules before a human approves.
One proof trail
Unified proof-of-play and attribution across screens and app. Sponsors see one campaign, one reach number, one invoice.
SDK
Built for apps, not for ad-tech complexity.
A lightweight SDK that treats your app as a first-class surface. Server-side decisioning, client-side caching, and offline resilience.
Lightweight iOS & Android SDK
Small binary footprint, minimal initialization, native Swift/Kotlin APIs. No WebView hacks or heavy third-party mediation layers.
Server-side ad decisioning
Ad calls route to the same core your screens use. Targeting, frequency caps, and pacing happen in one place, not in the app.
Offline caching & reconciliation
Ads cache locally. Event telemetry queues and reconciles when the connection returns. No dropped impressions, no blank moments.
Use cases
What operators run on the app surface.
Sponsor campaigns
Extend a screen buy to the phone. The same brand, the same offer, the same proof-of-play.
Appointment reminders
Contextual nudges before a visit. Useful, not intrusive, because the app already owns the appointment relationship.
Wellness content
Short-form health education, seasonal campaigns, and network news delivered to the pocket.
Cross-promotion
Promote a new host office, a new service line, or a new screen location to app users within the same geography.
Questions
What operators ask before adding the app surface.
Do we need a separate platform for in-app ads?
No. Mobile app ads run from the same Signal115 core as your screen network. The same audience graph, Ad Studio, targeting engine, and proof-of-play. You just add an in-app surface.
Does this replace our waiting-room screens?
No. It complements them. Screens capture attention in the office; the app extends that relationship to the phone. The same sponsors can run across both surfaces in one buy.
What apps can it serve?
Any consumer app you own or operate: patient apps, member apps, wellness apps, or partner apps. The SDK is designed for iOS and Android with a lightweight integration footprint.
How is it priced?
The in-app ad surface is scoped into the platform build, not a separate product. It is sized and delivered as part of the same fixed-fee engagement.
Every screen. Every office. Every app. One brain.
Tell us about your network and your app. We'll come back with a point of view on both surfaces.