@dwright  I am referring to your tutorial on custom AT.JS events, where one could use evens like at-content-rendering-succeeded for fetching user attributes in response tokens. We are currently just listening to the 'at-content-rendering-succeeded' in the web to refresh a token. Since we have migrat...

Hi @dwright    We implemented the WebSDK on our lower environment but the interact calls get a 207 response instead of 200 and I see the below in the alloy interact logs. hoping you have a quick help for me here   {events: [{,…}], query: {identity: {fetch: ["ECID"]}},…}events: [{,…}]0: {,…}data: {__...

Hi @dwright    Yes the plan is to get rid of appmeasurement on the pages in scope from the tag management system after 3 weeks. On your suggestion about Target activities, would it work if we pointed them to the new report suite(one for WebSDK) on the go live date?    Also another things that not cl...

Hi @dwright  Thanks a ton for the quick response. Further to this, I wanted to clarify that we would ideally want to keep appmeasurement and websdk for Analytics but only Websdk for target and reading the migration of planning page; it tells me that appmeasurement for analytics and websdk for target...

HI @dwright    We have planned to GO Live with WebSDK but also keep AppMeasurement.js active for 3 weeks after WebSDK go Live. The idea was to study if WebSDK and AppMeasurement.js collect the exact same data in 2 separate Analytics reportsuites. And later the plan was to remove appmeasurement.js wh...