# Custom Event
Two types of events can be viewed in the Data Management interface. Events created based on the reported data are tracked events, while those created by configuration rules are custom events. Given the high cost and stable needs associated with changes in the structure of reported data, flexible data requirements need to be fulfilled by custom events.
In case of the following needs, you may create a custom event:
- To combine multiple reported events into events of the same type for analysis;
- To break down a reported event into events with finer grains;
Scenario examples:
- What is the performance of user consumption behaviors related to topup or item purchase in Shanghai region?
Multiple topup and purchase events need to be combined, and events should be filtered on regional dimension in order to limit the analysis to Shanghai.
- Analyze the distribution of the trends on users' prop consumption or use?
Multiple events on prop consumption and use need to be combined.
- Analyze the performance of user behaviors associated with users' acquisition of coin/dimond/prop rewards from the source channel of Application Treasure?
Events associated with acquisition of coins, diamonds and props need to be combined, while limiting source channel to Application Treasure requires filtering the source channel dimension of the events mentioned above.
Rules for custom events(see the following chart):
- If any event is triggered, it is deemed that the custom event is triggered
- Global filtering simutenously acts on all events to which the rule is applied
- A custom event will inherit the association relationship of common event properties of events to which the rule is applied.