PushNetwork, publicly the Aimtell Offer Network, delivered ads to push subscribers across advertiser networks and reported the results to publishers. This is how the pieces fit.
Delivery. A publisher's site asks get.pushnetwork.com/api/content for an ad, passing the site and the Aimtell subscriber id. The delivery service, the get-ad-content repository, scores each request against per-property decision trees held in memory, loaded from configuration files in S3, and fails over across advertisers. At peak it handled over half a billion ad impressions a day across nine advertiser networks.
Data. Delivery data lands in MariaDB. pushnetwork-helper runs scheduled jobs every minute, five minutes, hour and day that aggregate it into read-optimized tables, and an eRPM-driven weight optimization reallocated traffic hourly across about 27 demand partners. The helper also publishes about 30 JSON configuration files to S3 for delivery to load. The pipelines have their own page: the ETL pipeline.
Reporting. The dashboard is a React 16 app on a Node.js 14 and Express API. The API reads the aggregates, authenticates with JWTs, pushes notifications over socket.io, reads impression records from DynamoDB, stores uploaded images in S3, and sends email through SES SMTP, Postmark, Gmail and AWeber.
It all ran on AWS: Elastic Beanstalk, EC2, S3 and Lambda.