User’s guide to Growhold
Growhold's user tracking API endpoint can provide you several different use cases:
- Track user's activities inside your app. This is the most typical use case: Within the first event you might send as much information much as possible, such as user's business name, company size, trial plan details, user preferences etc. And then during subsequent tracking events you might simply track user's actions, such as "page view" or "user invited".
- Collect signups from web forms to automate actions. Whenever new users sign up to your services, they probably fill out a web form with details such as full name and email address. These details can be sent to Growhold directly from the form and then utilized in automation: For example send a "thank you" letter to user, assign "a demo call" task to your sales team and determine lead scoring based on user's properties.
- Sync customer details when new information is available. Instead of tracking new events, you might also just update user's profile in Growhold database. For example if user changes email address, provides a new company name or perhaps closes the account, all these can be sent to Growhold with the same tracking endpoint.
- Track anonymous website visitors. Growhold can create an anonymous profile for each visitor. This profile can later transform into identified user profile when visitor signs up to your service. Anonymous tracking can provide statistical data as well as use behaviour data to your other systems as well as for Growhold's automation features.
Data integrity requires some special attention:
- User and account identifiers can be defined by your developers. Keep these always unique and in sync across all systems that you connect to Growhold. Growhold can memorize different ids that are given to users or accounts, but your developers need to make sure that these ids are always unique and given whenever calling Growhold user tracking endpoint.
- Growhold user tracking adds new users in the order that users are seen, unless you decide to push all users in at once. When connecting your app, you might want to use account-source field to define who are your existing users and who are new signups applied for newly built Growhold processes. For example account-source='new-signup-process' can be useful in segmentation queries to separate your new signups from the old users.
- Billing and user tracking sync tries to match with primary user's email address if no other account-id is given. In most of the cases user's email address is enough to identify the connection between billing and user tracking. You may also use for example Stripe metadata to define an account-id which is then mapped to Growhold account-id. These can be selected when connecting Growhold with Stripe or other billing solutions.
User’s guide to Growhold