The Ensighten Mobile UI has the ability for you to control which Mobile Events fire on which version of your Mobile App.
You may have multiple versions of your App as the App is developed over time and you may decide to fire certain Events/Tags on only particular App versions. You could create a new App ID in each App version and have multiple versions cluttering up your Mobile UI homepage, but if you have a lot of Apps using Mobile then this will become hard to maintain.
Luckily the Ensighten Mobile UI has versioning control. When you create a new App in the Mobile UI the default setting for ‘APP VERSION’ is ‘default’:
What ‘default’ means that if there is no corresponding App Version for your App, then the default Event configuration will be used.
What controls the App Version?
The App Version is controlled by the version number entered in your App code and can be seen in the configuration file (cg.php file) that is called from ‘nexus.ensighten.com’ when your App opens. If you use a proxy tools such as Charles proxy you can see the file and the version of your App:
As you can see in my example above, my version is ‘1.01’. However, at the moment, I don’t have a version value in my App’s Mobile UI configuration that matches ‘1.01’, I only have the value ‘default’
This means that any Event configured in the Mobile UI for this Application ID will fire. So, we may have only a simple Page View Lifecycle Tag firing on ‘default’:
So, let’s assume that version ‘1.01’ is our new and improved App. We may not want to use the same Events as before, but we don’t want to affect the other versions of the Apps. So, we create a new version.
When in the App’s homepage, click on the plus icon on the right-hand side. This will bring up a pop up where you can create your new version:
Click ‘ADD’ and your new App version will be created. All events from the default version will be copied over to the new version but will not be active until you commit and publish them.
In my new version I only want to fire some background and foreground events, I don’t want to fire the original page view event from default. So, making sure that my App version number is selected:
I can set up some new Events:
As you can see, I’ve only published the foreground and background events and the Page view is showing as ‘New’ so won’t fire. The default events are still the same:
In this scenario, any App, with ‘versiondemo’ as the App ID, that doesn’t match version ‘1.01’ will be served the default events. Version ‘1.01’ will only get it’s matching events.
By using versions, you can keep all of your App versions under one App in the Mobile UI and decide what Events/Tags are called on each version.
If you have any questions regarding this then please contact our support team at firstname.lastname@example.org
Please sign in to leave a comment.