Here are a few links that we referenced during this session: Documentation for the Data Element Assistant extension: https://exchange.adobe.com/apps/ec/101413 Documentation for the Web Vitals extension: https://exchange.adobe.com/apps/ec/106769/web-vitals Documentation for the Event Forwarding feature, available to Real-Time CDP customers: https://experienceleague.adobe.com/docs/experience-platform/tags/event-forwarding/overview.html?lang=en

I'd say both are options depending on your long-term goals. You may want to utilize a single schema if you foresee a lot of overlap in terms of the types of data that you collect between the two sites. If there's a very low number of custom fields that overlap between the two, and you don't ever foresee a world where the data from the two sites should be merged/combined for analysis/activation across sites, then it may make sense to keep them separate. IMO, most likely, a single schema will work...

Great question! You can actually return the entire object using a Data Element Type of JavaScript Variable like this: Then Map that Data Element to the Data Section of your Web SDK Event in the Rule Action

There was a request for the Javascript code that I'm using to set a GA Client ID. Keep in mind that I: 1. Haven't tested this with GA4 and so I don't know if a different identity format is expected. So check that if you are GA4'ing. 2. Am not a software engineer. So please don't make fun of my code 🙂 OKAY. With that out of the way, here's the Javascript I'm using in a client-side Adobe Tags data element in order to set a GA Client ID. I'm then passing that into an XDM field to my Web SDK event,...

There was a request for the Javascript code that I'm using to set a GA Client ID. Keep in mind that I: 1. Haven't tested this with GA4 and so I don't know if a different identity format is expected. So check that if you are GA4'ing. 2. Am not a software engineer. So please don't make fun of my code 🙂 OKAY. With that out of the way, here's the Javascript I'm using in a client-side Adobe Tags data element in order to set a GA Client ID. I'm then passing that into an XDM field to my Web SDK event,...

Unfortunately this would take a *ton* of reprocessing of *all* of the data in every report suite that you add. To successfully do this, customers today are utilizing Customer Journey Analytics, where multiple report suites can be merged together for analysis. More details here: http://adobe.ly/aacja

Thanks for following up @JSP2 I've just heard that: In general, processing rules are not affected. But you will lose access to editing mobile services-created processing rules after the sunset date. I read that as: there's no better time to migrate your rules from Mobile Services to Processing Rules than the present. Don't forget to QA with Real Time Reports and Griffon: https://experience.adobe.com/griffon