Yes. Per documentation: "You can include a bundled JSON configuration
file in your app package to replace or complement the configuration that
was downloaded by using the Configure with Launch App ID approach."
Assuming that you are using 1 Launch property to setup both iOS/Android
apps - to fork data by platform you'd need to change configuration
client side to accomplish this. However, instead of splitting report
suites - have you considered using Virtual Report Suites?
Only Mobile Services (via the mobile add-on SKU for Adobe Analytics) or
Adobe Campaign Standard provide support for in-app messaging. There's
not a way to compose, publish, and report on push or in-app messages
without access to the solutions listed above.
The Mobile Services extension is only required if using one or more of
the following features: in-app messaging, push, acquisition, and
location points of interest management.If you are using the features
listed above, you'll need to create separate apps in Mobile Services and
separate properties in Launch (as you can only have one environment per
Mobile Services extension).If you are not using the features above and
are looking, solely, to setup Adobe Analytics reporting, then you may
Processing rules to map variables and metrics are always applied to a
report suite. Mobile Services UI and Processing Rules UI (within Adobe
Analytics) use the same APIs to manage rules for a given report suite.As
you point out, using Mobile Services UI requires extra steps - however,
for some users, the MS UI may be easier to use. You may accomplish
mapping in either of the two UIs you find comfortable.
Hi andersonjh - apologies for the delayed response. I'm not completely
sure what you're trying to do. Can I trouble you provide a little more
context and perhaps some end-results of what you're trying to accomplish
so we can get you a prompt response?
Thanks for the feedback - we've received this request from other
customers as well. However, unfortunately, going forward we don't plan
to enhance marketing links functionality in any way. Please contact your
Adobe CSM for more detail.
sreeg59737456 - depends on your use cases. Generally speaking, Campaign
and Mobile Services push messaging are mutually exclusive. Campaign uses
mobile app subscriber profiles as target audiences while Mobile Services
uses Adobe Analytics user segments as target audiences.
sreeg59737456 - if you have the Adobe Analytics Premium SKU,
provisioning of Mobile Services may be done by your Adobe administrator
to give you appropriate access to push, in-app, and location
services.For questions and collateral on the various messaging offerings
across Adobe Experience Cloud - I would suggest reaching out to your
Adobe CSM or feel free to send me an email - cprasad at adobe.com so I
can get you looped in with your CSM.
Location tracking precision varies based on the underlying platform
(Android, iOS) and the device settings. Location latitude/longitude, in
this case, is obtained by the app developer and passed to Adobe
Analytics using the trackLocation API. The documentation implies that if
higher orders of precision are available, they will be passed into those
variables, accordingly. For questions on what levels of precision are
available, we refer to platform/device manufacturers; and for questions
on best ...
Hi davidg31597419 - yes, that's basically what we've got for our 4x
SDKs. However, we just launched (Sep 2018) - our new major version SDKs
that supports versatile programmatic configuration options - details