In the previous sections, we described the core foundations of using Heap. Much of what we described requires some critical steps to be taken in implementation to connect information about your customers so that you can answer the business questions you have today, and others that come up in the future.
Below is a quick view of the implementation checklist, for full documentation, review Setting Up Heap.
✓ Install Heap and confirm that it’s up and running on all domains – once you’ve done so, you can use projects and environments to keep your different data sources organized
❏ Review specification and implementation documents.
❏ Implement identify calls to answer business questions that require user identity data to answer.
❏ Implement server-side events to track events that happen outside of the domains where Heap is running.
❏ Integrate third party integrations like your marketing automation tool, CRM,
payment processor, and more.
❏ Configure your external data warehouse (optional).
❏ Review documentation on data governance, event naming, and categories to make sure your data stays organized.
You’ll likely need to set up some connections with other data sources to pull in data that is not available in Heap. Here are the core and enhanced data connections recommended for SaaS businesses.
Recommended Sources for SaaS
|Enhanced||Customer Success||Web Chat||In-app prompts|
|Enhanced||Marketing automation / Personalization / A/B testing||Business Intelligence||Advertising|
API Specs for User Properties
Here are key user properties that we recommend tracking via addUserProperties API calls so that you can conduct analysis based on user and segment information.
|createdAt||datetime of user registration|
|id||unique universal id|
|user’s email address|
Manual Events & Event Properties
Manual events can be configured to augment the Heap autocaptured event data. We previously suggested two core events for SaaS that should be tracked manually. Here is the recommended implementation of those events.
Recommended Manual Events for SaaS Companies
|Event||Event Trigger||Properties||Identify Call?||Domains|
|Core||Created Account||Triggered when a user successfully creates an account with a unique user ID.||appType|
|Core||Started Membership||Triggered when user successfully completes all steps to start or begin a purchase/product/policy or otherwise purchase a product/subscription/plan.||membershipId|
|Core||Purchased||Triggered when the payment has been processed and funds have been transferred.||transactionId|
|Core||Logged In||Triggered when a user logs into their account.||id||yes||Server|
|Core||Logged Out||Triggered when a user logs out of their account.||id||yes||Server|
|Enhanced||Started Trial||Triggered when a trial is|
|Enhanced||Ended Trial||Triggered when a user cancels their free trial and does not convert to a paid membership.||trialStartDate|
|Enhanced||Renewed Membership||Triggered when user successfully completes a renewal of an existing purchase/product/policy or otherwise purchases another term of their product/subscription/plan.||membershipId|
There are plenty of tools and best practices to keep your data clean and organized in Heap.
Three Common Options for Data Governance Policies:
- Locked Down: Only one or limited team members can author or change events and
definitions for all others to use.
- Team Leader Approach: Each team using Heap has a reviewer to approve and
validate all new shared events. (Recommended)
- Liberal: Allow broader team members to work freely in Heap.
Learn more about how to use our data governance features for management, control, and monitoring by reviewing our Data Governance guide.