Introduction to Adobe Mobile Services

web and apps

In most of my posts, I refer mainly to the Adobe Experience Cloud applied to the web. I have written a few posts on mobile apps, but I have not yet written an introduction to Adobe Mobile Services. In my experience, it has surprised me the lack of knowledge there is about what you can do with an app. Today I will explain how to use the Adobe Experience Cloud with mobile apps.

Read more

Hybrid apps, visitor stitching and Visitor ID Service

The classical problem of how to make sure that, in hybrid apps, the journey is not broken when transitioning from the native app to the embedded browser, is well known and it has been solved a long time ago. My colleague Carl Sandquist wrote a great post in the official Adobe blog some time ago about how to stitch visitors in hybrid apps. Two years later I still reference it to my customers. I recommend that, before you proceed with the rest of this post, you read it.

However, the aforementioned blog post does not cover the Visitor ID Service. It is still rarely used in mobile apps, but I am sure this will change as Web analysts use features like Customer Attributes.

Mobile SDKs currently support the Visitor ID service. It is very easy to enable: just add your Adobe Marketing Cloud Org ID in the ADBMobileConfig.json configuration file:

Now, the problem we face in hybrid apps is how to send the unique Visitor ID that has been given to the app, to the mobile web. I have not found anywhere any documentation about it, so I will attempt to explain it.

The first step is to retrieve all the possible IDs that may have been used. This is important as, during app upgrades, you do not want to create a new visitor and inflate your statistics. So, if an old value is still available, we should continue using it.

The next step is exactly to create a URL with all the previous parameters; this value needs to be passed to the web in a query string parameter. For example:

Moving to the web, the code becomes more complex, as there are various variables that might need to be set. In the s_code, outside of the doPlugins section,  you need to add the following code:

A few notes about the previous piece of code:

  • As with the SDK configuration, you need to replace YOUR-MCORG-ID with your Adobe Marketing Cloud Org ID
  • I am assuming you are using the AppMeasurement library; if you are still in the old H s_code, remember to replace the s.Util functions with the equivalents in H s_code.
  • The Visitor API version needs to be 1.3 or above.

If you are using DTM,you should copy this code to the “Customize Page Code” section of the Adobe Analytics tool.

visitoridhybrid

It must be noted that you must select “Before UI settings”.

Now, you should have a single journey in hybrid apps and use all the capabilities of the Marketing Cloud.