-
Lesson Overview
Transcription
Hello, welcome to the training video on how to test and debug your insight and mobile integration within the mobile UI. My name is Richard Jones, and I'm a mobile implementation consultant at InsightOn.
Previously we went through testing your insight and integration using Charles. Today we will walk through how to test using the mobile interface.
There are two ways to set up your connection to the mobile UI. The first way is by using a four finger press. So firstly ensure that you have the mobile UI screen open. Then in your app, press down four fingers onto your screen for at least 5 seconds. You may need to try a number of times as interaction on the page can disrupt the call. But if all is successful, you should see a pop up at the top or bottom of your screen informing you.
The connection has been made.
Another way to see if the connection.
Is working is via Charles.
The file device JS will appear. The second way is to create an app within your managed space. If you add the app inside of Mobile Tools, you'll be presented with a blank field to add IPS in. If you enter yours here, which you can find by simply searching my IP and then save, commit and publish the tag with all the other options left as default, it will automatically make the connection when you open up the app. Now that the connection has been made, what has this actually done? Well, if we look in the mobile UI within the top corner, we can now see that the little phone icon is now lit up. If we select this you will see a list of connected devices as we are the only ones connected in this account at the moment. You can easily see my device with it showing my device name and app ID. When we select the device we are shown some details about the app below this we have advanced settings which when expanded allows us to select the Show Console switch. You'll be able to see that a box has appeared at the bottom of the screen.
Now you can see at the bottom.
We have three tabs console, Test JavaScript and Test Config starting at Console. This is really useful if you do not have Charles. Firstly, you can see all network requests coming out. For example, if I change pages in my app, you can see here the Google Analytics request that we set up is being sent out.
In addition to this, you can also.
Run some JavaScript in the same manner as you would in the console of your browser. For example, if we put Console log.
Hello World, we can see hello world gets printed. We can use this to test out.
The JavaScript of tags before implementing them.
Debug issues or even fire off mobile.
Events to check that the events are working. To highlight this, we can fire off the page U tag event that we created in an earlier video and you can see the Google Analytics page U tag being sent in the console. The next option is test JavaScript. This is really useful as we have a set of common JavaScript functions here.
Such as print the data model to.
The console to inspect the framework values and Top View controller to view the page controller name. The final option is test config. As explained in previous videos, the config is a JSON object that is sent to the app based on the event and tokens you had set up.
You can send configs here before actually.
Implementing them, allowing you to test in your app on the fly. You thank you for joining me for this video and I hope you have learned how to test and debug your insightem mobile integration over these two videos. If you have any questions then please contact our support team via Support@insighton.com.
Feeling confident in your Ensighten Manage skills? Take our Ensighten Certified Professional - Mobile Quiz to see how you stack up!