This framework will enable your organisation to do mobile analytics and track user behaviour in your apps. It is only usable if your organisations has a mobile analytics account at Kantar Sifo:
https://www.kantarsifo.se/kontakt.
It is currently limited to Swedish customers only.
This framework is also available as a zip for manual installation, if you don't want to use cocoapods:
https://github.com/kantarsifo/SifoInternetSDK
This instruction assumes you have Cocoapods installed and are familiar with it. Otherwise check instructions here: https://cocoapods.org/
You also need to have the 'Sifo Internet' panelist app installed on your test device. The 'Sifo Internet' app holds your Sifo ID details. Otherwise look here: https://apps.apple.com/se/app/sifo-internet/id1015394138
This framework tracks a user by making a formatted url call ('SendTag') with a cookie to a backend. Registered users are identified via a Sifo account and a UUID in the keychain (or NSUserDefaults if you don't want cross-app UUID sharing). The backend recognises the user via the cookie and the resource is tracked by the url. There a two types of users: Anonymous users and Orvesto panelists, who has opt-ed in to be tracked and is using a separat panelist app, called 'Sifo Internet'. It's optional to track all users or only panelist users.
This framework will open the 'Sifo Internet' app at first launch, if installed. If the 'Sifo Internet' app is configured correctly, then the 'Sifo Internet' app will in turn open your app almost directly, with a cookie in the app url. This cookie will be stored by the framework. It will also create a UUID in the keychain/NSUserDefaults. This UUID can be shared among your apps using a shared keychain or NSUserDefaults. After a successfull initialisation, the framework is ready to send your tracking tags to the analytics backend. You can track these tags using your tools obtained from Kantar Sifo upon registration.
To make this work, there a few things needed:
- Allow your app to open the 'Sifo Internet' app in Info.plist
- Add a shared keychain id to an Entitlements file (Optional)
- Add the code below to integrate framework
- Add SendTags according to your tracking needs
What permissions does the Sifo SDK require?
The Sifo SDK is happy with whatever permissions your app uses.
- If your app requests access to IDFA through the App Tracking Transparency framework the Sifo SDK will also get access to IDFA.
- If your app does not request access to IDFA the Sifo SDK will use the IDFV to track panelists.
5.3.0
- Swift Package Manager Support
- Removed support for CocoaPods (will probably come back)
- Added Swift wrapper Library
- Renamed objc library and removed the exposure of objc code
5.1.1
- Fix memory leak that occurred in some specific scenarios.
- Add app version info to tags and cookie.
5.1.0
- SDK skips unnecessary call to server for non-panelists.
- SDK initializer includes new parameter to specify whether IDFA and IDFV should be used for tracking or not.
5.0.4
- SDK not longer uses AppTrackingTransparency framework.
5.0.3
- App start tag sent for apps.
5.0.2
- SDK now asks for tracking permission on iOS 14 for panelists.
- Added support for multiple webviews.
5.0.1
- Added support for iOS 14.
- Sifo panelists now sync with IDFA and IDFV.
- SDK can now detect faulty integration and warn about it.
- Bug fixes and improvements.
Minimum iOS deployment target: 9.0
1. Add library to project
Swift Package Manager:
source 'https://github.com/kantarsifo/SifoInternet_IOS_SDK.git'
2. Initialize the framework
class AppDelegate: UIResponder, UIApplicationDelegate {
func application(_ application: UIApplication, didFinishLaunchingWithOptions launchOptions: [UIApplication.LaunchOptionsKey: Any]?) -> Bool {
TSAnalyticsSwift.initialize(withCPID: ...,
applicationName: ...,
trackingType: ...,
isWebViewBased: ...,
keychainAccessGroup: ...)
return true
}
}
CPID
- Your Kantar Sifo Analytics id.ApplicationName
- Name of your app, can be anything you like that makes sense.TrackingType
- EitherTrackPanelistsOnly
orTrackUsersAndPanelists
.IsWebViewBased
- Set this totrue
if the app’s primary interface is displayed in one or many webviews.KeychainAccessGroup
- (Optional) Your app id or a shared app id if you have several apps sharing a keychain and your want to track the user between apps. If you don't need to use Shared Keychain functionality, then set this tonil
.
The purpose of this integration is to identify the user as a certain panelist. To allow the framework to integrate with the Panelist app you need to follow these additional integration steps.
1. Add url scheme, query scheme and user tracking usage.
Update your info.plist
to include.
Add query scheme:
<key>LSApplicationQueriesSchemes</key>
<array>
<string>se.tns-sifo.internetpanelen</string>
</array>
Add url scheme with <your_bundle_id>.tsmobileanalytics
:
<key>CFBundleURLTypes</key>
<array>
<dict>
<key>CFBundleTypeRole</key>
<string>None</string>
<key>CFBundleURLSchemes</key>
<array>
<string>my.example.id.tsmobileanalytics</string>
</array>
</dict>
</array>
2. Update Scene or App Delegate.
To have this custom URL scheme picked up by the framework you have to implement the relevant method. If your app has a AppDelegate and a SceneDelegate then you should implement the SceneDelegate version. If your app only has a AppDelegate then implement the AppDelegate version.
SceneDelegate:
func scene(_ scene: UIScene, openURLContexts URLContexts: Set<UIOpenURLContext>) {
for ctx in URLContexts {
TSMobileAnalytics.application(UIApplication.shared, open: ctx.url, options: [:])
}
}
AppDelegate:
func application(_ app: UIApplication, open url: URL, options: [UIApplicationOpenURLOptionsKey: Any] = [:]) -> Bool {
return TSMobileAnalytics.application(app, open: url, options: options)
}
3. Set webview (hybrid apps and other apps containing content in webviews).
If your app is webview-based, or contains content in occasional webviews that should be tracked, you need to tell the framework which webviews to track by adding them:
TSMobileAnalytics.addWebview(webView)
And stop tracking it, if it's completely removed from the view hierarchy:
TSMobileAnalytics.removeWebview(webView)
4. Shared Keychain (optional).
If you provided a shared keychain access group.
Set Keychain Sharing
to ON
in the target Capabilities settings
To get a good measure of the usage, your application should send a tag every time a new view or page of content is shown to the user. This tag should contain information about what content the user is seeing. For example when the user opens the application and its main view is shown, a tag should be sent. When the user shows a list, an article, a video or some other page in your application, another tag should be sent, and so on.
Streaming content is measured differently from regular content pages. “Stream started” is defined as when the actual content starts playing, after any pre-roll material that may precede it.
You need to use a unique value for “Stream started”, and use that value consistently across the app. We recommend that you synchronize this with the value you use to track “Stream started” on the web. Our recommendations is that you use one of the following values: play
, stream
or webbtv
.
The framework can help you with the whole process of sending them to the server. The only thing it needs from you is for you to tell it when a view has been shown, and what content it has.
To send a tag:
TSMobileAnalytics.sendTag(withCategories: ...,
contentID: ...) { (success, error) in }
- Categories is an array of strings.
- Id is a string with the identifier of the current content.
Before the app is submitted to App Store, tests need to be performed according to instructions provided by Kantar Sifo. To validate that SDK collect panelist data properly. Please contact Kantar Sifo.
Please send any questions or feedback to:
[email protected] +46 (0)701 842 372
[email protected] +46 (0)8 507 420 00