Hi everyone,
Myself and my colleagues are currently in the design stage of our event-based datalayer development for our Adobe Experience Platform migration. I just wanted to get the community's view on the benefits or drawbacks of using separate event names for pageview tracking on pages where additional data variables will be tracked, in conjunction with global variables.
Currently if we use the same data layer event name ‘PageView’ for all pages, this would mean we would need to add a lot of custom code to the data elements used in the PageView event XDM object to ensure the correct data variables are captured at the correct stage.
Ideally, we want to avoid having one rule for each page as these rules will need a large number of conditions to effectively track the correct data points for each page. For this reason, we have explored the custom code option to ensure certain variables only fire on certain pages and only one rule would be required to track all pageView data.
The concern we have for using one PageView event name and writing custom code for the additional variables required on specific pages is that this will create a lot of technical debt for us.
On the other hand, if we use a different event name for these specific pages, for example ‘pageView_thankyou’ for our Thank you page, where we need to track additional data on top of the global variables, then we could just create an XDM object for the rule that is triggered by that event name for a specific page. We would still have a rule for each page but these rules would not need any conditions because of the unique data layer event name.
Since the name of the event doesn’t dictate if the event would be tracked as a page view tracking or link tracking, I’m leaning towards this option because of less technical debt to manage going forward. But it would be helpful to know others’ thoughts and how they managed this situation. Is there a best practice route to follow in this situation?
Many thanks
