Adobe AEC Mobile SDK flowchart

[jaishal]

Hi,

Does anyone have flowchart like diagram for Adobe Experience cloud Mobile SDK flow like how the data is collected and send to Adobe analytics?

[FarazHusain]

Hye @jaishal This should help:

Additionally, you can review this one too- https://developer.adobe.com/client-sdks/home/getting-started/#integration-using-experience-platform-...

Here's the complete workflow - https://developer.adobe.com/client-sdks/solution/adobe-analytics/migrate-to-edge-network/#workflow-c... including how different extension send data in case of Mobile SDK.

[jaishal]

Hi @FarazHusain ,

Thank you for the above information. Actually, i am looking for AEC Mobile SDK data flow before AEP existed. The one you shared is the migration to AEP. 

[FarazHusain]

Do you mean ACP or 4x SDKs?

[jaishal]

Adobe Mobile SDK's

[FarazHusain]

Adobe Mobile SDK has a different version i.e. Experience Platform has 1.x, 2.x, 3.x; and then we used to have Version 4 SDKs if you're looking for Version 4 or ACP ones here, then I'm afraid these are deprecated and archived. I only see migration guides for these. 

[Jennifer_Dungan]

I don't have a flow chart per se... but we are still using the ACP SDK (the version not using the Edge server or XDM Stream).

Do you have a specific question that I can maybe answer?

[jaishal]

Is there any out of the box dimension from Adobe mobile SDK to show how many times the app was downloaded ?

[Jennifer_Dungan · Accepted solution]

So there is a "First Launch" metric, which is essentially an "install" (which is part of the lifecycle metrics)... (along with Launches, Upgrades, etc)

Now, you have to keep in mind that data will only send when the app is open...

So

Scenario 1:

• User Downloads the App
• User never opens the app

Scenario 2:

• User Downloads the App
• User opens the app right away
  • Lifecycle Metrics (if enabled) should send:
    • Launch Event
    • First Launch Event
• User uses the app a month later
  • Lifecycle Metrics (if enabled) should send:
    • Launch Event
• User Updates the App a month later
  • Lifecycle Metrics (if enabled) should send:
    • Launch Event
    • Upgrade Event

Scenario 3:

• User Downloads the App
• User opens the app for the first time a month later
  • Lifecycle Metrics (if enabled) should send:
    • Launch Event
    • First Launch Event

This should track only 2 "First Launches"/"Installs", since scenario 1 never opened the app... 

In scenario 3, the "install" (aka First Launch) is actually delayed by a month, since the app wasn't opened.

In scenario 2, I show an install, a launch and an upgrade... so your "Launches" for that user would be three over the 2 months, there would be 1 install (First Launch), and 1 Upgrade.

[jaishal]

Hi Jennifer, 

Thanks for the explanation. Which dimension can be used to determine from which which country the customer installed/launched the app? My App is canada based and i want to check the customers installing the app from different countries around the world

[Jennifer_Dungan]

You should be able to break these events down by the GeoLocation metrics, which are based on the user's IP address.

So dimensions like:

• Countries
• Regions
• Cities

Now, if you have enabled IP Obfuscation, this might render these unusable?? I am not sure if the Geo Location is calculated before or after the IPs are obscured for privacy (this isn't something we have done, so I haven't see what happens)... likewise, if you are using the "Hide Last Octet", this may reduce the accuracy of the locations, but country should be okay, I think this would mostly be at the city level.

Now, a few caveats to this... the IP is usually based on the user's ISP, which may or may not be located in the same city... some provider have more granularity then others... but if you are looking at Country, this again shouldn't affect you....

But use of VPNs (either work, or personal), might route people so they appear as another country... there's no real way around that.

The GeoLocation dimensions are available for both web and app.