Tracking In-App Branded Content
How Nudge Works
There are typically two scenarios of branded content delivery mechanisms mobile publishers use.
1) They trigger a built in web browser and pull in an HTML view of their content.
This could be the same URL as their web destination, or a private URL specifically for the app.
2) They use native mobile app components, to build a web-like view.
This is typically via API requests which fetch the web content and display it.
For Scenario 1, Nudge code works and will show all of its regular tracking.
Often the app though, will remove the referral and and tracking tags. This means the campaign will show high mobile direct traffic. The fix to this is to load a parameter using the Nudge traffic source builder.
For Scenario 2, Nudge does not track.
At the moment, it is advised, to understand what analytics they do use. Please contact support, and Nudge will help advise the best next step.
How to tell what scenario a publisher is using:
Often an app is one, or the other, or a hybrid of the two. The best bet sure fire way is to ask the partner, to connect with the app team to clarify.
A giveaway that someone is using a native mobile app, can be if clicking a link on a branded content piece, the link opens a new browser or a different view to open that. Rather than staying in the same view as the article. As this has meant the app has had to engage a web view.
You may have already isolated this early, through simply putting the Nudge code across the content and seeing the web app traffic.