Hi Ben\u000a\u000aGreat timing! We have 2 SaaS products straining to burst onto the market in the next month. We are running 14 day trials on both, and see onboarding hand holding to get people in a guided manner to the golden \u0022taddah\u0022 moment of seeing those killer features that they simply cant do without as key.\u000a\u000aWe use stripe, tick, and also chargebee, tick (thanks Appsumo for the startups LTD that at $49 USD gave us 2 years free with Chargebee ($249 USD per month value) and $10000 of offset Stripe fees \u002D best 100% guaranteed investment return EVER!!).\u000a\u000aThis seems almost too good to be true \u002D perfect timing.\u000a\u000aBut \u002D a couple of questions please before I max out: \u002D\u000a\u000a1 \u002D Notice that help on the site comprises a single article on custom events \u002D and this looks like setting up custom code on a specific UI control \u002D is this really all the documentation available? Blod also comprises of 1 article....how well documented is help etc?\u000a2 \u002D Am I correct in assuming the Javascript code is a custom code snippet that can be embedded with Google Tag Manager (if not then rest will need answering, but know we can track all required DOM events using GTM)\u000a3 \u002D We operate a 100% serverless stack, either angular or react (single page applications) both of which of almost entirely client\u002Dside rendered (apart from non\u002Dcore services such as client messaging). Do you support this architecture and will we be able to track all necessary DOM events?\u000a4 \u002D The 1 blog article you have on the site currently is on customer personas. We track subscription type, persona type and role in both our SaaS products. We hold these as depersonalised values that are then made available to GTM (and from there to intercom, segment etc. via the DOM). Can we use this approach also for Onboardflow and if so, can we create logic to trigger unique onboarding tracking and push notifications for users based on these values? Site sort of touches on this, but the closest I can see is \u0022custom properties\u0022 in the Segment, Segment, Segment section on auto\u002Dmessages. What custom properties can we define, and how?\u000a\u000aThanks in advance\u000a\u000aRichard

Question

Hi Ben\u000a\u000aGreat timing! We have 2 SaaS products straining to burst onto the market in the next month. We are running 14 day trials on both, and see onboarding hand holding to get people in a guided manner to the golden \u0022taddah\u0022 moment of seeing those killer features that they simply cant do without as key.\u000a\u000aWe use stripe, tick, and also chargebee, tick (thanks Appsumo for the startups LTD that at $49 USD gave us 2 years free with Chargebee ($249 USD per month value) and $10000 of offset Stripe fees \u002D best 100% guaranteed investment return EVER!!).\u000a\u000aThis seems almost too good to be true \u002D perfect timing.\u000a\u000aBut \u002D a couple of questions please before I max out: \u002D\u000a\u000a1  \u002D Notice that help on the site comprises a single article on custom events \u002D and this looks like setting up custom code on a specific UI control \u002D is this really all the documentation available? Blod also comprises of 1 article....how well documented is help etc?\u000a2 \u002D Am I correct in assuming the Javascript code is a custom code snippet that can be embedded with Google Tag Manager (if not then rest will need answering, but know we can track all required DOM events using GTM)\u000a3 \u002D We operate a 100% serverless stack, either angular or react (single page applications) both of which of almost entirely client\u002Dside rendered (apart from non\u002Dcore services such as client messaging). Do you support this architecture and will we be able to track all necessary DOM events?\u000a4 \u002D The 1 blog article you have on the site currently is on customer personas. We track subscription type, persona type and role in both our SaaS products. We hold these as depersonalised values that are then made available to GTM (and from there to intercom, segment etc. via the DOM). Can we use this approach also for Onboardflow and if so, can we create logic to trigger unique onboarding tracking and push notifications for users based on these values? Site sort of touches on this, but the closest I can see is \u0022custom properties\u0022 in the Segment, Segment, Segment section on auto\u002Dmessages. What custom properties can we define, and how?\u000a\u000aThanks in advance\u000a\u000aRichard

Ben_OnboardFlow · Answer

Hey Richard,\u000a\u000aThanks for writing in \u002D sounds like you\u0027re on the cusp of awesome things. Here\u0027s hoping we can help you get over the line \u003B)\u000a\u000aPlease find my answers below:\u000a\u000a1) We do need to add some additional documentation \u002D so apologies for that being a little sparse. The good news is that other than triggering custom events within your website (which our support doc helps explain) there\u0027s nothing else you need to do. We automatically detect when people start a trial and convert (or not, as the case might be). This is all handled through a combination of you connecting your payment provider (Stripe, Chargebee etc) and installing our JavaScript tracker on your site. By default we track all page views automatically. If you want to track custom UX events as well (such as watching a video, or clicking a specific button) then the help doc we have around that provides instructions.\u000a\u000a2) Good question! Technically yes, but we haven\u0027t yet created any guides on how to install the tracker \u000avia GTM. You would need to define a data layer and then that would be referenced in GTM to ensure the correct data is sent via the tracker. Pop me a note when you\u0027re getting setup and i\u0027d be happy to help you out.\u000a\u000a3) Another good question. Right now we\u0027re optimised for multi page apps. However, we absolutely need to make sure we are compatible with single page apps as well. So as with my answer to number 2. Let me know when you\u0027re ready to get things integrated and i\u0027ll make sure to give you some guidance and / or assign some developer resources to make sure that we are fully setup to support your single page app.\u000a\u000a4) Yes absolutely. You\u0027d just need to define them in the GTM data layer. There are currently three types of things we can log against your users. Firstly, custom properties \u002D these are typically numbers, strings or booleans (so your persona type and role would be good candidates here \u002D FYI subscription plan is not needed here as we get that data from the payment provider directly). Second, we track page views within your app. This happens automatically \u002D though as noted, with your app being a single page one, we\u0027ll probably need to tweak a couple of things to ensure this works properly. And finally, you can fire custom events through a basic javascript call.\u000a\u000aHope the above helps. I\u0027m here if there are any follow\u002Dup questions.\u000a\u000aBen

OnboardFlow

Share OnboardFlow

Related questions