If collectLifecycleData() is called twice in the same session, then your application will report a crash on every
call after the first. The SDK sets a flag when the application is shutdown that indicates a successful exit. If this flag
is not set, collectLifecyleData() reports a crash.
Events, Props, and eVars
If you've looked at the Adobe Mobile Class and Method Reference, you are probably wondering where to set events,
eVars, props, heirs, and lists. In version 4, you can no longer assign those types of variables directly in your app.
Instead, the SDK uses context data and processing rules to map your app data to Analytics variables for reporting.
Processing rules provide you several advantages:
• You can change your data mapping without submitting an update to the App Store.
• You can use meaningful names for data instead of setting variables that are specific to a report suite.
• There is little impact to sending in extra data. These values won’t appear in reports until they are mapped using
processing rules.
Any values that you were assigning directly to variables should be added to the data HashMap instead.
Processing Rules
Processing rules are used to copy the data you send in context data variables to evars, props, and other variables
for reporting.
Processing Rules Training @ Summit 2013
Processing Rules Help
Become authorized to use Processing Rules
We recommend grouping your context data variables using "namespaces", as it helps you keep logical ordering.
For example, if you want to collect info about a product, you might define the following variables:
"product.type":"hat"
"product.team":"mariners"
"product.color":"blue"
Context data variables are sorted alphabetically in the processing rules interface, so namespaces let you quickly
see variables that are in the same namespace.
Also, we have heard that some of you are naming context data keys using the evar or prop number:
"eVar1":"jimbo"
This might make it slightly easier when you perform the one time mapping in processing rules, but you lose readability
during debugging and future code updates can be more difficult. Instead, we strongly recommend using descriptive
names for keys and values:
"username":"jimbo"
Context variables that define counter events can have the same key and value:
"logon":"logon"
Context data variables that define incrementor events can have the event as the key and the amount to increment
as the value:
"levels completed":"6"
Note: Adobe reserves the namespace "a.". Aside from that small restriction, context data variables just need
to be unique in your login company to avoid collisions.
12Analytics
(73 paginas)
Manymanuals.com
Manymanuals.de
Manymanuals.fr
Manymanuals.it
Manymanuals.pl
Manymanuals.cz
Manymanuals.es
Manymanuals-pt.com
Comentarios a estos manuales