Common Questions & Answers
For content management questions (pages, zones, items, campaigns, styling), see the Content Management Q&A.
Q: What are the staging app and staging console environment?
A: In Spaaza we work with a production and a testing environment. Before making the app public you get access to these testing environments. For the content management system is this: https://console-test01.spaaza.com/ and for the app it will be a test app version will be shared.
Q: What information is required for the initial app setup?
A: You must provide account setups (Google Play, App Store, Firebase), design assets (logos, fonts, colors), email domain settings, and other configuration details. See the Mobile App Onboarding page for the full list.
Q: What is the purpose of the testing (staging) version of the mobile app?
A: The staging version allows you to test and preview content changes on a real mobile device in a controlled environment before deploying them to production.
Q: How are store icon types configured in the app?
A: You choose between two approaches: one for stores planning to join (requiring specific icons) or one for various store types (requiring a range of icons), as defined in the additional configuration settings.
Q: What file formats are recommended for the client logo?
A: A 1024×1024px PNG is recommended, with SVG also supported for scalability and clarity.
Q: What are the recommended specifications for splash screen icons?
A: The splash screen icon should be a 960×960px transparent PNG with a centered 512×512px logo.
Q: Does the app support localized language?
A: Partly, all programmed text inside of the app is translated. Content you feed it through the CMS can be with some help of Spaaza. Vouchers can currently not be translated. The app does not have a language switcher but determines the language used by the settings of the users phone. Inform Spaaza for more details.
Q: I’ve made some changes to the content inside console but it does not display in the app?
A: Use the pull-to-refresh feature of the corresponding screen where you made content changes in console to refresh the mobile app’s page.
Q: How do I set up push notifications?
A: In Spaaza Console go “Settings” > “Integrations” > “View all triggers”. Then click “Add a trigger” > “Add Spaaza push message trigger”. Select an event, for instance: “Voucher is Issued”. Now every time a voucher is issued and the user has accepted push notifications in their phone they will receive a push notification. If this is not working yet, reach out to Spaaza. The push notification title will be generic. Currently you can only control the content of the notification.
Q: Can I make one specific campaign send a push notification?
A: Yes, it is also possible to make an event regarding a specific campaign trigger a push notification. It is only possible if the campaign issues a certain rewards, it will not work for “Personal Pricing Discounts” type campaigns. To do this go to your list of campaign and click the three dots (“…”) for one specific campaign and click “View”. In the header you will see “Triggers”. Click “Triggers” > “Add a trigger” > “Add Spaaza push message trigger”. The push notification title will be generic. Currently you can only control the content of the notification.
Tips
- Prepare all the campaign text content in a text document. Then copy and paste the content over to Spaaza Console. This way it’s easier to keep track of changes.
- Open multiple browser sessions at the same time to make working with console easier. You can do this by creating a second browser window but putting that window in incognito mode. Then you can put both browser windows side by side and start editing.
- Use the pull-to-refresh feature of the corresponding screen in the mobile app where you made content changes in console to refresh the mobile app’s page.
- When running a new type of campaign test them out in Spaaza’s Staging console environment and staging mobile app first.