Project data processing rules
The system creates the data structures used for analysis when events and properties are reported for the first time. If the first reported data is incorrect, the structures are created incorrectly, which makes later fixes costly.
If you have already added a tracking plan to the system, you can use it as the data processing standard to keep reported data consistent with the planned data in the early stage of data reporting.
You can configure tracking plan-based data processing rules in Project Settings → Settings → Implementation → Data Processing Rules. Three modes are available:
| Mode | Description |
|---|---|
| Free Reporting | The tracking plan places no constraints on saving reported data. |
| Strict Verification | Reported data that doesn't match the tracking plan can't be saved. Recommended for projects with high data quality requirements. |
| Customize | When reported data doesn't match the tracking plan, custom rules determine whether the data can be saved. |
Reported data is checked against the tracking plan for consistency in the following cases:
- Events not in the tracking plan
- Event properties not in the tracking plan (event properties that don't exist under any event in the tracking plan)
- User properties not in the tracking plan
- Event properties or user properties whose property type is inconsistent with the tracking plan
Choose the data reporting mode that fits your constraint requirements for the check scenarios above. After it's set, members can view the current project's Data Processing Rules settings on the Tracking Plan page:
Note:
-
Data processing rules take effect only when the tracking plan isn't empty. If no tracking plan is configured or the tracking plan has been cleared, data is processed in Free Reporting mode.
-
Data processing rules apply only to newly reported events or properties whose metadata hasn't been generated yet. (That is, if metadata for an event or property already exists in the system, a newly created data processing rule doesn't take effect on that existing metadata.)
For example, the "recharge" event isn't recorded in the tracking plan, but data has already been reported for it. If you select Discard for Events not in the tracking plan, the rule doesn't apply to the "recharge" event.