With the growth of your data and business, so does the complexity involved in traditional approaches and architecture. Snowflake and Fivetran have partnered to bring you the Data Cloud and the most automated data integration solution which helps customers simplify data pipelines for all your businesses so you can focus on your data and analytics instead of infrastructure management and maintenance. In this virtual hands-on lab, you will follow a step-by-step guide to perform marketing analytics for Google Ads data by using Fivetran, Snowflake, and dbt. Let's get started.

Prerequisites

To participate in the virtual hands-on lab, attendees need the following:

Sample Google Ads data will be provided if you do not have a Google Ads account.

What You'll Need During the Lab

What You'll Learn

What You'll Build

  1. Login to your Snowflake trial account.
    Snowflake Log In Screen
  2. UI Tour (SE will walk through this live). For post-workshop participants, click here for a quick tour of the UI.
    Snowflake Worksheets
  3. Let's change our role and enable notifications. We need to work in the ACCOUNTADMIN role for this lab and notifications are how Snowflake will alert you when resource monitor thresholds have been crossed. Click on your User Name in the upper right-hand corner.
  4. You'll get a popup with 4 items; click on Switch Role.
  5. Select ACCOUNTADMIN.
  6. The UI will refresh and you should see ACCOUNTADMIN under your username. If you don't, go back to step 5.
  7. Click on your username again and you'll get the same popup with 4 items; click on Preferences.
  8. Click on Notifications.
    Preferences - step 2
  9. Select All, which will send notifications to your email address and this UI (in the Notifications tile in the upper right).
    Preferences - step 3
  10. Now let's create your Fivetran account. Click on the Partner Connect tile at the top of the UI...
  11. ...and then click on the Fivetran tile inside Snowflake Partner Connect. (if you aren't in the ACCOUNTADMIN role you'll receive a warning. Go back and complete steps 6-9.)
    Create Fivetran Account - step 2
  12. Click on Connect.
    Create Fivetran Account - step 2
  13. Click on Activate in the pop-up that appears. This will open a new browser tab and take you to Fivetran where you will enter a password for the trial account. Create Fivetran Account - step 3

In the next three sections we will create an automated data pipeline, with an extract-load (ELT) architecture::

  1. Extract and Load:
    • Complete Fivetran Account Setup
    • Upload Sample Adwords Data using the Fivetran Google Sheets Connector
  2. Transform:
    • Create our first dbt project
    • Setup Fivetran dbt Transformations

Let's get started!

Complete Fivetran Account Setup

  1. Create a password.
    Fivetran - Password
  2. That is it! Hang out on this screen until the next section. To log into Fivetran in the future, you can navigate to https://fivetran.com/dashboard. Your email is the same as your Snowflake email (at the time you connected with Partner Connect) and your password is whatever you entered in Step 1 of this section. Fivetran - Source

Note: The Setup Fivetran dbt Transformations section assumes you have uploaded the sample data as outlined in this section. If you used your own Google Ads data, that is fine; you will just need to edit the dbt_project.yml file as discussed in the next section.

