-
Lesson Overview
Transcription
Welcome to the training video on how to test and debug with Charles proxy. My name is Richard Jones and I'm a mobile implementation consultant at InsightOn. There are two main ways of testing mobile events and tags. The first is using the application Charles which we will go through in this video. Charles is a proxy tool that allows you to view Http and Https traffic between your device and the Internet.
This is used to us as we can see if the inciting calls are firing correctly along with any tags that we have implemented. If you do not have Charles, you can download from www.charlesproxy.com to set up Charles with your mobile device. Start by opening Charles going to help SSL proxy in install Charles root certificate on a mobile device or remote browser. This will show you the proxy IP address you need to use the port number and finally a web URL you can download the Charles certificate from. Firstly, we need to set up the proxy on your device.
You can do this by going into the advanced settings of the WiFi network you are connected to and changing the proxy setting to manual. In the proxy host name, you need to enter the IP from the Charles box. In my case, ten, 948, two, four, three. And then the port number, which is eight eight eight by default, unless you manually change this, save these settings and then copy the URL specified in the Charles popup and enter it into your device browser. This should automatically start the download for your child certificate.
Install this and you should be ready to start testing your implementation. Now that's sorted, let's start testing our insight and integration with the proxy setup. Let's open up our app. As a side note, I've set up Charles to rewrite the production call of Nexus Insighton.com to the test environment. Nexustest Insighton.com so the first thing we can see is a call to Nexus test Insighton.com.
This contains all the files that you'll need for your insight and integration. If you do not see this at all then please check that you have installed the framework correctly. Now with that showing, if we open it up you should see two directories, mobile two and your account name which is ens training 350. In this example, the mobile two directory contains all the configuration files from the mobile UI which is what we will be concentrating on. Here you will have a number of further directories pertaining to the coding, language, account name, app ID and version.
Within this you should see a number of files tag container HTML this file will bring down the bootstrap files for your integration CG PHP this contains the configuration setup for your mobile events. You can see here that we have the page view lifecycle event that we set up in the mobile UI. Mobile bootstrap JS this contains the JavaScript code to run. All of these files should be present. If not please revisit the installation videos.
You may also see Device JS this is to do with the connection to the Mobile UI. However we will go into that in further detail in the next video. Now that we know the insight and integration is correctly firing all calls, we can check if the Google Analytics that we set up is working. You can see a call to Google Analytics.com here, and if we look inside, we can see Analytics JS indicating that the base code has fired. If I navigate through the app, you can also see that Page calls are being successfully fired.
We can also look at the request of the analytics call, select Query String and see the custom dimensions that we set up. Thank you for watching this video. Please join me in the next video where we will go further into testing within the Mobile UI. 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!