Facebook Ads are ads served up to Facebook users based on their activity, demographic information, device use information, advertising and marketing partner-supplied information, and off-Facebook activity. The platform includes reporting tools that let you see what impact your ads have.

Panoply provides a managed data warehouse platform that lets users quickly set up a new Amazon Redshift instance. It uses machine learning algorithms to handle complex tasks like schema building, data mining, modeling, scaling, performance tuning, security, and backup. Panoply can import data with no schema, no modeling, and no configuration, and you can work with the analysis, SQL, and visualization tools you already know on data in Panoply just as you would if you were creating a Redshift data warehouse manually.

Data can be retrieved programmatically via the Facebook Ads Insights API, which is available to anyone who uses the platform. Don't confuse this with the API Facebook offers for placing and managing ads, which is not relevant to our purposes.

By following the process in the API documentation, you can make calls to the Ads Insights API to retrieve your data. You'll have access to endpoints such as impressions, clickthrough rates, and CPC, all broken out by time period.

Below is an example of what that response might look like when you query the Ads Insights API.

{
   "data": [
      {
         "impressions": "1862555",
         "adset_name": "My ad set",
         "cost_per_action_type": [
            {
               "action_carousel_card_name": "My Carousel Card 1",
               "action_type": "app_custom_event.fb_mobile_activate_app",
               "value": 0.093347346315861
            },
            {
               "action_carousel_card_name": "My Carousel Card 2",
               "action_type": "app_custom_event.fb_mobile_activate_app",
               "value": 0.38324089579301
            },
            ...
         ],
      }
   ]
}

Once you've identified the columns you want to insert, you can use Redshift's CREATE TABLE statement to define a table to receive all of the data.

With a table built, you might be tempted to migrate your data (especially if there isn't much of it) by using INSERT statements to add data to your Redshift table row by row. Not so fast! Redshift isn't optimized for inserting data one row at a time. If you have a high volume of data to be inserted, you should load the data into Amazon S3 and use the COPY command to load it into Redshift.

At this point you've coded up a script or written a program to get the data you want and successfully moved it into your data warehouse. But how will you load new or updated data? It's not a good idea to replicate all of your data each time you have updated records. That process would be painfully slow and resource-intensive.

Instead, identify key fields that your script can use to bookmark its progression through the data and use to pick up where it left off as it looks for updated data. Auto-incrementing fields such as updated_at or created_at work best for this. When you've built in this functionality, you can set up your script as a cron job or continuous loop to get new data as it appears in Facebook Ads.

And remember, as with any code, once you write it, you have to maintain it. If Facebook modifies its API, or the API sends a field with a datatype your code doesn't recognize, you may have to modify the script. If your users want slightly different information, you definitely will have to.

Panoply 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, Snowflake, or Microsoft Azure Synapse Analytics, which are RDBMSes that use similar SQL syntax. Others choose a data lake, like Amazon S3 or Delta Lake on Databricks. 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 Azure SQL Data Warehouse, To S3, and To Delta Lake.