Hey @Hey_John, I doubt this parameter is still valid in the case of WebSDK, but I'll see what I can find.

This is a bug and has been logged to the product team. If you haven't created a ticket, please create one from the Admin Console to get the latest update on the fix. However, I will try to update here once this is fixed.

In WebSDK, it is done using appendIdentityToUrl. Here's the reference for the same - https://experienceleague.adobe.com/en/docs/experience-platform/web-sdk/commands/appendidentitytourl 

The "Enable Japanese Keyword Processing" setting is used to properly determine if Japanese search engines are providing referrers in SHIFT_JIS or EUC_JP character sets, thus it is critical to be enabled for sites that have referrers from Japanese search engines. There is no direct documentation for ...

Yes, I believe so; this should ideally mean after Page A (pageview call), the next hit should be Page B.

Hey @Pradeep_Kumar_Srivastav, You can follow this documentation of data source for summary data upload - https://experienceleague.adobe.com/en/docs/analytics/import/data-sources/overview or you can explore the API part as well - https://developer.adobe.com/analytics-apis/docs/1.4/guides/data-sources...

This is just an icon to denote it is a metric. ' Likewise, below one denotes Dimension:  

Hey @skatofiabah For metrics, you can refer to -https://experienceleague.adobe.com/en/docs/analytics/components/metrics/overviewYou might need to go through the description for each metric under this section.Likewise for dimension you can explore this documentation: https://experienceleague.adobe.co...

This should help -You can find the above here - https://experienceleague.adobe.com/en/docs/analytics/analyze/analysis-workspace/components/apply-create-metrics Likewise, you can explore more under Components sections to explore more on Dimensions and Segments: 

If Page A and Page B must happen in consecutive pageviews, then ideally a sequential segment where Page equals A > Then after 1 Page view > Page equals B should yield the expected results. I don't think using 'Within 1 one-page view' is valid in this use case.