There are two modes of integrating Dynamic Yield on mobile. One is purely based on APIs, and the other is a mobile SDK. This article aims to help you understand the pros and cons of each integration method.
| API | SDK | |
|---|---|---|
| Section | Same section for both Android and iOS (can also be together with the web) | Different sections for Android and iOS |
| User and session ID |
Script-based mode: Managed by Dynamic Yield API-only mode: Setup by website owner |
Managed by Dynamic Yield |
| Context | In the pageview and campaign calls | Implemented separately |
| Events | Reported by the website owner | Reported by the website owner |
| Engagement | For all campaigns | For recommendations |
| Pageviews | Reported by the website owner | By Dynamic Yield |
| Versions | -- | Need to update the SDK |
| Logs | Appear in Admin | Do not appear in Admin |
| On-the-fly campaigns (messaging only) | Need a developer | Can be done by Marketing |
| Content delivery | API-based | API or CDN-based (or both; depends on campaign type) |
| Push notifications | Available | Available |