christa_mabee

Re: Unique visitor inflation after upgrade - Adobe Analytics 15-10-2015

That page describes web traffic, not app traffic, and this was around a release and not a holiday.

151

Unique visitor inflation after upgrade - Adobe Analytics 15-10-2015

We just updated an app from 1.2 to 4.0, and saw the number of unique visitors immediately spike at release. I'm trying to figure out why. We weren't setting the visitor id before, and aren't (intentionally) now either. To make sure I did a string search on the codebase and didn't find any references to visitorID in the previous implementation or to setUserIdentifier in the new one. We don't clear the SharedPreferences at upgrade, we update some of our own stored strings but those would be in a s...

212

Re: Mobile App Acquisition - race condition in Android - Adobe Experience Cloud Mobile 15-10-2015

Aha! No, offlineEnabled is false. I'll give that a shot.

347

Re: Mobile App Acquisition - race condition in Android - Adobe Experience Cloud Mobile 15-10-2015

Using offlineEnabled plus a timeout of 10 didn't help, but that plus a timeout of 60 did. Unfortunately, due to the need to continue tracking un-upgraded versions of the app, we can't turn on offline tracking on the report suite. Apparently that'd cause the server to drop all of those tracking requests, since they don't include a timestamp. So... I shall continue to dig. Edit: actually, would it hurt anything to enable offline tracking in the app but not on the server?

347

Re: Mobile App Acquisition - race condition in Android - Adobe Experience Cloud Mobile 15-10-2015

Hi Hunter, thanks for looking at this. My concern is that the longer that timeout is the more likely it is that another tracking event will occur before that lifecycle hit gets sent. That's why I'm calling it a race condition. There is no way (that I can find) to detect when that InstallEvent hit was sent, I can track when the app reaches Analytics.processReferrer() but that returns void immediately. There's no indication that it's now safe to start sending other tracking events. If it went out ...

351

Re: Mobile App Acquisition - race condition in Android - Adobe Experience Cloud Mobile 15-10-2015

Given that our problem is a race condition where other tracking gets sent before the acquisition hit and thus absorbs the campaign data (why does that happen?) I don't think waiting even longer to send the acquisition hit would make the problem less frequent. The information is definitely present and in the intent provided to Analytics.processReferrer().

348

Mobile App Acquisition - race condition in Android - Adobe Experience Cloud Mobile 15-10-2015

I've implemented Mobile App Acquisition as instructed here: https://marketing.adobe.com/resources/help/en_US/mobile/android/acquisition.html I've run into the situation where sometimes the InstallEvent request fails to pick up any of the campaign information. It is always coming through, this is apparent because I save that info when the INSTALL_REFERRER Intent is received and then add it to a custom tracking even that happens later. Instead those attributes get automatically tacked on to whatev...

1.0K

Re: Difference between resume/launch in 2.x Android SDK versus 4.x - Adobe Experience Cloud Mobile 15-10-2015

The migration documentation does not cover how resume or launch were handled in 2.x.

323

Difference between resume/launch in 2.x Android SDK versus 4.x - Adobe Experience Cloud Mobile 15-10-2015

In the 4.x SDK, if the app launches from the background less than five minutes from the previous launch, it counts as a resume, but past five minutes (by default) it counts as a new launch. Was it the same way in 2.x? Was there a time distinction between resume and launch, or some analogue of the lifecycleTimeout field? Also: where can I find documentation about 2.x? I have some legacy code that had it (which is no longer in production) and am frequently asked about how things have changed. Ques...

521

Learn

Documentation

Community

Support

Resources

Adobe account

Adobe