What are Guides?¶
In Pointzi terms a "guide" is a general term for Announcements, InApp Videos, Carousels, Contextual Tips, Tooltips, Surveys/Feedback and FAQs. Most importantly within one guide, you can have 1 or more of the above in a sequence - allowing you to take a user on a tour of a few screens and their elements.
How many Guides do I have on my Pointzi Plan?¶
Pointzi allows you to engage and guide users through the full lifecycle, for this reason we provide plans primarily based on Monthly Active Users (MAU) and number of enabled guides. As you conclude your trial period, you will decide with Pointzi how many MAU and how many enabled guides you need.
Enabled simply means that this guide has the green slider and green "Running" indicator in the Guides screen (And the "FAQ Lists" screen). You can have many Guides that are drafts, expired, inactive and these do not count toward your Plan.
- drafts - a guide you have been working on but have not launched to your user base.
- expired & inactive - when you create a guide you can set its activation and expiry date-times. These guides will start and stop according to your settings at save time.
e.g So your plan might be purchased to support 10K MAU and 25 Guides. You might have 30 other inactive guides that do NOT contribute to the Plan limits.
Each row that has a green "running" counts as "1" of the 25. Within each (Guide) row, it could be a simple tooltip or it could be a sequence or a video or a feedback So when you disable or if the guide expires then, the green "running" no longer counts toward the plan.
Can I have one guide for multiple operating systems?¶
No. Customers usually have some guides the same on IOS and Android, but they also count as "1" each as the operating systems are different designs and different analytics. This is true even for hybrid platforms like Cordova/Ionic or ReactNative.
Can I have one guide for multiple languages?¶
Unfortunately no. At this time we allow you to set a filter for a specific language group, Pointzi SDKs automatically detect the language on the user's device and send it to the cloud as "sh_language". That is matching a specific guide for a specific language (along with other filters) for the user. Its best to keep guides seperate for languages as it allows the guide analytics to be independent for each language - you can see which language guides are performing better.
To create guides for multiple languages:
- Perfect your first guide. Make sure audience you have selected a "User String Properties" to target your desired language(s).
- In the Guides list, click on the 3 dots and select "Duplicate" - the copy will appear in the Guides list as disabled.
- In your new Guide, edit the text for the new language. Change the "User String Properties" to your new language. Save, Preview. Enable.
BTW, Pointzi does not provide automatic translation.
You can read more about the sh_language tag and other tagging here.
Can I have multiple Apps on my plan?¶
Pointzi allows IOS/Android and Web Apps all on one plan (and app_key). Further you get two app_keys:
- for your staging or development environment
- for your
If, however, the functionality is different this may not make sense as:
- the analytics will be conflicting
- the guides have no commonality or natural grouping
Do your plans support Web App domain wildcards?¶
Yes, you can have one plan (app_key) support the following (where your product is acme-app.com):
- SiteA.acme-app.com, SiteB.acme-app.com, whatever-subdomain.acme-app.com
- acme-app.com/SiteA, acme-app.com/SiteB, acme-app.com/whatever-subdomain
Refer to Advanced URL Settings in the Pointzi Creator (Chrome Extension)
Do Pointzi plans support whitelabled or multi-tenant Mobile Apps?¶
Yes probably, if (and only if) your app is fundamentally the same design.
|General analytics may make sense||You won't be able to segment general usage analytics per customer|
|One guide per OS can be used and show across all apps||To get performance for different apps for the same guide, you would have to run seperate guides|
|You can use tags to target guides per app. e.g have a tag called "CustomerID"||You will use more guides in your plan|
|You can use tags to personalize per app. e.g have a tag called "CustomerName" and use substitution||N/A|