Connect playback to advertising evidence.
Connect delivery activity with useful reporting.
Where this work fits
The schedule said what should play. Reporting needed to know what did play, including when a device lost its connection or a prayer interrupted a track. Sending each record immediately was not always possible.
I integrated advertising-related services across content delivery, playback events, and reporting. The work required handling the different contracts for those responsibilities rather than treating the provider integration as a single API call.
Distinguish planned activity from actual playback
Keep the record until delivery succeeds.
Removing a record when sending started could lose it on failure. I retained unsent records on the device and removed the sent batch after success. Monitoring had a related timing problem: it needed to allow for delayed evidence before treating an expected event as missing.
The skills behind the work
- API contracts
- Keep the meaning and format of information consistent between communicating systems.
- Event design
- Represent an action accurately so another part of the product can respond or measure it.
- Validation
- Reject invalid or unsupported input before it affects the rest of the application.
Unsent playback records could survive a restart and travel when connectivity returned. Monitoring made missed activity easier to investigate, with alert outcomes recorded separately from the detection itself.