In the previous article, we... E-commerce Demo Through virtual data simulations and analysis within the environment, we learned how Sensors Analytics helps users quickly understand the quantity and quality of new user acquisition across various channels. In actual use, Sensors Analytics utilizes data sourced from the client's own real user data.
In this article, we will briefly introduce the issues of data sources and data security.
Data source issues
All data in Sensors Analytics comes from clients' own data access.
Sensors Analytics primarily supports the collection of three types of customer-owned data: front-end operations, back-end logs, and business data (including historical data). Furthermore, Sensors Analytics provides various data access solutions and tools for data from different sources.
For example, we provide a client SDK , a server SDK , an external data import tool , and... Methods such as API import .
Data security issues
Except for the SaaS version service, where data storage is provided by Sensors Data, for the privately deployed standalone/clustered versions, all data is stored on the customer's server. Furthermore, Sensors Data will not provide user data from customers it has served to build a user tagging system for targeted marketing.
Meanwhile, in terms of technical implementation, we ensure the security of customer data from various angles ( related blog links ). For example:
- Support using HTTPS as the transport protocol
- Encrypt the transmitted content
- Backend data collection from Sensors Data will not expose customer data.
- Antispam after collection
This concludes our beginner's guide. In the next chapter, we will detail how to use the various analytical models offered by Sensors Data.
Welcome to Sensors Analytics E-commerce Demo Follow the instructions to practice.