Multiple extensions vs multiple tags

[TravisTook]

I was wondering if it was better to use one tag loaded on all pages, using a group of set data extenstions to dynamically create the data mappings based off the page type, or multiple tags each loading on a specific page type with static data mappings?

[robert_sabec]

@TravisTook

Most if not all of the marketplace tags are designed to have dynamic values from different pageTypes mapped to one tag.

Robert

[TravisTook]

Just to be clear, @robert_sabec, what I'm talking about is something like mapping 'product_list_price' to the tag's value variable on product pages, and mapping 'order_subtotal' to the same value variable on cart pages.

Currently I have one tag with some UDO variables mapped to each of the tags outputs. Then I have a separate setData extension, scoped to the tag, for each pagetype. These extensions set the values of the mapped UDO variables to be the values I am needing to send for that pagetype

[mvenkatesan]

Hello @TravisTook

Based on my understanding of your question, having 1 Tag and multiple extension would be a good option (my personal approach).

Example: Today you have 5 variables for 5 differnt pages you end up creating 5 tags for each page, in case if your variable count increases each time you have to make changes accordingly for all those tags or if a new page is added you have to have addditional tag for thoses as well.

if you have one Tag then it will be easy to manupulate the data with differnet type of extensions and the same data can be used in multiple areas as required.

Hope this helps and please do let me know if you need more info.

Thanks!