For your convenience we have included sample Google Adwords data in the form of a Google Sheets containing three workbooks. Each workbook corresponds to a table to be synced to the Snowflake warehouse. This gives us the opportunity to explore another Fivetran feature, the Google Sheets connector. Google Sheets is, in fact, the most popular connector used by Fivetran customers. In the next section, we will:

  1. Google Sheets is the first connector in the list! Click on Google Sheets. Fivetran - Source2
  2. You should see this screen.
    Fivetran - Google Sheet
  3. Please use the following values for the two fields:
    • Destination schema: google_ads_demo
    • Destination table: final_url_performanceFivetran - Google Sheet2
  4. Scroll down the page a bit, and paste the URL you just copied into the Sheet URL field. (Follow these instructions to get a Google Sheets URL) Then, click the FIND SHEET button. This step will take a few moments. Fivetran - Google Sheet3
  5. In the Named Range field, choose final_url_performance. Fivetran - Google Sheet4
  6. Click SAVE & TEST. Fivetran - Google Sheet5
  7. When you see All connection tests passed!, click the VIEW CONNECTOR button. Fivetran - Google Sheet6
  8. Click Start Initial Sync. This will start the data sync into the warehouse! Now any updates to these sheets will be automatically synced to Snowflake. Fivetran - Google Sheet7
  9. Great! The Google Sheets connector is now syncing. Let's setup the next table. Click the Connectors menu.
    Fivetran - Google Sheet8
  10. Click the + Connector button.
    Fivetran - Google Sheet9
  11. Please use the following values for the two fields:
    • Destination schema: google_ads_demo
    • Destination table: criteria_performanceFivetran - Google Sheet10
  12. Scroll down the page a bit, and paste the URL you just copied into the Sheet URL field. (Use the same Sheets URL as step 4, or follow these instructions to get a new Google Sheets URL.) Then, click the FIND SHEET button. This step will take a few moments. Fivetran - Google Sheet11
  13. In the Named Range field, choose criteria_performance. Click SAVE & TEST. Fivetran - Google Sheet12
  14. When the connection tests complete, click VIEW CONNECTOR. Fivetran - Google Sheet13
  15. Click Start Initial Sync. Then click Connectors on the left-hand menu. Fivetran - Google Sheet14
  16. Click + Connector.
    Fivetran - Google Sheet15
  17. Please use the following values for the two fields:
    • Destination schema: google_ads_demo
    • Destination table: click_performanceFivetran - Google Sheet16
  18. Scroll down the page a bit, and paste the URL you just copied into the Sheet URL field. (Use the same Sheets URL as step 4, or follow these instructions to get a new Google Sheets URL.) Then, click the FIND SHEET button. This step will take a few moments.
    Fivetran - Google Sheet17
  19. In the Named Range field, choose click_performance. Click SAVE & TEST.
    Fivetran - Google Sheet18
  20. When the connection tests complete, click VIEW CONNECTOR.
    Fivetran - Google Sheet19
  21. Click Start Initial Sync. Then click Connectors on the left-hand menu.
    Fivetran - Google Sheet20
  22. Congratulations! You can see your 3 Google Sheets connectors running, each creating one of our three sample data tables. Click on Google Sheets (3).
    Fivetran - Google Sheet21

This view shows you all of your Google Sheets connectors. Some of your connectors may still be syncing, that is fine; we will have time for them to complete while we perform the next part of the lab.
Fivetran - Google Sheet22

In Snowflake (optional): When the sync is complete, you can see your schema and tables in Snowflake's Worksheet view. You should be able to see the data in the tables by clicking into the PC_FIVETRAN_DB database, into the GOOGLE_ADS_DEMO schema, then clicking on one of the tables and then clicking Preview Data.

Note: The Setup Fivetran dbt Transformations section assumes you have uploaded the sample data as outlined in the previous section. If you use your own Google Ads data, that is fine; you will just need to edit the dbt_project.yml file as discussed in this section.

For your convenience, we have created a sample dbt Github project that is already configured to work with Fivetran's dbt_google_ads_source and dbt_google_ads packages. You can find the sample repository at the following link: https://github.com/fivetran/snowflake_fivetran_vhol

This section assumes that you have created a Github account and are logged into that account. In this section we are going to:

When you click https://github.com/fivetran/snowflake_fivetran_vhol and you are logged in, you should see the following screen. Notice the user / owner is fivetran and the repository is named snowflake_fivetran_vhol.

  1. On the upper right (but below your user icon) is a Fork button. Click it! Fork repo - 1
  2. If you have access to multiple github accounts, you will have the option to select into which account to fork this repository. Choose your personal user account.
    Fork repo - 2

That's it! Notice in the screenshot above the user / owner is crw and the repository is (still) named snowflake_fivetran_vhol - but now that repository is under your personal Github account. I can now manipulate this repository however I like, without impacting the sample repository. Fork repo - 3

