kingtommy dot com

PushNetwork data model

Work project · Table and column names are from the production schema

PushNetwork is the ad network's publisher dashboard and API. This slice of its MariaDB schema covers who a property belongs to, what it earned from each demand source, and how creatives and offers perform.

overall_properties is the publisher site list: one row per user and property, with the site code, the PushPros pd_id, and a JSON config. Views join it to users on user_id, and users.role points at roles.

revenue_daily_property is the main reporting table: one row per property, revenue source and day, with revenue, the client's share (revenue_client) and the revshare applied. Its owner_id joins to users.

revenue_sources lists the demand partners and holds their optimization controls: weight, multiplier, priority and auto_optimized. creative_performance_daily records impressions, clicks and revenue per creative and offer, and hasoffers_offers keeps the offer records from the HasOffers affiliate platform.

As in PushProsRev, there are no foreign-key constraints, so solid lines are joins the code makes and dashed lines are shared keys. The full schema has 213 tables and 55 views. This is seven tables.

Entity diagram of seven PushNetwork tables. users links to roles and to overall_properties, the publisher site list. revenue_daily_property holds daily revenue per property and revenue source and joins to users through owner_id. revenue_sources, creative_performance_daily and hasoffers_offers cover demand partners, creative performance and offers.
Seven tables from PushNetwork. Select to enlarge.

All demos