I'm trying to understand impact to A4T reporting when our app opens a webview and we pass in the MID via visitorAppendToURL function. Would the visitorapi.js generate SDID in this case within the webview page that would allow Target activities on in the webview page to remain stitched to the analytics call?
Generally speaking, the visitorAPI.js generates an SDID when the at.js fires a request from the page. So yes, a webview that has both the visitorAPI.js and at.js deployed properly and in order should have the SDID for reporting on any Target activities that fire on the webview.
Generally speaking, the visitorAPI.js generates an SDID when the at.js fires a request from the page. So yes, a webview that has both the visitorAPI.js and at.js deployed properly and in order should have the SDID for reporting on any Target activities that fire on the webview.
