The "event" doesn't have to be in the s.products string. It can be standalone too, e.g. s.events = "event123". It depends on the use-case, but from @gkrish12345 original post, it's not clear how "event" should best be set. (Also @jeffbloomer, "evar2" should be capitalised as "eVar2" in your example ...

Can you show screenshots of your Web SDK extension's configuration? That might help us to  better troubleshoot your issue.

Don't inspect the adobeDataLayer array directly. Instead, log adobeDataLayer.getState() to see the latest, computed state of the data layer when each event occurs.

Your "Test environment" would fall under Development. In AEP Tags (a.k.a. Adobe Launch), you can only create new environments under Development. In your workflow, when you create a library, you need to assign an environment to it. So you'd assign "Test environment", so that your library's changes ge...

Usually, pushing the attribute into the data layer is the effective way to do it. Your Content Management System (CMS) should allow authors or other authorised roles to set the category for each piece of content. With that, your developers should then be able to read the content category from the CM...

You don't. You setup segments based on the reported data that you see in AA itself.

There probably isn't because every campaign would normally be measured against different dimensions and metrics. Even the same organisation may not have the same campaigns running all of the time. So you have to build your own dashboard based on your campaign's own objectives.

You can't sum up App Users just like that. Consider a user called Tom. He uses your app on 1 Feb, 4 Feb and 10 Feb. He's one App User in total. But he would also be counted as one App User on 1 Feb, 4 Feb and 10 Feb.

According to the extension's source code at https://github.com/adobe/reactor-extension-core/blob/bac916b0ca0c798a205f662cb47c8558e845ed8e/src/lib/events/blur.js#L16 , this event gets triggered by the browser's document "blur" event, which should happen when the current window (or tab) is not the foc...

My bad, sorry