Data not populated in the Report Suite, when sending from iOS SDK 4.0

[#1]

Hi,

We've implemented tracking for our client's mobile application using the new iOS SDK 4.0.2.

Everything looks like it is sent out fine (200 in return) when we test using Charles or Bloodhound, and the configuration also looks correct (we have checked that the report suite is ready for offline tracking).

The output from Charles looks like this:

<transaction status="Complete" method="GET" protocolVersion="HTTP/1.1" protocol="http" host="metrics.ourclient.com" actualPort="80" path="/b/ss/ourclientrsid/0/OIP-4.0.2/s76645163" query="AQB=1&amp;ndh=1&amp;pageName=presenter&amp;ce=UTF-8&amp;aid=13D9916EE23C4340-1A7C95AFC9BC1A50&amp;c.&amp;a.&amp;DeviceName=iPad2%2C5&amp;Resolution=768x1024&amp;OSVersion=iOS%207.1&amp;AppID=ourclient%201.4%20%28223%29&amp;CarrierName=%28null%29&amp;.a&amp;.c&amp;t=00%2F00%2F0000%2000%3A00%3A00%200%20-120&amp;AQE=1" remoteAddress="metrics.ourclient.com/66.235.139.205" clientAddress="/172.16.2.44" startTime="2014-05-21T09:08:00.199+02:00" startTimeMillis="1400656080199" dnsDuration="452" connectDuration="206" requestBeginTime="2014-05-21T09:08:00.857+02:00" requestBeginTimeMillis="1400656080857" requestTime="2014-05-21T09:08:00.857+02:00" requestTimeMillis="1400656080857" responseTime="2014-05-21T09:08:01.057+02:00" responseTimeMillis="1400656081057" endTime="2014-05-21T09:08:01.058+02:00" endTimeMillis="1400656081058"

And the configuration file is currently this: 

{
"version" : "1.0",
"analytics" : {
"rsids" : "ourclientrsid",
"server" : " metrics.ourclient.com",
"charset" : "UTF-8",
"ssl" : false,
"offlineEnabled" : true,
"lifecycleTimeout" : 150,
"privacyDefault" : "optedin",

}

I have also attached a screen dump from Bloodhound.

Any help or pointers would be greatly appreciated.

FYI: We have created a ticket, but no response yet.

Thank you in advance,

Robert

[#2 · Accepted solution]

Robert,

The screenshot that you provided does not show the variable ts. This variable indicates that the app is set up for offline tracking. With that said the config file that you posted indicates that you have set "offlineEnabled" to True. Are we sure that is the config file that is being used?  Is the application target pointing to a dev config file or something? To test this can you maybe change the rsid in that config and verify it changed in the hit in bloodhound?

Hunter Peterson
Mobile Engineer

Adobe Marketing Cloud

[#3]

I am also seeing the same issue on our side - Bloodhoud is populating and the RSID matches that of the suite name in Omniture but no data is being populated on the front end.

Would appreciate any help here asap.

Thank you

Sivaram

[#4]

Thanks for your reply.

Nope, we're not getting any hits in at all.

We have enabled the mobile reports etc., and double checked if the report suite is time-stamped enabled.

Regarding the proxy configuration, could you elaborate on that? We're also discussing whether it could have anything with the ssl/privacy setting, but shouldn't the server reject the call if this is set wrongly?

[#5]

Hi Hunter,

You are correct, it was the missing ts variable that did it. After double checking the config file, data is now populated in the report.

Thank you all for you help and pointers,

Robert

[#6]

Are you getting any data at all in your report suite? Run a visits report with hour granularity to see if any hits are making it to data collection. If you don't even see visits, it is likely that the hits aren't making it to the network due to proxy configuration.

If you see visits but not any mobile metrics, make sure that you have enabled the mobile reports: http://microsite.omniture.com/t2/help/en_US/mobile/ios/analytics.html

The output in bloodhound and your configuration look correct, so I don't think the issue is in your app code.

@Gigazelle, offline tracking is enabled ("offlineEnabled" : true), and it sounds like they've already verified that the report suite is timestamp-enabled (though it never hurts to check this again).

[#7]

What is the track offline variable set to? The report suite might not match the timestamped hit backend setting.