Congrats! You have successfully created your first dbt project! That was easy! The next section is OPTIONAL and not required for the workshop. It is included for your information only.

There are three very important configuration files to be aware, all at the top level of the file tree.

dbt_project.yml: Fork repo - 4
Various configuration settings are found in this file. Please see dbt's documentation for more information on these settings.

packages.yml:
This is where you can include outside packages to run! See hub.getdbt.com for a complete list and installation instructions. As of this writing, Fivetran has created over 17 packages, including packages for Netsuite, Salesforce, Twitter Ads, Marketo, Zendesk, Mailchimp, and more! Fork repo - 5

deployment.yml:
This is a Fivetran-specific file that configures what jobs will run when, leveraging a crontab-style syntax for scheduling. Documentation can be found in the file itself. Remember, as described above, you can edit files directly in Github!

In this section we will take the dbt project we created in the previous section, and run it via Fivetran to generate models! We will be showing how Fivetran is used to orchestrate dbt jobs, and the first step is to connect to your dbt project in Github. There are a lot of steps in this section, but for the most part they are not too complicated. Let's get started!

Note: dbt Transformations in Fivetran are in beta as of this writing. Depending how you signed up for your Fivetran trial, you may or may not see the option to "Try dbt Transformations". If you do not see this option, please reach out to us and we will try to get you enabled to try this feature.

If you see this screen, please reach out to Fivetran sales – we can enable dbt Transformations beta for your account.
Transformations - 1

  1. If you have not already, switch back to your Fivetran tab in your web browser. First click on the Transformations section of your Fivetran interface. You should see the following interface. We will be clicking the button labeled Try dbt Transformations. Transformations - 2
  2. Click Enable dbt TransformationsTransformations - 3
  3. Click I am ready to connect my Git repo. Transformations - 4
  4. Now we will configure the connection to Github. Next to Public Key, click Copy to Clipboard (the papers icon). Transformations - 5
  5. On the Github repository we created above (your_username/snowflake_fivetran_vhol) click on Settings (farthest-right of the tabs under the repository name.) Transformations - 6
  6. On the left-hand navigation, click on Deploy Keys (lower half, under Integrations, above Secrets). Transformations - 7
  7. Click Add deploy key, on the mid-upper-right hand side of the screen. Transformations - 8
  8. Give the deploy key a memorable, distinct title, like Fivetran dbt access. Paste the previously-copied deploy key in the Key field. DO NOT check "Allow write access" - currently Fivetran only requires read access to the repository. Click Add keyTransformations - 9
    Phew! Done! If at any time you want to revoke Fivetran's access to this repository, come back to this screen and delete the deploy key we just created.
  9. Before leaving Github, return to the Code tab. Transformations - 10
  10. Now click the green Code button. Make sure the SSH tab is selected, and copy the: git@github.com:your_username/snowflake_fivetran_vhol.git URL. We will need it on the next step. Note: it is safe to ignore errors about not having an SSH key configured here. The Deploy Key we configured will give Fivetran access to this repository. Transformations - 10
  11. Paste the value into the Repository URL field. Transformations - 10
  12. For Default Schema Name field, enter GOOGLE_ADS_DBTTransformations - 10 As of this writing, you need to perform the next actions to continue. Note: Github has changed their default branch name to "main". This change was made very recently, and Fivetran has not yet caught up to the new naming convention. For the time being, for this guide, we will need to manually change the branch name.
  13. Click Show Advanced Options. Transformations - 10
  14. Change the Git branch field's value to main.
    Transformations - 10
  15. Click SAVE. Then when you see the green success message, click TRANSFORMATIONS. Transformations - 10
  16. That's it! Your dbt project is now configured to run and be orchestrated with Fivetran. In the upper right corner, there is a toggle switch, Activate dbt Transformations. Click this switch to start your transformations running. Transformations - 10
  17. Now if left to their own devices, your transformations will run on the schedules listed below. As a reminder, these schedules are configured in the deployment.yml file, as discussed in the previous section. But let's run one right away! Click on the weekdays line item.
    Transformations - 10
  18. In the upper right corner, click Run now (the circular arrow icon.) Transformations - 10
  19. The dbt job runs successfully! Click on the line item with the green checkmark next to it. Transformations - 10
  20. Here we can see the results of running the dbt job. Click on the down arrow (caret) next to run models. Transformations - 10

