Can I use Data Feed to find out Page Event Trigger?

[suchindra]

I am currently exploring the use of Page events to develop a calculated metric that will help me better understand the intricacies of these events. As part of this process, I want to perform tests on the metrics I've designed. To do this effectively, I need to identify the specific actions or conditions that trigger a page event to activate. What approaches or methods would be most effective in uncovering these triggers?

Can I use Data Feed for this purpose?

[Deepika_S_V]

The Data Feed tells you what happened (e.g., event5 fired on a page at a certain time), but it doesn’t tell you why or how it happened (such as a button click or menu open). To find triggers, you need to use browser debugging tools.

[Isha__Gupta]

Hi @suchindra ,

As mentioned by @Deepika_S_V , to identify the events or triggers for your page events, you would need to use browser tools. One thing you can do is enable browser in debugging mode by typing _satellite.setDebug(true) in the developer console. Enable preserve log. Then observe the triggered rules when you click/hover on buttons or navigate between pages. This will tell you which rule is triggered by which page action.

One more thing you can do is observe Event Listeners associated with each event type and you can then tie them back to triggers set up in your tag management rules.

Hope this helps!

Best,

Isha

[Jennifer_Dungan]

One thing that I did in my Launch setup was to set up some "runtime" Data Elements:

For example:

Then I configured a HIT based eVar (to make use of the longer character count) and set the runtime variables on every rule:

The full value for reference is

%runtime:PropertyId%|%runtime:BuildDate%|%runtime:RuleId%

---

This way I can see in my data what Property, BuildDate and Rule ID was used.

Note, that every version of a Rule has a different ID... so if you go back into Launch and open the specific rule id using the URL:

https://experience.adobe.com/#/@orgname/sname:prod/data-collection/tags/companies/COxxx/properties/P...RLREPLACETHISVALUE

You will get the Revision Snapshot:

I use the ID, incase the Name changes (which I do to reflect change - I use a naming convention that includes a designation of what the trigger is (like CC for custom code, CE for click element, DR for dom ready, etc, plus information about what the rule is doing, or to what element, and also shortform list of what the rule is impacting AA for adobe analytics, for FB for facebook pixels, etc) So my names do tend to shift over time... but maybe your names are more stable... I have considered adding names to my solution...