What makes a person a ninja? The formal definition of a ninja is “a person trained in the ancient Japanese martial arts and mainly used for espionage and assassinations.” It’s dark, I know. But I found another definition, this time in the Oxford Dictionary.. “A person who excels in a skill or activity” That’s what I’m talking about here to help you become a mobile ninja implementation, j ‘have some tips and tricks – mainly based in our Adobe basic Services solution. – some of which will also help pull the power advantage of the mobile analysis
to become a ninja mobile implementation, it need three things.
- core competencies, and
- An array of special moves, deployed with powerful tools
when I think of a ninja, I remember I was playing video games where warriors would deploy “finishing” moves when the opponent was running on force. as the battle progressed, the movement have become more powerful. This is the approach that I advise clients to make as they develop their strategies for measuring mobile applications. So let me give you some basic skills and help maximize the accuracy of your movements and your mobile end implementation with a ninja finishing moves.
basic skills Mobile-Ninja
First, we will learn some new basic skills!
Know Your JSON config file.
I like to think of JSON config file as the brain of the mobile software development kit operation (SDK). This file is fully configurable through the user interface of mobile services. One of the most important parameters is LifecycleTimeout . By default it is set to 300 seconds. This parameter determines the duration of your application can be in the background before launching a new app-launch event, and I recommend you tune based on the average session length of your application. In addition, you can enable the acquisition of mobile applications by setting ReferrerTimeout to a value greater than 0, which is the main way to collect mobile app-purchase bonds in core mobile services .
switch to JSON Runtime.
A constant problem I’ve noticed is that clients will use a JSON config file that points to a development or preproduction report later while they ‘re still developing the application. In the race to publish applications in app stores, this setting is sometimes overlooked, and you are left with data that is being sent to your Suite development report. But, you are able to replace the location of the config JSON file when running, giving you the ability to switch between a development configuration file for testing and a production configuration file for your launch!
Special Moves to improve monitoring
Now we’re going to maximize the accuracy of your movements!
use the “Secret Menu” SDK variables.
Adobe SDK collects most of its data via contextual variable data, but there are some exceptions. There are variables that you can call if you want to set up specialized use cases:
- && products / EVAR – The variable products must be defined using this specialized syntax. If you eVars merchandising you want to send along with the variable product, you can call them specifically as EVAR in the product chain.
- && events – We recommend this option if you use serialized events. For example, if you are a retailer, you can serialize an event (such as buying event) so it is not counted more than once. Unfortunately, the processing rules can not do the serialization event, so set this variable for more precise tracking.
- && tnt -. When using Adobe target, set this variable to send data in the target
- && currencyCode – One of my new favorites! Again, this can be done via the processing rules, to use this variable to designate the currency conversion code.
Keep track background.
This is a cautionary tale plus a tip. If you are going to follow-up services (such as notification- services or location-based) that “wake up” your application in the background, make sure to use the correct name followed to ensure that these services triggered by inadvertently Analytics calls.
Finishing Moves – The Ones Awesome
And finally, we get to the good stuff
App to Track Web Handoff.
Many applications use a combination of native application screens and Web views that are formatted to appear as if they are loaded from within the application. You can track a visitor transfer smoothly from your application on your web-view by synchronizing the ID of visitors on both platforms. You can do this by determining which visitor ID you defined in your application (including Adobe Marketing Cloud ID) and send them to be collected and used in web-view. This will help you avoid a broken trip, what happens when a different visitor ID is defined as the user moves between the application and the web-view.
Trigger an In-App Message From Adobe Audience Manager (AAM) Segment.
Yes, you can! In the mobile SDK Adobe, Adobe Audience Manager returns information / public segment via JSON response. You can check the JSON response, analyze segment ID values, and pass them in Analytics as a context variable data, separated by commas. Once this variable is collected by Analytics, you can use the value (s) to trigger a message in real time application based on the values you set. Conversely, you can use it later to send push notifications to selected segments of the users of your application. Awesome!
Now Become the Mobile Application Ninja You were meant to be!
Use these tips and tricks mobile implementation to get the most of your mobile solution Application Analysis. To learn more, see my mobile session implementation Adobe Summit this year -. Session # 358