This exposes the results of running the dbt job. If you scroll to the bottom of the page, you can see the job ran successfully. Transformations - 10

Congratulations! You have successfully run your first dbt job!

In Snowflake (optional): We can see the results of all of this hard work in the Snowflake Worksheets view. On the left hand column, you can see the GOOGLE_ADS_DBT schema which has the results of running our dbt job: fresh models, produced simply by including Fivetran's open source dbt_google_ads package! We are that much closer to exposing the true value of this data!

The tables created by these models do the following:

Did You Know? All of the code that produces these models is open source! Fivetran officially supports over 20 open source dbt packages that model data delivered by Fivetran, typically to provide commonly required aggregations. You can see all of the available packages at https://hub.getdbt.com/ - scroll down to the Fivetran section.

The two packages we use in this lab are the Google Ads packages: google_ads_source source code on githubgoogle_ads source code on github

You can save considerable development time by leveraging Fivetran's open source dbt packages with data delivered by Fivetran. Now that you have a running dbt project, feel free to try including more packages!

The summary so far: Maintenance-free data pipelines and powerful in-warehouse transformations

In the previous sections, we learned the following skills:

In doing so, we have set up a complete, end-to-end modern data pipeline focusing on the advantages of the Extract-Load-Transform (ELT) architectural approach. Data loading is extremely simple to configure and comes with the benefit of hands-free maintenance, forever. dbt is a powerful transformation tool that comes with many open source Fivetran modeling packages out-of-the-box. Moreover, Fivetran manages the execution of those transformation jobs, and the jobs run natively in the Snowflake warehouse, exposing all of the pßower of Snowflake's query engine to your transformations.

  1. Back in the Snowflake UI, let's take a quick look at the query history to see all the work that Fivetran/dbt performed.
    Snowflake Part 2 - 1
  2. Click on Add a filter.
    Snowflake Part 2 - 2
  3. Change the left box to User and select PC_FIVETRAN_USER in the right box. All of the Fivetran/dbt queries executed as this user.
    Snowflake Part 2 - 3
  4. In the table below you can see all of these queries. Scroll down. Click on a SQL Text value and you'll see a pop-up of the specific SQL statement. You can read about this UI screen here.
    Snowflake Part 2 - 4
  5. Click on the Worksheets tile at the top. Snowflake Part 2 - 5
  6. Your screen will look like this. This is where we will do most of our remaining work. Snowflake Part 2 - 6
  7. Now load the script (vhol_script.sql) by clicking on the button and then selecting in the pop-up. Navigate your computer and find the script. Snowflake Part 2 - 7
  8. The script should appear in your worksheet like this. Snowflake Part 2 - 8
  9. Notice on the left-hand side is a database browser with a database called PC_FIVETRAN_DB. This is the database that you loaded with Fivetran. Click on it and you will see the schemas. GOOGLE_ADS_DEMO is where the data initially loaded and GOOGLE_ADS_DBT is the schema created by the dbt process. Click on GOOGLE_ADS_DBT and you'll see the tables and views that live within. Snowflake Part 2 - 9
  10. Let's start our work performing DBA functions. We need to set the context we want to use within the worksheet. In each worksheet I can have a different role, warehouse, database, and schema. Each worksheet is independent of the others (like Snowflake compute!). My worksheet role can also be different from the role I have in the upper right-hand corner under my name.

    Let's execute the SQL in script section A to set our worksheet context. To do so, highlight the two lines (use role..., use schema...) and click the button.

    Pro Tip: You may get a pop-up asking if you want to run both statements. If you don't want this warning every time, click in the check box and click OK.
    /*-----
    --A--
    -----
    --Let's set our worksheet role and db/schema*/
    use role ACCOUNTADMIN;
    use schema PC_FIVETRAN_DB.GOOGLE_ADS_DBT;
    
    Notice that your worksheet context now has a default role, database, and schema but no warehouse (yet).
    Snowflake Part 2 - 11
  11. Let's pretend that the data we loaded and transformed with Fivetran is our production data. We only want it to be changed by our Fivetran process. Since our analysts will want to experiment with and change the data, we'll CLONE the entire PC_FIVETRAN_DB database so they can have their own sandbox. This is a logical copy; it will consume no additional space unless the data in the clone starts to change. This is a fantastic tool for creating as many sandboxes as you need. It also works well for making time-specific snapshots.

    Cloning reduces time to value - full production clones are fast and support more accurate analytical results because they are rich and complete data sets.
  12. Run the Create Database SQL and the Use Schema commands in section B to make a clone, then refresh the database browser with the (small) Refresh button:
    /*-----
    --B--
    -----
    --Make a new DEV db and schema and then clone the 3 key tables for isolated analysis and experimentation*/
    create database GOOGLE_ADS_DEV clone PC_FIVETRAN_DB;
    use schema GOOGLE_ADS_DEV.GOOGLE_ADS_DBT;
    
    Now your analysts have GOOGLE_ADS_DEV - a complete clone of PC_FIVETRAN_DB.
  13. Next we need to create a warehouse (compute) for the analysts. For this workshop we'll create an Extra Small - the smallest unit of Snowflake compute - with an auto suspend time of 2 minutes and auto resume enabled. Auto resume means it will start up when a request is made. Run the SQL in section C to create the warehouse. Notice that this warehouse is now in your worksheet context.
    /*-----
    --C--
    -----
    --Create a virtual warehouse (compute) for the Marketing Analyst team to do their work*/
    create or replace warehouse MKT_ANALYSIS with warehouse_size = 'XSMALL' auto_suspend = 120 --seconds
    auto_resume = TRUE;
    
    Snowflake compute is unique. It's (1) easy to define and manage; (2) fast to activate and suspend; (3) self-suspending; (4) self-healing; (5) isolated from the storage layer; (6) isolated from other compute; (7) quick to scale up/down and out/in; (8) non-disruptive when any of this is happening.
  14. For our last act as DBA we'll create a resource monitor to track warehouse consumption. Resource monitors are convenient tools for setting time-based consumption thresholds on compute at the warehouse or account level. You can set alerts for various thresholds and even prevent a warehouse from running once it reaches a credit value that you set.
    /*-----
    --D--
    -----
    --Create a resource monitor to track credit usage of the marketing virtual warehouse*/
    create or replace RESOURCE MONITOR "MARKETING_ANALYSIS" with CREDIT_QUOTA = 20,
    frequency = 'DAILY',
    start_timestamp = 'IMMEDIATELY',
    end_timestamp = null triggers 
    ON 100 PERCENT DO SUSPEND 
    ON 5 PERCENT do NOTIFY 
    ON 10 PERCENT do NOTIFY 
    ON 50 PERCENT do NOTIFY 
    ON 90 PERCENT do NOTIFY;
    alter WAREHOUSE "MKT_ANALYSIS"
    set RESOURCE_MONITOR = "MARKETING_ANALYSIS";
    
    Run the two SQL statements in section D to create a resource monitor that has a daily 20 credit limit, sends an alert at 5%, 10%, 50%, and 99% thresholds, and suspends the warehouse at 100% (20 credits). The second statement associates the resource monitor to the warehouse.
  15. Now we'll switch to ‘Analyst mode'. In real life this would be a different person with a different userid and a different Role. An analyst might write a query like the one in section E of the script to answer the question "What was the best performing cranberry sauce campaign?" Go ahead and run it. We're working with tiny data sets in the lab but in reality we might run over millions or billions of rows.
    /*-----
    --E--
    -----
    --What was the best performing cranberry sauce campaign?*/
    select ad_group_name,
    campaign_name,
    sum(spend) as TOT_SPEND,
    sum(clicks) as TOT_CLICKS,
    sum(impressions) as TOT_IMPRESSIONS,
    sum(impressions) / sum(spend) as IMPRESSIONS_PER_DOLLAR,
    sum(spend) / sum(clicks) as cost_per_click
    from GOOGLE_ADS__URL_AD_ADAPTER
    where ad_group_name = 'cranberry sauce'
    group by ad_group_name,
    campaign_name
    order by 6 desc;
    
  16. These are interesting results, but you have a hypothesis: clicks increase with snowy weather. Let's go to the Snowflake Data Marketplace and find what we need. The Data Marketplace lives in the new UI called Snowsight (currently in Preview mode but feel free to test drive after the lab). Click on Preview App at the top of the UI. Snowflake Part 2 - 16
  17. Click Sign in to continue. You will need to use the same user and pw that you used to login to your Snowflake account the first time. Snowflake Part 2 - 17
  18. You're now in the new UI - Snowsight. It's pretty cool - with charting and dashboards and context-sensitivity - but today we're just focused on getting to the Data Marketplace. Click on Data... Snowflake Part 2 - 18
  19. ...and then Marketplace...
    Snowflake Part 2 - 19
  20. ...and now you're in! Over 100 providers have made datasets available for you to enrich your data. Today we're going to grab a sample of weather data. Click the Ready to Query checkbox...
    Snowflake Part 2 - 20
  21. And then find the Weather Source tile. Once you find it, click on it.
    Snowflake Part 2 - 21
  22. Here you'll find a description of the data, example queries, and other useful information. Let's get this data into our Snowflake account. You'll be amazed at how fast and easy this is. Click . Snowflake Part 2 - 22
  23. In the pop-up, rename the database to WEATHERSOURCE (important!), check the "I accept..." box and then . No need to add additional roles (though you might in real-life).
    Snowflake Part 2 - 24 What is happening here? Weather Source has granted access to this data from their Snowflake account to yours. You're creating a new database in your account for this data to live - but the best part is that no data is going to move between accounts! When you query you'll really be querying the data that lives in the Weather Source account. If they change the data you'll automatically see those changes. No need to define schemas, move data, or create a data pipeline either. Isn't that slick?
  24. Now click Done. You can close this browser tab and go back to the other Snowflake UI that you started in. Snowflake Part 2 - 25
  25. Refresh the database browser and notice you have a new shared database, ready to query and join with your data. Click on it and you'll see views under the PUBLIC schema. We'll use one of these next.
    Snowflake Part 2 - 26
  26. With production-sized data sets we are likely to have very large tables and complex queries; therefore, we might want to increase the amount of compute we're using to perform this analysis. In Snowflake this is fast and easy. Run the statement in section G. Notice how fast it scales up. No disruption. No shuffling of data. We've changed from an XS (one node cluster) to an XL (16 node cluster) in seconds. Ready to go!
    /*-----
    --G--
    ----- 
    --With production-sized data sets we might want to join and query tables with billions of rows
    --In these cases it's easy and productive to scale up our virtual warehouse so these queries run faster*/
    alter warehouse mkt_analysis set warehouse_size = 'XLARGE';
    
  27. So, let's join that weather data to our Google Ads data and see if there is a correlation between clicks and snowfall. Run the correlation query in section H. Remember that we're actually joining data across two accounts, but the experience and performance is seamless and fast.
    /*-----
    --H--
    -----
    --Is there any correlation between clicks and snowfall for any ad group?*/
    select ad_group_name,
    abs(corr(clicks, w.tot_snowfall_in)) as clicks_snow_corr
    from GOOGLE_ADS__URL_AD_ADAPTER ga,
    "WEATHERSOURCE"."PUBLIC"."HISTORY_DAY" w
    where ga.date_day = w.date_valid_std
    group by 1
    order by 2 desc;
    
    It's a weak correlation so maybe our hypothesis isn't worth exploring further. But our ability to quickly source Marketplace data and mash it with our own data has saved us lots of time and we can iterate further. Snowflake Part 2 - 29
  28. Because this combination may yet have value, let's create a view that combines the correlations with the URL data so others can take a look more easily. Run the SQL in section I. One creates the view and the other queries it.
    /*-----
    --I--
    -----
    --Let's create new view with the correlations built in to the URL_AD_ADAPTER data*/
    create or replace view GOOGLE_ADS__URL_AD_ADAPTER_CORR as (
    with corr as (
      select ad_group_name,
        abs(corr(clicks, w.tot_snowfall_in)) as clicks_snow_corr
      from GOOGLE_ADS__URL_AD_ADAPTER ga,
        "WEATHERSOURCE"."PUBLIC"."HISTORY_DAY" w
      where ga.date_day = w.date_valid_std
      group by 1
    ),
    base as (
      select *
      from GOOGLE_ADS__URL_AD_ADAPTER
    )
    select b.*,
      c.clicks_snow_corr
    from base b,
      corr c
    where b.ad_group_name = c.ad_group_name
    );
    select *
    from GOOGLE_ADS__URL_AD_ADAPTER_CORR;
    
  29. Now that our heavy lifting is done, let's scale down the warehouse size. No need to pay for more compute than we need. Run the SQL in section J.
    /*-----
    --J--
    -----
    --Once we're done with our complex queries we scale the warehouse back down*/
    alter warehouse mkt_analysis set warehouse_size = 'XSMALL';
    
  30. For our last trick let's imagine we've accidentally dropped the table we're working with. No one has ever done that! Run the DROP statement in section K and then refresh the database browser. Notice the table is gone. Now run the UNDROP and refresh. It's back! This is the power of time travel. You can restore lost data for up to 90 days of history.
    /*-----
    --K--
    -----
    --Let's look at one last great feature of Snowflake.  Have you ever accidentally dropped a table?  Or a database?  
    --Let's 'accidentally' drop a table.*/
    drop table GOOGLE_ADS__URL_AD_ADAPTER; 
    /*--Fortunately, in Snowflake, this is an easy fix.*/
    undrop table GOOGLE_ADS__URL_AD_ADAPTER;
    
    Time Travel also enables you to query and replace tables as of a particular point in time or prior to a specific SQL statement.
  31. One last thing. How is our Snowflake consumption looking? It's easy to understand. We'll look in two places. First, you might have a Notification, so click on that tile. When you have notifications enabled and resource monitors built, you'll get notifications.
    Snowflake Part 2 - 32
  32. See anything that looks like this? These notifications come from the resource monitor we set up earlier in the lab. You'll also get emails with the same information.
    Snowflake Part 2 - 33
    Snowflake Part 2 - 33
  33. Now, click on the Account tile.
    Snowflake Part 2 - 34
  34. Then click on Usage.
    Snowflake Part 2 - 35
  35. Here you can see monthly/daily credit usage...
    Snowflake Part 2 - 36
  36. ...and monthly/daily storage usage (you won't see much for storage yet since our data is small). In addition to these screens you can query the Snowflake metadata layer for the same info and build reports in your favorite BI tool.
    Snowflake Part 2 - 37

This concludes the lab. We hope you learned a lot and are interested in exploring Fivetran and Snowflake for your use cases. Please feel free to ask questions.

Congratulations on completing this lab on automating data pipelines to drive marketing analytics! You've mastered the Fivetran and Snowflake basics and are ready to apply these fundamentals to your own data. Be sure to reference this guide if you ever need a refresher.

We encourage you to continue with your free trials by loading your own sample or production data and by using some of the more advanced capabilities of Fivetran and Snowflake not covered in this lab.

Additional Resources:

What we've covered:

Enter a username, email address, and password. Appendix I - 1

Solve the puzzle and continue! Appendix I - 2

You can skip down to the bottom of this screen, or take the time to choose your interests. Appendix I - 3

Choose Complete setup. Appendix I - 4

Head to your email application and verify your email address. Appendix I - 5

That's it! You now have a Github account. Appendix I - 6

  1. Go to https://signup.snowflake.com/.
  2. Enter your personal information. You need to use a valid email address that you can access and haven't used previously. Appendix II - 1
  3. When you sign up for Snowflake it auto-populates to Enterprise. This is the best choice for this lab. Choose the cloud/region closest to you and click the "GET STARTED" button. Appendix II - 2
  4. Your account will provision in 1-2 minutes and you will receive an email activation link like this to create a user. Click on the CLICK TO ACTIVATE link.
    Appendix II - 3
  5. Next, you'll see this page your browser. Specify your username and password. Be sure to store your credentials in a safe location.
    Appendix II - 4
  6. You will be logged in to your new account and it will look like this. You will also receive another email with your username and account URL.
    Appendix II - 5

Congratulations, you are ready to work in Snowflake!

Log into Fivetran and you should see the following screen, which shows our selection of source connectors. Use the type-down or the drop-down menu to find the Google Ads connector. If you have already setup your first connector, you may need to go to the Connectors tab in the Fivetran web application, and choose + Connector.
Appendix III - 1

The Fivetran Google Ads connector setup screen is shown below, before we begin to modify it. On the left are the configuration controls. On the right are inline, helpful setup instructions.
Appendix III - 2

Obtain your customer ID per the instructions on the right.
Appendix III - 3

And enter it in the field on the left. Click AUTHORIZE to sign in to Google.
Appendix III - 4

Choose the account with which you wish to authenticate.
Appendix III - 5

Authorize Fivetran to access your Google Ads data by clicking Allow.
Appendix III - 5

Now we need to configure three reports. These three reports will give us the raw data that we will use to generate our models later. Each report will require:

For each report, we will use Configuration Type: Use Custom Report.

For the first report, use the following configuration:

Appendix III - 7

For the second report, use the following configuration:

Appendix III - 8

For the third report, use the following configuration:

Appendix III - 9

That's it for setting up reports! To review, your connector configuration screen should look like the screen shot below:
Appendix III - 10

Great! Now click SAVE & TEST to save your configuration.
Appendix III - 11

Click CONTINUE to see the next screen, where you can Start Initial Sync to start the data flowing!
Appendix III - 12

Before we start the first sync, let's take a look at the configuration Fivetran provides for connectors. Appendix III - 13

First let's look at the Schema tab. Here, depending on the connector type, you can configure up to three settings:

With Ads connectors, you can enable or disable a particular report from syncing.

Next let's visit the Setup tab. There is one very important configuration tool here, and that is the Sync Frequency. This can be set to as frequently as every 5 minutes, to as infrequently as every 24 hours. Fivetran starts and stops the Snowflake warehouse used for data loading on demand, and is extremely efficient at data loading, so you only pay for the time Fivetran is actually loading data.
Appendix III - 15

OK! That is it! The Schema setup in the Schema tab, and the Sync Frequency setting in the Setup tab are the only configuration details you need to manage, and even those can be left on the defaults for flawless operation! With that visited, let's go back to the Status tab and start the sync!

Once the Start Initial Sync button is clicked, you should see your sync start up.
Appendix III - 16

While the sync is running, we can take a quick detour into the Logs tab. This is a real-time view into the data loading process. Fivetran offers ways to export these logs into your preferred log aggregation service. We even have a free connector called the Fivetran Log connector, that exports log data, schema operation metadata, and Fivetran credit consumption data!
Appendix III - 17

For this demo, I chose to only sync 3 months of historical data, so the initial sync finished relatively quickly at two and a half minutes. When your sync has completed, you will see its status on the timeline, as per below.
Appendix III - 13