Can you double check the syntax? I see some differences in the snippet that you have added in the question description. Can you double the check the parenthesis. MobileCore.registerExtensions(extensions, {MobileCore.configureWith(appId: self.LAUNCH_ENVIRONMENT_FILE_ID)if appState != .background {Mo...
I think we would need logs, if configuration is correct then there must be something within the app blocking the calls. Apart from lifecycle calls, do you see any other data making to the reports from iOS App?
I haven't tested passing additional context data in lifecycle calls, but if it breaks the lifecycle metrics then this is definitely something that can be checked internally.
Hey @bjoern__koth I found this connector which you can check - https://enautics.com/software-platforms/segmentsync/ but not certain if this still works. They do have a support center - https://enautics.zendesk.com/hc/en-us where you can check on integration part.
Hey @vallus additionalConextData:nil shouldn't be the problem here as this is an optional parameter to pass a dictionary of additional data that will be attached to the lifecycle event. I suspect it something else. Do you see any sort of errors in the debug logs? If we can get logs from the App it c...
Hey @Saloni_Gakhar This kind of tracking can be done AppsFlyer integration. I'm unsure if this can be passed as context data in lifecycle call. I think the best approach would be Appsflyer and you can check the following documentation: - https://support.appsflyer.com/hc/en-us/articles/115003326706-A...
Hey @Madhusudan_S This thread might help - https://experienceleaguecommunities.adobe.com/t5/adobe-analytics-questions/implementation-of-consent-mode-google-ads-adobe-tms/m-p/608366
The product profile seems to be correct. We might need to take a further look. Can you please log a support ticket via Admin Console with all these details?