Configure Estimated Play Analytics for Legacy Systems¶
Estimated Play Analytics helps you approximate campaign playback on legacy player systems that do not provide real-time proof-of-play (POP) reporting into Lucit.
This guide is based on: - Configuring "Estimated Play" Analytics for Legacy Systems
When to Use This¶
Use this feature when your campaign is running on a legacy integration where Lucit cannot receive full real-time playback telemetry.
Common examples: - Watchfire Ignite / Ignite OP - Blip Player
If you are scheduling on those systems, review these integration guides first: - How to Schedule Lucit Campaigns in Watchfire Ignite - How to Schedule Lucit Campaigns in Blip Player
For feature-level context, see: - Lucit vs Watchfire Ignite - Lucit vs Blip
Important Notes Before You Start¶
- Estimated play reporting is a best-effort estimate, not final proof-of-play.
- Lucit estimates likely playback using your configured daily play volume plus player request signals.
- For final reconciliation, always pull official playback reports directly from your player platform.
Prerequisites¶
Before enabling estimated analytics, make sure you have: - Access to the account that owns the campaign - A campaign already scheduled on a supported legacy player - A realistic estimate of total daily plays for that campaign
Step-by-Step: Enable Estimated Play Stats¶
- In Lucit, open the account that contains the target campaign.
- Go to Campaigns and click the campaign.
- Click the 3-dots menu in the upper-right corner.
- Click Settings.
- Enable Estimate Play Stats from Daily Average Plays.
- Set Estimated Total Plays Per Day to your expected daily play count.
- Save settings.
What Happens Next¶
- Allow roughly 10 to 15 minutes for analytics to begin populating.
- In campaign/home analytics views, you should see reporting values marked as Estimated.
Choosing a Good Daily Estimate¶
Use the most defensible baseline you can get: - Historical average daily plays from the player platform - Contracted or scheduled play goals for the campaign - Screen-level traffic weighting if the campaign spans multiple boards
If delivery patterns change, update Estimated Total Plays Per Day so estimated analytics stay aligned with real-world behavior.
Validation Checklist¶
After enabling the feature, confirm: - Campaign is active and linked correctly to the legacy player - Daily estimate is not zero and is in a realistic range - Estimated metrics appear after the 10 to 15 minute sync window - Numbers trend in the expected direction day-over-day
Troubleshooting¶
No estimated metrics appearing - Confirm the campaign is active and actually receiving player requests - Re-check that Estimate Play Stats from Daily Average Plays is enabled - Confirm Estimated Total Plays Per Day was saved - Wait the full 15 minutes before re-checking
Estimated numbers seem too high or too low - Recalculate the daily estimate from a longer historical window - Separate very different inventory types into different campaigns if possible - Adjust the estimate and monitor for 24 to 48 hours