The following table contains a list of frequently asked questions for Adobe Mobile Services:
Yes, we are constantly making updates in effort to get you the most feature rich, standard-compliant, and secure SDKs. We typically release a new version every month. These SDK updates are drop-in replacements (for version 4x) to aid in ease of implementation. For more information on our updates, see our Release Notes.
Our current SDKs are on version 4.11. For more information, see our Release Notes.
The SDKs for individual mobile platforms may be downloaded by visiting the Manage App Settings section.
After you create a new app report suite, navigate to Manage App Settings and configure all of the required options on the app information page. After you save your configuration, download the required SDKs from the bottom of the Manage App Settings page. The SDK will come pre-configured with the options you have saved and can be found in the
ADBMobileConfig.json file in the SDK package. If you change any SDK settings on the Manage App Settings page, make sure you re-download the SDK files or update your
ADBMobileConfig.json file with the necessary changes.
The Adobe Mobile SDKs use the standard iOS and Android network stacks. For iOS, the SDK uses NSURLSession (iOS versions 7+) and NSURLConnection (iOS versions 7 and later) which are fully compliant with IPv6. Developers who have built or use their own networking stack might want to review if there are other mitigating considerations. Here is some additional information from Apple:
If you’re writing a client-side app using high-level networking APIs such as NSURLSession and the CFNetwork frameworks and you connect by name, you should not need to change anything for your app to work with IPv6 addresses. For more information see, Supporting IPv6 DNS64/NAT64 Networks.
Lifecycle Metrics are “out-of-the-box” metrics that are automatically collected when the SDK is first implemented in your app. For more information, see Lifecycle Metrics (Android) and Lifecycle Metrics (iOS).
For more information, see Processing Rules Tips and Tricks.
Yes. The SDKs provide the ability to send data to multiple Adobe Analytics report suites. To capture data in multiple report suites by using an image request, set the multiple report suite IDs in the rsids field under analytics section in the
ADBMobileConfig.json file, delimited by commas and no spaces. For more information, see ADBMobile JSON Config.
A launch is measured by the SDK when a user opens the app for the first time or returns to the app after having been out of the app for longer than the specified timeout value. The typical timeout is 5 minutes (300 seconds) in lifecycleTimeout field, which is located in the
ADBMobileConfig.json file. A visit is a server-side calculation by Adobe Analytics and is based on the first and last data hits that are sent by the SDK without exceeding a visit timeout. Typically, session timeouts are set at 30 minutes for a report suite. Although visits come from traditional web analytics, these hits still provide valuable insights into how users enter and exit from your app.
Push notification messages have a 140 character limit. There are no limits on how many notifications might be sent or scheduled or how often notifications are sent.
Yes, we provide for a custom push payload that may coded in JSON. Android and iOS payloads are restricted to 4KB and 2KB respectively. These payloads are sent to the app via a push or a local notification. For more information, see Experience: Push Message.
Published and active in-app messages created in Adobe Mobile Services are hosted on a server with a 15MB size restriction per app report suite. While this restriction applies to message content and resources hosted with Adobe, there are no restrictions on what resources the in-app message may refer to on other hosts or those within the app.
Yes, we support custom HTML for your in-app messages. For more information, see Experience: In-App Message.
Marketers may choose any Analytics data or event that is being sent as a trigger to display in-app messages. In-app messages use triggers that happen locally on the device. If multiple triggers are chosen, all triggers must occur in the same hit for the message to display. For more information, see Experience: In-App Message.
Push messages are sent using pre-existing Adobe Analytics segments or custom segments that may be created on historic Analytics data already collected. For more information, see Experience: Push Message.
You cannot use the same in-app message, push message, or marking link name in multiple apps that use the same parent report suite or VRS. To resolve this issue, enter another name for your in-app message, push message, or Marketing Link.
There no specific restriction, but for ideal performance and due to memory restrictions on the user’s device, we recommend that you create or upload a maximum of 5000 POIs.
Yes. Adobe Mobile Services can help you build marketing tricks that help promote and drive traffic to your apps and tie acquisition campaigns to in-app analytics and conversions. For more information, see Acquisition.
You can create Marketing Links that route users to download applications from the Apple App Store and Google Play. These links allow you to attribute your success events to the downloads. For more information, see Marketing Links Builder.