Campaign Manager (formerly DoubleClick Campaign Manager) is a web-based ad management system that advertisers and agencies use to manage creative assets and run ad campaigns.

Delta Lake is an open source storage layer that sits on top of existing data lake file storage, such AWS S3, Azure Data Lake Storage, or HDFS. It uses versioned Apache Parquet files to store data, and a transaction log to keep track of commits, to provide capabilities like ACID transactions, data versioning, and audit history.

Campaign Manager has an API that you can use to get information about advertisers, campaigns, creative assets, and more. For example, to get information about a campaign for a given profile, you would call GET /userprofiles/{profileId}/campaigns/{id}.

Here's an example of the kind of response you might see with a query like the one above.

{
  "kind": "dfareporting#campaign",
  "id": long,
  "idDimensionValue": dimensionValues Resource,
  "accountId": long,
  "subaccountId": long,
  "advertiserId": long,
  "advertiserIdDimensionValue": dimensionValues Resource,
  "advertiserGroupId": long,
  "name": string,
  "archived": boolean,
  "startDate": date,
  "endDate": date,
  "comment": string,
  "billingInvoiceCode": string,
  "audienceSegmentGroups": [
    {
      "id": long,
      "name": string,
      "audienceSegments": [
        {
          "id": long,
          "name": string,
          "allocation": integer
        }
      ]
    }
  ],
  "eventTagOverrides": [
    {
      "id": long,
      "enabled": boolean
    }
  ],
  "clickThroughUrlSuffixProperties": {
    "overrideInheritedSuffix": boolean,
    "clickThroughUrlSuffix": string
  },
  "defaultClickThroughEventTagProperties": {
    "overrideInheritedEventTag": boolean,
    "defaultClickThroughEventTagId": long
  },
  "creativeGroupIds": [
    long
  ],
  "creativeOptimizationConfiguration": {
    "optimizationModel": string,
    "optimizationActivitys": [
      {
        "floodlightActivityId": long,
        "floodlightActivityIdDimensionValue": dimensionValues Resource,
        "weight": integer
      }
    ],
    "id": long,
    "name": string
  },
  "additionalCreativeOptimizationConfigurations": [
    {
      "optimizationModel": string,
      "optimizationActivitys": [
        {
          "floodlightActivityId": long,
          "floodlightActivityIdDimensionValue": dimensionValues Resource,
          "weight": integer
        }
      ],
      "id": long,
      "name": string
    }
  ],
  "lookbackConfiguration": {
    "clickDuration": integer,
    "postImpressionActivitiesDuration": integer
  },
  "createInfo": {
    "time": long
  },
  "lastModifiedInfo": {
    "time": long
  },
  "traffickerEmails": [
    string
  ],
  "externalId": string,
  "nielsenOcrEnabled": boolean,
  "adBlockingConfiguration": {
    "enabled": boolean,
    "overrideClickThroughUrl": boolean,
    "clickThroughUrl": string,
    "creativeBundleId": long
  },
  "defaultLandingPageId": long
}

To create a Delta table, you can use existing Apache Spark SQL code and change the format from parquet, csv, or json to delta. Once you have a Delta table, you can write data into it using Apache Spark's Structured Streaming API. The Delta Lake transaction log guarantees exactly-once processing, even when there are other streams or batch queries running concurrently against the table. By default, streams run in append mode, which adds new records to the table. Databricks provides quickstart documentation that explains the whole process.

Now what? You've built a script that pulls data from the Campaign Manager API and loads it into your data warehouse, but what happens tomorrow when you have new data?

The key is to build your script in such a way that it can identify incremental updates to your data. Thankfully, many of the API results include fields like createInfo that allow you to identify records that are new since your last update (or since the newest record you've copied). Once you've take new data into account, you can set your script up as a cron job or continuous loop to keep pulling down new data as it appears.

Delta Lake on Databricks is great, but sometimes you need to optimize for different things when you're choosing a data warehouse. Some folks choose to go with Amazon Redshift, Google BigQuery, PostgreSQL, or Snowflake, which are RDBMSes that use similar SQL syntax, or Panoply, which works with Redshift instances. Others choose a data lake, like Amazon S3. If you're interested in seeing the relevant steps for loading data into one of these platforms, check out To Redshift, To BigQuery, To Postgres, To Snowflake, To Panoply, and To S3.