Immediately after launching embedded accounting, your product team will
want to track key user activation funnels and optimize against those funnels. If you’d like to set user activation on
auto-drive, you can enable Tight’s Twilio integration, which use smart SMS
messages to handle all onboarding and activation lifecycle messaging.
Activating through timely notifications
With detailed user-level events, Tight gives you the tools to send the right notification at the right time, ensuring
you are helping your users activate as successfully as possible.
Defining the channel
SMS
While many of Tight’s customer-partners already have already established notification channels with their userbase (e.g.
SMS, push notifications, in-app chat, email), customer-partners often find less friction by simply allowing Tight’s
Agentic Accountant to text the business owner the same way a human would
whenever a quick action is needed.
Push Notifications
If you already send out push notifications, you can simply subscribe
to Tight’s lifecycle webhooks, and then use those webhooks to trigger push
notifications to your users. Additionally, if you utilize Intercom for in-app chat and/or push notifications, you can
leverage Tight’s Intercom integration.
Email
If you already send out emails, you can simply subscribe
to Tight’s lifecycle webhooks, and then use those webhooks to trigger
emails. Alternatively, Tight can send out lifecycle emails on your behalf.
Triggering the right notifications
The following events are proven to drive initial user activation:
Linking banks or credit cards
Event: bankLinked
Notification timing: User registered >2 days ago and bankLinked not triggered
Messaging: Link your card to automate your expense tracking
Follow-up actions: transactionCreated, transactionEdited, transactionRuleSuggested
Setting up invoicing
Event: invoiceSetupCompleted
Notification timing: User registered >5 days ago and invoiceSetupCompleted not triggered
Messaging: Customize your invoices and get paid faster
Follow-up actions: invoicePaymentProcessingSetupCompleted, invoiceDrafted, invoiceSent
Tracking user activation funnels
Defining key user activation funnels
There are many different ways to define funnels depending on the goals of your product. Two of the most common examples
are described below:
Expense Tracking Funnel
| Funnel Step | Event | Description |
|---|
| 1 | companyCreated | User registered |
| 2 | bankLinked | User linked their bank or credit card for automated transaction categorization |
| 3 | transactionsProcessed | Transactions have been processed from an integration such as Plaid, Unit, or CSV Import |
| 4 | transactionRuleSuggested | Tight system suggests a rule for automatic expense categorization to the user |
| 5 | transactionRuleAccepted | User accepted an automated expense rule, indicating that they have customized/personalized the app to their needs. User is then rewarded and retained by automatic expense categorization. |
Invoicing Funnel
| Funnel Step | Event | Description |
|---|
| 1 | companyCreated | User registered |
| 2 | invoiceSetupCompleted | User added their company branding, logo, address, etc., to customize their invoice template |
| 3 | invoicePaymentProcessingSetupCompleted | User is now able to accept credit card and ACH payments |
| 4 | invoiceSent | User sent an invoice to their client |
| 5 | invoicePaid | User received payment from their client for an invoice (and is very likely retained) |
Tight’s GTM team is glad to help you define the activation funnels that are most critical to your product.
Tracking user-driven events
In order to receive the important user-driven events for tracking and optimizing user activation, you will want to
subscribe to events via one or more of the following methods:
a. Intercom integration: if your team utilizes Intercom for user support and
messaging
b. Mixpanel integration: if your team utilizes Mixpanel for tracking aggregate user
behavior
c. Lifecycle webhooks: if your team has custom-built user messaging and
behavior tracking flows
d. Data Lakes: if your team has custom-built flows and wants to get
user behavior data into your data scientists’ hands without involving developers 
