I have a scenario where I want to capture and manipulate the variables from link call before sending to adobe.
js page variable:
I am getting this data variable in a link call. I want to manipulate it in an extension before sending it to adobe.
Which scope should I use for the extension?
Solved! Go to Solution.
01-31-2023 01:57 AM - edited 01-31-2023 01:58 AM
You have three choices that would technically work:
Both options 2 and 3 feel like they'd be suitable here. You should select option 3 if other tags need to receive the same data without the modifications you're proposing to make, and you should select option 2 if you want to be able to make the modified data available to other tags (for example to maintain consistency across different reporting mechanisms).
In general I find it better practice to maintain a single event payload across multiple tags so that there aren't vendor-specific overrides that potentially put data out of sync across different technologies, but if it really needs to just be changed in the Adobe tag, then the tag-scoped extension is best.
01-31-2023 07:33 AM - edited 01-31-2023 07:34 AM
Thanks you. Looks like I can use the 'After Load Rules'.
Does the utag.js script re-executes from the beginning for a link call?
How can I make my extension to run only on a link call? Can I use utag_data.tealium_event in 'After Load Rules' extension?
Within the extension conditions, you can specify the prerequisites for the extension being executed. In order to just scope an extension to link events, you can use the condition "(UTAG) event (js) equals link", otherwise aliased as ut.event, which then means that the extension would only fire if it's a link rather than view event. You can further constrain the trigger using the conditions to cause it to only run when specific values of other fields are set if required.