@Gokul_Agiwal and @Jennifer_Dungan ,The application uses SharePoint Framework (SPFx) used for development of SharePoint Online applications.

Hi @Gokul_Agiwal , Don't have the screenshots but the application uses TypeScript instead of JavaScript for client-side programming. So the launch embed script which is JavaScript, isn't working.

Hi all, We have a application which uses typescript and are facing issues to embed the launch script. Need help on how we could do this. Thanks.

At report suite level all eVars are set to expire after visit.Code level, developer has said it's set at every hit but still we find unspecified but still will verify again. 

So we have only two success events and when we use those 2 metrics we don't see unspecified. Unspecified values only appears when visits and unique visitors metrics are used.

So the evar just has the screen names and userId...We have used processing rules completely but still face the issue. uncheck the "Show unspecified" checkbox - Yes we are aware of this and use often but the requirement is to completely avoid it from implementation itself.

We have made sure that each and every hit has a value for that dimension, whether set in the beacon or persisted from previous beacons. But still we see unspecified and when we break it with custom link it shows the value ADBINTERNAL:Lifecycle

How do we remove unspecified completely from the reports?Apart from unchecking 'include unspecified' in the report?

checked the namespace as well, it is set correctly  

Thanks @leocwlau  for sharing the article.   Will try troubleshooting the extension.