Summary

• Page properties (1 modified, 0 added, 0 removed)

Details

Page properties

Content

...	...	@@ -155,24 +155,10 @@
155	155
156	156	== 3.2 Tracking in app events ==
157	157
158		-In-App Events provide insight on what is happening in your app. It is recommended to take the time and define the events you would like to measure.
159		-
160	160	=== 3.2.1 Overview ===
161	161
162		-An event consists of two fields that you (% style="display:none" %) (%%)can use to describe a user's interaction with your app content:
163		-
164		-(% class="table-bordered table-hover" %)
165		-|(% style="background-color:powderblue; width:200px" %)**Field name**|(% style="background-color:powderblue; width:200px" %)**Type**|(% style="background-color:powderblue; width:200px" %)**Required**|(% style="background-color:powderblue; width:200px" %)**Description**
166		-|(% style="width:200px" %)Category|(% style="width:200px" %)String|(% style="width:200px" %)yes|(% style="width:200px" %)Event category
167		-|(% style="width:200px" %)Parameter|(% style="width:200px" %)String|(% style="width:200px" %)no|(% style="width:200px" %)Event parameter.
168		-There can be more than one
169		-
170		-You can use any event category or parameter string of your choice. However, react-native-mobigate plugin contains recommended event categories and parameters via String constants (see [[Event categories>>doc:||anchor="H3.2.3Eventcategories"]] and [[Event parameters>>doc:||anchor="H3.2.4Eventparameters"]]).
171		-
172	172	=== 3.2.2 Implementation ===
173	173
174		-Tracking in-app events is performed by two methods:
175		-
176	176	=== 3.2.3 Event categories ===
177	177
178	178	=== 3.2.4 Event parameters ===