Design demand-side ads relational tables

Q: Design demand-side ads relational tables

This question evaluates relational data modeling, normalization, key/foreign-key design, and the ability to represent hierarchical advertising entities and attribution join paths.

Q: How do I approach Software Engineering Fundamentals interview questions?

Software Engineering Fundamentals questions require understanding of core concepts and practice. PracHub provides solutions with explanations to help you master software engineering fundamentals interviews.

Question

You are designing the core relational data model for a demand-side advertising system.

Create a normalized schema (tables + key columns + relationships) that supports:

Advertiser owns multiple Campaigns .
A campaign contains multiple Ad Groups (line items).
An ad group contains multiple Ads/Creatives .
Targeting settings (geo, device, audience), budgeting, start/end dates, pacing, and status (active/paused).
Reporting needs: join keys that make it easy to attribute an impression/click back to advertiser/campaign/ad group/ad.

Explain:

Primary keys/foreign keys and cardinalities.
Which fields belong at campaign vs ad group vs ad.
How you would model targeting (as columns vs separate tables).
How you would handle versioning/audit (changes over time).

Design demand-side ads relational tables

Quick Overview

Solution

Comments (0)