Heap Connect lets you directly access your Heap data in BigQuery. You can run ad-hoc analyses, connect to BI tools such as Tableau, or join the raw Heap data with your own internal data sources.
Best of all, we automatically keep the SQL data up-to-date and optimize its performance for you. Define an event within the Heap interface, and in just a few hours, you’ll be able to query it retroactively in a clean SQL format.
In order to start accessing Heap Connect data through BigQuery, you’ll require an existing Google Cloud project. After some initial setup of your project, all that needs to be done is to add our Heap service account as a BigQuery user, and share your Project ID with us. All of these steps are detailed below.
Before starting the Heap Connect BigQuery connection process, you’ll need to:
- Have a Google Cloud Platform (GCP) project. If you don’t already have a project created, you can learn how to do so here.
- Enable billing in the GCP project. If you haven’t already done so, you can follow instructions available here.
- Enable the BigQuery API. If you haven’t already done so, you can begin the process here.
- Know the region you want to use (see Supported Regions)
- Decide on a name for your dataset (optional, default is project_environment)
These three prerequisites are also outlined in GCP’s quick-start guide.
Once you’ve completed the prerequisites, to connect Heap to BigQuery, proceed as follows:
1. Authorize Heap access to BigQuery
Within the GCP dashboard for your selected project, please visit
IAM & admin settings and click
In the subsequent view, add
email@example.com as a
BigQuery User and save the new permission.
We would prefer to be added as a BigQuery user per the steps above. At minimum, we need to be assigned to a dataEditor role, and additionally, have permissions for bigquery.jobs.create. See BigQuery’s access control doc to learn more about the different roles in BigQuery, and see this StackOverflow response for steps to grant individual permissions to create a custom IAM role for Heap.
2. Provide Heap Your GCP Project ID
Once the GCP project is configured, you’ll need to provide your Heap account team with your
Project ID. You can find the
Project ID within
Project info on your GCP project dashboard (make sure you’re in the correct project). In the screenshot below, our project ID is
That’s it! Your Heap account team will follow up once the initial connection has been made. Please don’t hesitate to reach out your account team or firstname.lastname@example.org with any questions.
You can learn about how the data will be structured upon sync by viewing our docs on data syncing.
Duplicate ‘Raw’ Tables
Each of the tables (except for
all_events) is backed by a “raw” table with the name
<view_name>_raw. This means that every environment will have both a
users view and
users_raw table, for example. The views perform deduplication, as the underlying raw tables may have duplicated data introduced during the sync process.
Additionally, the users view filters out users that are from the user in an identify call. For that reason, we recommend querying only against the deduplicated views.
User migrations are not automatically applied. user_migrations is a fully materialized mapping of from_user_ids to to_user_ids. Downstream consumers are responsible for joining this with events/users tables downstream to resolve identity retroactively. For complete steps, see Identity Resolution.