![]() Those options are a bit more work - And it would be easier if you already have something in your event to play from though. Patented, permanently affixed and bar-coded metal tag that actively deters equipment theft. When the tag fires for the first time, we set has_xxx_fired in utag.data, which we then read on subsequent events, and we dont let the tag fire a second time. Ten Pack of STOP Security Plates offers significant savings. You can change out the variable name "has_xxx_fired" with anything you like! Then add this code to a JavaScript Extension scoped to "Before Load Rules"ī.has_xxx_fired = _xxx_fired || false This would involve modifying the template though, which many people prefer to avoid.Īdd this code to a javascript extension which is scoped to the tag. Tag Template - Some of our tags already have this functionality built in - lots of them will make use of a "u.initialised" flag which you can use.Thoughtfully designed for retailers and shoppers combined, it’s a seamless experience for your customers and team a great addition to any store. TAGR is completely web-based, meaning there’s no app for your customers to download. ![]() If the event data being sent for both of your view events is identical - and there isn't and easy way to be able to identify whether this is the second event on the page or not - You could look to add some functionality in one of a few places WHY TAGR A powerful tool for your retail business. Typically you would only have a "view" event fire once per page, there are some exceptions - but it may be worth confirming if you want to be using "utag.view" instead of "utag.link" ![]() The best way to prevent a tag from firing would be to adjust the loadrules to only be met for specific events. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |