Data Verification Definition
Test Data and Production Data
The Operation Growth platform has two types of data by default: test data and production data. These two types of data use different reporting methods and storage locations. There are no other configuration differences, and the two types are isolated from each other. After configuring metadata and data sources, it is recommended to first use the Data Verification feature to report test data in data verification mode. After verification shows no exceptions, report production data.
Data Verification Feature
Applicable Scenarios
To make it easier for users to debug code and adjust data formats, and to ensure the success rate of data reporting in the production environment, we provide SDKs for each platform, such as Android, iOS, and WeChat Mini Program, and add data verification mode. It is mainly used for:
- Developers debugging code and data.
- Sending data to the backend in synchronous and blocking ways. This mechanism may differ slightly on some platforms due to platform characteristics.
- Displaying server-side verification results in real time. When verification fails, the specific error reason is displayed, and users are explicitly reminded in forms such as thrown exceptions.
- For data that passes verification, the data verification feature lets you view in real time the values and types of each field in the final stored records.
Operation Guide
The Operation Growth platform provides a feature for reporting test data in data verification mode to check whether the reporting format is correct. For operation details, see Data Verification.
Handling Data Reporting Exceptions
In principle, we recommend reporting data according to the data type and data requirements configured for attributes. See Attribute Data Types. When data does not meet requirements, the system attempts conversion and storage. If conversion succeeds, the data can be used. If conversion fails, the data cannot be used or is discarded directly.
| Data Reporting Exception | Whether Data Is Stored | Whether Data Can Be Used | Recommended Action |
|---|---|---|---|
| Event data that has not been created is reported | Yes | The entire record cannot be used | Create the corresponding meta event on the platform according to the actually reported data, then it can be used normally |
| Custom event starts with jg | Yes | The entire record cannot be used | Not supported for now |
| Event name starts with a non-letter, contains uppercase letters, or contains special characters other than underscores | Yes | The entire record cannot be used | Not supported for now |
| Attribute data that has not been created, or attribute data not associated with an event, is reported | Yes | The incorrect attribute cannot be used; other data can be used | Create the corresponding event attribute or user attribute on the platform according to the actually reported data, and associate it with the event, then it can be used normally |
| Configured attribute data type does not match the actually reported attribute data type | Yes | The incorrect attribute cannot be used; other data can be used | Contact technical personnel to modify the data type on the platform according to the actually reported data, then it can be used normally |
| Event name starts with a non-letter, contains uppercase letters, or contains special characters other than underscores | Yes | The incorrect attribute cannot be used; other data can be used | Not supported for now |
| Reported attribute value is empty | Yes | The incorrect attribute cannot be used; other data can be used | Not supported for now |
