Advertising controls & downstream synchronization
DSP Delivery Controls
Advertiser and campaign controls for when, where and how often ads can be delivered.
Business problem
The challenge
Delivery restrictions needed to remain consistent across inherited settings, customer changes and downstream buying services.
Technical solution
Our approach
Advanced-settings UI, backend validation and synchronized publisher/daypart/frequency rules.
- 01
Expose useful controls
Built frequency caps, day/week parting, TV-network and publisher-domain exclusions, automated/manual controls, inheritance and role-aware configuration.
- 02
Keep downstream restrictions consistent
Handled timezone/UTC conversion and SHAPI schedule synchronization. Extended publisher-blocklist sync so unblocking one setting preserves overlapping TV-network or Multi-Touch exclusions.
- 03
Support real input formats
Added bulk domain uploads, wildcard/subdomain validation and public-suffix handling; improved network lookup efficiency and removed warehouse-backed UI blocklist dependencies.
Results & impact
Project outcomes
Advertiser and campaign controls for when, where and how often ads can be delivered.
Inherited and explicit restrictions
UI settings and downstream exclusions preserve the same delivery intent.
Validated domain controls
Domain uploads and wildcard rules support practical advertiser workflows.
Visual assets
How the workflow fits together
DSP Delivery Controls
flowchart TD A["Advertiser and campaign settings"] --> B["Validate and merge inheritance"] B --> C["Normalize time and domains"] C --> D["Synchronize restrictions"] D --> E["Delivery services"]
Tech stack
Technology and ownership.
Contributions span Premier UI, GaryQL, SHAPI, shared URL tooling and publisher-blocklist synchronization.