Google Campaign Manager to Metabase

This page provides you with instructions on how to extract data from Google Campaign Manager and analyze it in Metabase. (If the mechanics of extracting data from Google Campaign Manager seem too complex or difficult to maintain, check out Stitch, which can do all the heavy lifting for you in just a few clicks.)

What is Campaign Manager?

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.

What is Metabase?

Metabase provides a visual query builder that lets users generate simple charts and dashboards, and supports SQL for gathering data for more complex business intelligence visualizations. It runs as a JAR file, and its developers make it available in a Docker container and on Heroku and AWS. Metabase is free of cost and open source, licensed under the AGPL.

Getting data out of Campaign Manager

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}.

Sample Campaign Manager data

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
}

Loading data into Metabase

Metabase works with data in databases; you can't use it as a front end for a SaaS application without replicating the data to a data warehouse first. Out of the box Metabase supports 15 database sources, and you can download 10 additional third-party database drivers, or write your own. Once you specify the source, you must specify a host name and port, database name, and username and password to get access to the data.

Using data in Metabase

Metabase supports three kinds of queries: simple, custom, and SQL. Users create simple queries entirely through a visual drag-and-drop interface. Custom queries use a notebook-style editor that lets users select, filter, summarize, and otherwise customize the presentation of the data. The SQL editor lets users type or paste in SQL queries.

Keeping Campaign Manager data up to date

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.

From Google Campaign Manager to your data warehouse: An easier solution

As mentioned earlier, the best practice for analyzing Google Campaign Manager data in Metabase is to store that data inside a data warehousing platform alongside data from your other databases and third-party sources. You can find instructions for doing these extractions for leading warehouses on our sister sites Google Campaign Manager to Redshift, Google Campaign Manager to BigQuery, Google Campaign Manager to Azure Synapse Analytics, Google Campaign Manager to PostgreSQL, Google Campaign Manager to Panoply, and Google Campaign Manager to Snowflake.

Easier yet, however, is using a solution that does all that work for you. Products like Stitch were built to move data automatically, making it easy to integrate Google Campaign Manager with Metabase. With just a few clicks, Stitch starts extracting your Google Campaign Manager data, structuring it in a way that's optimized for analysis, and inserting that data into a data warehouse that can be easily accessed and analyzed by Metabase.