Heap.io

This page describes how to use Census with Heap.io

Getting Started

‌In this guide, we will show you how to connect Heap.io to Census and create your first sync.

Prerequisites

Have your Census account ready. If you need one, create a Free Trial Census account now.
Have your Heap.io account ready.
Have the proper credentials to access to your data source. See our docs for each supported data source for further information:

1. Get Your App ID from Heap.io

Census needs only one piece of information to connect you to your Heap.io instance:

Your Heap.io app ID. This can be found in the Account settings section under Privacy & Security, and it will be in the Use the API tab.

2. Create the Census Connection

Now that we have the app ID from Heap.io, we can now set up Heap.io as a Destination in Census.

In the Destinations tab of Census, create a new Heap.io Destination.
You can provide whatever name you like.
Provide the app ID from Heap.io.
Save.

3. Create your Model

Navigate to the Model section of our Dashboard

Here you can write a SQL query to select the data you want to see in Heap.io, or you can use a model from a dbt project or a Looker Look. Here are some ideas of data you could select

The Lifetime Value of a customer
The end date of a user's trial
The date a user became active in your product
The number of key activities a user did in your app in the last 7/30 days

Once you have created your model, click save.

4. Create your first Sync

Now head to the Sync page and click the Add Sync button

In the "What data do you want to sync?" section.

For the Connection, select the data warehouse you've already connected (See Prerequisites).
For the Source, select the model you created in step 3.

Next up is the "Where do you want to sync data to?" section.

Pick the Heap.io connection you created in step 3.
For Object, Select Account, User, or Event.

For the "How should changes to the source be synced?" section.

For Account and User select Update or Create or select Send for an Event sync

For the "How are source and destination records matched?" section.

Pick the mapping key; for syncs to the User object the identifier is Identity, for the Account object the identifier is Account Id, and the Event object can use any unique field from your source as an identifier.
Select the field from your model you want as the identifier.

Finally, select the fields you want to update in the Mapper in the "Which Fields should be updated?" section. Here simply map the field from your Heap.io instance to the column from your model.

Click the Next button to see the final preview, which will have a recap of what will happen when you start the sync.