- Mark as New
- Follow
- Mute
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report
I wouldn't expect a difference between how iOS handles Lifecycle vs Android, but I don't feel confident without digging into the app's server calls and data.
If those Unspecified values show Lifecycle data when broken down by Custom Links, I'd feel confident that's the root cause.
The reason some global variables have Lifecycle data and others don't may have something to do with expiration of those eVars vs other eVar expirations vs props. If any of your eVars are set to expire at the Visitor granularity, then the values would persist 'through' the Lifecycle metrics getting fired.
Are you seeing that the context data variables that you're setting are firing in your debugger (ex: Charles) with the Lifecycle metric server calls?
Views
Replies
Total Likes