This topic describes how to use Quick Tracking to provide detailed guidance for businesses, requirements, and technologies. This way, you can efficiently implement tracking and access to Data Management, analyze, and build and display visual Kanban boards.
Newcomers need to know
First, let's understand the complete tracking process, from requirement raising to data collection to Quick Tracking display, which key links are included:
Step 1: Business preparation (requirements | business technology)
The demand personnel will lead the overall demand combing, index system design and burial point scheme design. Among them, business personnel cooperate with demand communication, technical support personnel cooperate with buried point scheme design confirmation. This section is recommended to be conducted under the guidance of Quick Tracking's analyst team.
Requirements | Business
Sort out modules such as core objectives /KPIs, user journeys, user groups /product features, and existing indicator systems to clarify business objectives and core requirements.
Index system design (requirements)
After sorting out the business requirements, you need to define key business indicators, build an indicator framework, and precipitate an indicator system; that is, to clarify what data the requirements will eventually see, you can refer to the standard indicator system for design.
Burial Point Scheme Design (Requirements | Technology)
Scene event design is based on business requirements (metrics). Scene event design should combine workflow and interface content, and technical content reporting is based on scene events.
Step 2: Product Preparation
Before you use Quick Tracking, you must create an organization and an application. Then, you must integrate SDKs, collect user behavior logs, and analyze data.
Organization Management: creates and manages the organizational structure of an enterprise or team.
Application Management: Create an independent application for each project.
Permission management: You can configure permissions for different roles to ensure data security and standardize operations.
Step 3: Enter the embedding scheme (requirements)
After the tracking solution is approved by business and technical parties, you need to log on to the Quick Tracking background to manage events and prepare for the next step of tracking integration.
Scenario Management: Scenario Management is a folder of events. Events are summarized and managed.
Event Management: defines user behavior events and their trigger conditions. It must be managed according to the design of the tracking point scheme to map the events reported by the technology, and then the events can be selected for analysis in the analysis module.
Attribute Management: allows you to add event-related attributes to enrich data. The attributes include event attributes, global attributes, user attributes, and channel attributes.
Step 4: Embedding Integration and Verification (Technology)
After you create an organization and an application, you must connect the client to the SDK to collect user behavior logs and provide a data source for subsequent data analysis.
SDK integration (technology)
The first time you implement embedding on a client, you need to initialize the SDK by operation. Currently, data can be accessed from multiple clients. For more information, see.
End | References |
Android | |
iOS | |
Web | |
Mini Programs | |
uniapp | |
flutter | |
React Native | |
Hongmeng Next | |
Quick App |
Buried point verification (technical)
After the technology reports data, you need to check whether the reported information is consistent with the collected information. You can use multiple methods such as log verification, tracking verification, and analysis verification. For more information, see tracking verification.
Step 6: Buried point release (technical)
After both technical and business verification, the technical support personnel can publish the code to the production environment. Pay attention to the appkey and domain name of the production environment.
Step 7: Data analysis and presentation (requirements)
kanban build
Kanban is divided into two types:
Preset dashboard: allows all users who have the required permissions to view the dashboard. This dashboard is used to implement standardized monitoring and collaborative analysis of key metrics within an organization.
My dashboard: You can create and manage a dashboard. The dashboard can be viewed only by the user or authorized to view the dashboard.
Data model analysis
Quick Tracking supports model analysis such as event analysis, vulnerability analysis, retention analysis, distribution analysis, interval analysis, session analysis, path analysis, visualization analysis, and attribution analysis.
Follow the above steps step by step to quickly master and use Quick Tracking to complete data collection and analysis tasks!