#Console Usage Guide
#Create an App
Step of creating an application:
Click the [Add app] button
Configure app information：
Fill in the correct package name, app name and server key(Firebase).
After the creation is complete, you can click on the app to enter the [App Settings]-[App details] to view the app information. And refer to the Android SDK Access Guide to complete the SDK access.
The user who created the application is the [owner] of the application and has all the information viewing and operating permissions for the project. The owner can assign [Operation] and [Administrator] permissions in the permission configuration.
User group is to combine the conditions of tag targeting, which is convenient for operations to directly select the created targeting combination when creating a message.
Click [Add Group], enter the user group name. For example, add a group of "African", select African countries and click [Confirm], the user group "Africa " has been created. At this time, in the message creation interface, select the "African " for the targeting-user group, that is directly select the targeting condition for this group.
This page is the application owner (creator) permission. You can add users and set the users to [Administrator][operation] [Test] permissions.
Note: The following are permissions assignments.
Click [Add Member], enter the user email and select the role and click [Add] to complete the operation. Unregistered users can register by checking the email and clicking the link.
Select the application, push the message-push notification, select the system default style / custom style, fill in the push content and click the [Create] button at the bottom of the page to enter the message preview.
[Small icon] is the small icon in front of the application name.
After the message is created, it will first enter the preview interface to review the push content for the last time.
After the push is completed, jump to the push records to view the push data.
Transparent transmission is that developers can send custom message content to APP. For the operation steps, refer to Push Notification.
The message record presents details and statistics of all instant or timed messages that have been created.
[Cancel] send：Before the timing message occurs, click [Cancel] in the record to cancel sending.
[Copy] Click Copy to return to the message creation interface. The content is copied to this record, which can be edited and then sent.
[Edit] It is possible to modify and save the content before the timing message occurs.
[Pause sending] Before the message is sent, if it is found that the content of the message is incorrect or other scenarios where the sending needs to be paused. After a pause, you can continue sending before the message is valid.
[Continue sending] After the push message is paused, you can continue to send it before the message expires.
[Withdraw] Message withdrawal is to withdraw the displayed (not clicked) message within the validity period of the message, and stop sending when the message is not sent. This function needs to upgrade SDK to 1.1.6.06 and higher.
Est.delivery：Target users (installed minus known uninstalls minus 3 months of inactivity minus silent users)
Delivery：The actual number of users successfully delivered (the number of successful releases returned by firebase (the reason for the unsuccessful delivery: the token is invalid))
Arrives: Number of messages successfully pushed to users' phones
Arrival rate: The proportion of messages arriving at the user to the total effective amount (arrivals / pushes)
Impressions: The number of messages successfully displayed in the notification bar after the user's mobile phone received the message
Imp rate: Impressions / Arrives
Clicks: The number of user clicks after the message was displayed in the system notification bar
CTR: Clicks / Impressions
Conversions: Conversion events are customized by the app. Conversions show how many aspects of the marketing campaign (e.g., campaigns, ad networks, creatives) brought in conversion events and purchases, and how much revenue and lifecycle value, etc.
Conversion rate: Conversions / clicks
Analytics show the number of pushes and user-related data. You can view data statistics within one year and support export reports.
New users refers to the new application users who have Twibida service. When the app starts for the first time, the Twibida SDK initiates an internal registration with Twibida.
Active users refers to the total number of active users who open the process at least once in the statistical time.
Valid users: refers to users who have installed the app, remove users who have been uninstalled, and remove users who have not been active for three months.
Turn on the developer's "Test mode" switch, and the user enters the test mode directly. Test mode in order to meet the needs of developers for push-related development and simulation testing, and to avoid affecting online users. Developers can begin to execute this process according to actual needs.
Use the "test mode" process as follows:
- Developer needs to prepare a test app that matches the official app package name.
- Add push SDK:
The app owner turns on the developer-test mode switch to enter the app settings page in test mode. Add push SDK according to test mode's App ID, App key, App secrets. Please refer to SDK Access Guide.
- The developer makes the test-related logic, which is convenient for the test to switch to the test environment with one click in the same package. For the method, refer to 2.6 Set test AppId and AppKey.
- Testers or other developers need to assign “Testor” permissions. In the official application, “Testor” permissions can only be directed to Gaid to send messages. In test mode, “Testor” permissions are upgraded to push tests in various dimensions.
- After the test mode test is completed, continue to do the directed push test under the formal application, and go online after verifying that there are no problems.