Attached is week 4's Toolkit, sorry it's a little late. This toolkit goes more deeply into Launch Tags- setting up, publishing, extensions usage, etc. Let me know if you have any questions!

We're on to Toolkit #3! Plus information about a voucher for the exam fee.Attached is the toolkit for our third week. Section 3.1 has information about implementation through Launch Tags, both for the webSDK and the older appMeasurement approach, either through the Tags Analytics extension, or vanil...

Attached is the second Toolkit. This one has a lot of material in the first half on Adobe Workfront- this won't be featured much in the exam, but it'd still probably be a good idea to get loosely familiar with it. However, there is a section on Adobe Analytics Documentation that you absolutely shoul...

Hello, Everyone! Attached is the Toolkit for the first Module, "Understanding Analytics in the Adobe Experience Cloud Ecosystem". It includes 3 sections:1. A general "what is Adobe Analytics" with a lot of good links for learning the technical side of Adobe Analytics2. Setting Analytics and Experien...

@tim_funk Thank you! I had tried to find any previous ideas (I mean, surely, someone had suggested it before) but couldn't find it, so thank you for the link.

Description - When I search in Launch, I'd like to be able to know what rule a rule component belongs to.Why is this feature important to you - Right now, if I need to find the rule where prop17 is set to "resources", or I need to make a change to every rule that references the Criteo marketing pixe...

Add in Activity Map region as one I'd like to classify

Thanks for that- that makes sense. I've come to expect data elements to always (re)evaluate at the time my rules run, but it sounds like since we're using the data element in a configuration component, the data element will only evaluate when that extension configuration component runs.So it's bigge...

Ah, fair, it appears it will set on s.tl beacons if you don't ever use Clear Variables; I should have caught that in my little demo site. I guess the key difference is that I do count on dynamic values (especially on single page apps), and I do use the Clear Variables action (especially on single pa...

I see what you're saying, but... they're not tracked with every beacon. They're never tracked on s.tl beacons, and if you ever clear out variables (as is best practice) then they're not tracked on that DOM ever again. I think calling them "global" is very misleading, because they really are just "gl...