Tealium Learning Center

Extension Category Standard Data | Advanced | Events | Tag Specific | Privacy Standard Data Extensions Extension Description Crypto Enable support for cryptographic hashing. Hosted Data Layer Supplement the on-page data layer with data from your hosted data layer objects. Join Data Values Join data values together into a larger hierarchical data value. You can choose which character to use to join the data (ie /, -, : ). Lookup Table Translate values based on a lookup table. Lower-Casing Set data layer, JavaScript page, meta-data, query string and cookie variables to lower case. This is a best practice for data consistency. Pathname Tokenizer Tokenize the location.pathname attribute into individual tokens (max of 8 tokens). Persist Data Value Set a data value into a persistent cookie. You can choose the cookie name and persistence duration. Previous Page Persist the previous page name value for use on the subsequent page. Set Data Values Set or default variable values based on a condition. Advanced Extensions Extension Description Advanced Javascript Code Write JavaScript code in an enhanced editor with syntax checking, code diffs, GitHub integration, and a draft mode to safe guard your publish workflow. Channels Get a view of your customer’s journey across multiple channels. Set the Channel Conversion Credit sent to your Originator, Influencer and Closer affiliates. China CDN Deployment Determines a user's location (inside or outside China), which allows web site content to be sent to the user from the appropriate CDN. Content Modification Change the content of an HTML element. This can be used to show A/B content based on a condition. Data Validation Trigger errors for incorrect data values on specific pages. Domain-Based Deployment Load a QA or Dev version of your Tag Deployment based on hostname. E-Commerce Define a standard set of E-commerce variables such as Order Total and Product Sku List. Flatten JSON Objects Flatten JSON objects. Javascript Code (Basic) Use this customization to write custom Javascript code and have it invoked at a global scope or only for a specfic tag. Modal Offer Enables the insertion of a modal overlay on any pages to alert the user of promotions, call to actions or offers. Split Segmentation Randomly assign your visitors into segments. Can be used for A/B testing or Sampling. View-Through Tracking Configure a cross-domain view-through tracking pixel for use in your ad creative. (Requires the Manage Account permission) Events Extensions Extension Description jQuery clickHandler (jQuery v1.6 and below) Trigger tracking events when elements are clicked. jQuery 1.6 or earlier required. jQuery onHandler (jQuery v1.7 and up) Trigger tracking events when web page elements become visible such as LightBoxes or clickable elements. jQuery 1.7 or later required. Tealium Events Defines standard conditions for the most commonly tracked events. Adds the tealium_event variable to your data layer, to be passed along to Customer Data Hub via the Tealium Collect tag or to help simplify tag mappings, load rules, or other conditions. Link Tracking Enable and configure link click tracking. Tag Specific Extensions Extension Description Adobe Target Tag Content Modification Use this extension with the Adobe Target tag to change the content of an HTML element. This can be used to show A/B content based on a condition. Currency Converter Convert dollar amount totals between different currency types. If conditions conflict, the last Conversion definition will be used. (Requires Tealium Currency Converter tag) Privacy Extensions Extension Description Do Not Track Enable Do Not Track support. Privacy Manager Enable Tracking Opt Out by Tag. Tracking Opt Out Enable Tracking Opt Out. Usercentrics V1 Supports the Usercentrics Consent Management Platform (CMP), v1 to enforce end-user privacy preferences (consent) and ensure that only consented services have the ability to transmit data to third parties. Usercentrics V2 Supports the Usercentrics Web CMP, v2 to enforce end-user privacy preferences (consent) and ensure that only consented services have the ability to transmit data to third parties. ... View more

Notes on ActionScript When it comes to integrating Tealium iQ (and just about any tag-based third party vendor) into Flash, we typically divide the world into two pieces. Flash applications that support ActionScript 3.0 and up and those that don't. In this post, we will look at the two different approaches to integrating Tealium iQ into a Flash video player based on the above division. In the examples below, we will be using the data sources recommended in the "Tracking Video with Tealium iQ" post to build out our tracking calls. ActionScript Versions 1.X-2.X With pre-3.0 versions of ActionScript, there isn't a method for making tracking calls natively from within the Flash environment. Instead, the Flash application will need to make external calls to the web page's JavaScript in order to accomplish the goal of tracking events within the application. As mentioned previously, with early versions of ActionScript we can't include a native library to handle our tracking calls. So instead, we will make JavaScript calls to the webpage that contains the video player. Here is the generic structure of that type of call: getURL(‘javascript’:utag.link ( { variable_1:”variable_1_VALUE”, variable_2:”variable_2_VALUE”} ) ’); Note the following: Variables and variable values are separated by a colon ( : ) Variables are separated by a comma ( , ) ​Variable values are enclosed in double-quotes ( " ) ​Now that we have the generic structure, let's look at how we would attach Tealium iQ (and therefore your analytics tags) to a play button in a video player: In this example, we assume the simplest execution which is attaching our Tealium iQ call directly to an event on an object in the Flash player. If you have custom event handlers and event listeners built into your Flash player, you may end up building in the Tealium iQ calls as part of those. playBtn_btn.onRelease = function() { getURL(‘javascript:utag.link ( { //recommended attributes video_event:”video_play”, video_name:”My Video Title”, //the name or title of the video video_type:”standard”, //the type of video video_position:”0”, //time position of the event in seconds (could also be in milliseconds and should match units used in video_length) video_length:”60”, //the total length of the video in seconds (could also be in milliseconds and should match units used in video_position) //optional attributes video_player:”MyCo Proprietary Player”, video_category:”My Video Category”, video_subject:”My Video Subject” } ) ‘); ​ Note the following: We attached the Tealium iQ function "utag.link" to the object "playBtn_btn" and are triggering it "onRelease" Always make sure to separate your getURL for Tealium iQ onto an event handler different from other getURL calls that might be attached to that object ActionScript Version 3.X+ Starting with ActionScript 3, Flash started supporting native libraries which enables us to import the Tealium iQ functions directly into the Flash application and make our tracking calls natively from within Flash. To do this we need to: Import the Tealium iQ ActionScript library (utag.as) Import the utag class from utag.as into our Flash player Instantiate the tracking object Define the data object Define the appropriate tracking calls to objects and events within the Flash player Import the Tealium iQ ActionScript Library Our ActionScript library is very small and you could easily download and import it to your Flash player app locally, but in this example we will import the copy that Tealium keeps stored on our CDNs: //import utag.as from the CDN include “http://cdn.tealium.com/universal_tag/libs/com/tealium/utag.as”; Import the utag class​ //import the utag class from utag.as import com.tealium.utag; Instantiate the Tracking Object //create the tracking instance var utagObj:utag = new utag(); Create the Tealium Data Object (utag_data) //create the data object var utag_data = new Object(); Populate the Data Object and Trigger the Tracking Event​ //populate the data object and trigger the view playBtn_btn.onRelease = function() { utag_data.video_event = “video_play”; utag_data.video_name = “My Video Title”; utag_data.video_type = “standard”; utag_data.video_postion = “0”; utag_data.video_length = “60”; utag_data.video_player = “MyCo Proprietary Player”; utag_data.video_category = “My Video Category”; utag_data.video_subject = “My Video Subject”; utagObj.handler.trigger(“view”, utag_data); } And that's all there is to it. If you have more specific questions about using Tealium iQ from within Flash, please contact your Account Manager to schedule a working session. ... View more

This article explains how the data layer works for websites by clarifying the various related terms and providing an overview of the flow of data from your website to your vendor tags. First, let's define the various terms related to a website data layer and your installation of utag.js: Universal Data Object, UDO, utag_data  The JavaScript object implemented on your site to contain dynamic values that describe the page and visitor. Learn more about how the UDO works. Variable Types  Data available directly from your web page (other than your customized UDO) via DOM Data, Query Strings, Meta Data tags, Cookies, and JavaScript variables. Read more about the data layer variable types. utag.data  The final data object combining variables from the UDO with all other variable types available from the page. This data is used to evaluate load rules. Learn more about the built-in variables available in the UDO. "b" object  An internal JavaScript object that is a copy of utag.data to be used for each individual vendor tag. The "b" variable can be referenced in JavaScript Extensions. Read more about the "b" object and how it's used. This graphic shows how individual variables come together to create your Data Layer and how that data flows out to your vendor tags. Data Layer Flow When a web page with Tealium iQ is rendered in a visitor's browser, this is how the data moves. All required Variables are identified Variables are combined into utag.data utag.data is copied to the locally-scoped 'b' object as needed Extension operations may be performed on Variables Load Rules may evaluate Variable values to determine which Tags to load and fire Final Variable values are mapped to destinations in Vendor Tags Vendor Tags fire and pass Variable values to your vendors Read more about the order of operations of the Tealium Javascript library.   ... View more

Google Analytics (gtag.js) Google Analytics (gtag.js) Tag Setup Guide Google Analytics (analytics.js) Google Universal Analytics (analytics.js) Tag Setup Guide Google Universal Analytics: Event Tracking Google Universal Analytics Tag: Advanced Mapping Setting Up Google Universal Analytics Cross-Domain Tracking Google Universal Analytics Tag: Enhanced E-Commerce Transitioning from Google Analytics (GA) to Google Universal Analytics (GUA) ... View more

website: www.act-on.com   SAMPLE CODE SNIPPET <script type="text/javascript"> /* <![CDATA[ */ document.write ( '<img src="http://www.tealium.com/acton/bn/1234/visitor.gif?ts='+new Date().getTime()+'&ref='+escape(document.referrer) + '">' ); /* ]]> */ </script> Tealium iQ Configuration The ActOn tag requires little in the way of configuration. Navigate to the Tags tab, and click "Add Tag" Search for "Act On" Add the ActOn tag by clicking the "Add" button In the Tag Configuration Wizard, give the new Act On tag a title that is meaningful to you Enter your Account ID Enter the Path (the URL path leading to your account id e.g. http:www/tealium.com/acton/bn/1234/visitor.gif?) Click 'Next' to assign a specific Load Rule to the tag or click 'Finish' to apply the default Load Rule to this tag. ... View more

This article describes how to set up the Adform tag in your Tealium iQ Tag Management (TiQ) account. In this article: Table of Contents Placeholder Tag Tips Uses the following E-Commerce variables _corder _csubtotal _ccurrency _ccountry _cprod _ccat _cquan _cprice Divider Tells Adform which character to use to split up the pagename. The default value is the pipe character "|". Can be overridden by mapping Custom variables can be mapped to order-level or product-level. Possible values are sv[n] , svn[n] or var[n] where n is any integer from 0 to 89 . The Purchase step must be mapped using a lookup table. Step 1: Product View Step 2: Basket Step 3: Conversion (thank-you page) Custom Order / Product Vars var – Data Object Variable sv – String Variable svn – Numeric Variable Tag Configuration First, go to Tealium's tag marketplace and add the Adform tag (Learn more about how to add a tag). After adding the tag, configure the following settings: Tracking Setup ID Unique Client ID number generated by the Adform system. Page Name Unique name for the tracking point. Use variable mapping to set this dynamically. Data Mappings Mapping is the process of sending data from a data layer variable to the corresponding destination variable of the vendor tag. For instructions on how to map a variable to a tag destination, see Data Mappings. The available categories are: Standard Variable Description campaignid Tracking Setup ID/Campaign ID page_name Tracking Point Name/Page Name divider Divider E-Commerce Variable Description order_id Order ID Overrides _corder . order_subtotal Subtotal Overrides _csubtotal . order_status Order Status order_currency Currency Overrides _ccurrency . customer_country Country Overrides _ccountry . customer_agegroup Age Group customer_gender Gender product_id Array List of Product IDs Overrides _cprod . product_name Array List of Names. Overrides _cprodname . product_category Array List of Categories. Overrides _ccat . product_category_id Array List of Category IDs. product_quantity Array List of Quantities. Overrides _cquan . product_unit_price Array List of Prices. Overrides _cprice . product_weight Array List of Product Weights. step Step Values of 1 / 2 / 3 . Custom Order/Products Custom variables can be mapped to order-level or product-level. Possible values are sv[n] , svn[n] or var[n] where n is any integer from 0 to 89 . Variable Description order Order product Product var Data Object Variable ranging from 1 to 10. sv String Variable, ranging from 1 to 89. svn Numeric Variable ranging from 1 to 2. Vendor Resources Adform Test and Support Center Adform Click and Tracking Pixel ... View more

This article describes how to set up the Acoustic Digital Analytics tag in your Tealium iQ Tag Management account. Acoustic Digital Analytics helps companies measure and improve the effectiveness of online marketing programs, directly improving their bottom line. In this article: Table of Contents Placeholder Tag Tips You can map values to override values set in E-Commerce Extension (not recommended) Mapping toolbox shows 10 custom attributes for each event. Acoustic Digital Analytics supports 50 attributes. To map to a value beyond 10, edit the number in the toolbox directly To use Manual Page View tag, map value to Manual Page View Destination URL (other values picked up from standard Page View mappings) Tag Configuration First, go to Tealium's tag marketplace and add the Acoustic Digital Analytics tag (Learn more about how to add a tag). After adding the tag, configure the following settings: Tag Version: Use the External (default) option to load eluminate.js from the Acoustic-hosted CDN. This ensures you always have the latest library code from Acoustic. Client ID: First parameter to the cmSetClientID function (e.g., 89999999|SiteID). This value can also be set via mapping. Test Client ID: This is the Client ID used when a match is found in the Test Domains list. Collection Method: True indicates Client-Managed 1st Party cookie. False indicates Acoustic-Managed 1st Party or 3rd Party as applicable. Collection Domain: The target domain for Acoustic data collection requests. Cookie Domain: The domain for Client-Managed cookies (e.g., tealium.com). Test Domains: Comma-separated list of test domains. This is the complete domain (e.g., dev1.tealium.com,qa-serv3.tealium.com). External Script URL: Only used by the External Tag Version. Data Mappings Mapping is the process of sending data from a data layer variable to the corresponding destination variable of the vendor tag. For instructions on how to map a variable to a tag destination, see Data Mappings. The available categories are: Page View Variable Description Page ID (pi) Page Category (cg) Search String (se) Search Results (sr) ---------------   Attribute 1 (pv_a1) Attribute 2 (pv_a2) Attribute 3 (pv_a3) Attribute 4 (pv_a4) Attribute 5 (pv_a5) Attribute 6 (pv_a6) Attribute 7 (pv_a7) Attribute 8 (pv_a8) Attribute 9 (pv_a9) Attribute 10 (pv_a10) ---------------   Extra Field 1 (pv1) Extra Field 2 (pv2) Extra Field 3 (pv3) Extra Field 4 (pv4) Extra Field 5 (pv5) Extra Field 6 (pv6) Extra Field 7 (pv7) Extra Field 8 (pv8) Extra Field 9 (pv9) Extra Field 10 (pv10) Product View Variable Description Product ID (pr) Product Name (pm) Product Category (cg) Product Virtual Category (cm_vc) ---------------   Attribute 1 (pr_a1) Attribute 2 (pr_a2) Attribute 3 (pr_a3) Attribute 4 (pr_a4) Attribute 5 (pr_a5) Attribute 6 (pr_a6) Attribute 7 (pr_a7) Attribute 8 (pr_a8) Attribute 9 (pr_a9) Attribute 10 (pr_a10) Cart View (ShopAction5) Variable Description Product ID (pr) Product Name (pm) Product Quantity (qt) Product Price (bp) Product Category (cg) ---------------   ShopAction5 Attribute 1 (s_a1) ShopAction5 Attribute 2 (s_a2) ShopAction5 Attribute 3 (s_a3) ShopAction5 Attribute 4 (s_a4) ShopAction5 Attribute 5 (s_a5) ShopAction5 Attribute 6 (s_a6) ShopAction5 Attribute 7 (s_a7) ShopAction5 Attribute 8 (s_a8) ShopAction5 Attribute 9 (s_a9) ShopAction5 Attribute 10 (s_a10) ---------------   ShopAction5 Extra Field 1 (sx1) ShopAction5 Extra Field 2 (sx2) ShopAction5 Extra Field 3 (sx3) ShopAction5 Extra Field 4 (sx4) ShopAction5 Extra Field 5 (sx5) ShopAction5 Extra Field 6 (sx6) ShopAction5 Extra Field 7 (sx7) ShopAction5 Extra Field 8 (sx8) ShopAction5 Extra Field 9 (sx9) ShopAction5 Extra Field 10 (sx10) Order (ShopAction9) Variable Description ShopAction9 Registration Id (cd) ShopAction9 Order Number (on) ShopAction9 Order Subtotal (tr) ShopAction9 Product ID (pr) [Array] ShopAction9 Product Name (pm) [Array] ShopAction9 Product Quantity (qt) [Array] ShopAction9 Product Price (bp) [Array] ShopAction9 Product Category (cg) [Array] ---------------   ShopAction9 Attribute 1 (s_a1) ShopAction9 Attribute 2 (s_a2) ShopAction9 Attribute 3 (s_a3) ShopAction9 Attribute 4 (s_a4) ShopAction9 Attribute 5 (s_a5) ShopAction9 Attribute 6 (s_a6) ShopAction9 Attribute 7 (s_a7) ShopAction9 Attribute 8 (s_a8) ShopAction9 Attribute 9 (s_a9) ShopAction9 Attribute 10 (s_a10) ---------------   ShopAction9 Extra Field 1 (sx1) ShopAction9 Extra Field 2 (sx2) ShopAction9 Extra Field 3 (sx3) ShopAction9 Extra Field 4 (sx4) ShopAction9 Extra Field 5 (sx5) ShopAction9 Extra Field 6 (sx6) ShopAction9 Extra Field 7 (sx7) ShopAction9 Extra Field 8 (sx8) ShopAction9 Extra Field 9 (sx9) ShopAction9 Extra Field 10 (sx10) ---------------   Order Number (on) Order Subtotal (tr) Order Shipping Amount (sg) Order Registration Id (cd) Order City (ct) Order State (sa) Order Zip/Postcode (zp) ---------------   Order Attribute 1 (o_a1) Order Attribute 2 (o_a2) Order Attribute 3 (o_a3) Order Attribute 4 (o_a4) Order Attribute 5 (o_a5) Order Attribute 6 (o_a6) Order Attribute 7 (o_a7) Order Attribute 8 (o_a8) Order Attribute 9 (o_a9) Order Attribute 10 (o_a10) ---------------   Order Extra Field 1 (or1) Order Extra Field 2 (or2) Order Extra Field 3 (or3) Order Extra Field 4 (or4) Order Extra Field 5 (or5) Order Extra Field 6 (or6) Order Extra Field 7 (or7) Order Extra Field 8 (or8) Order Extra Field 9 (or9) Order Extra Field 10 (or10) Registration Variable Description Registration Id (cd) Registration Email (em) Registration City (ct) Registration State (sa) Registration Zip/Postcode (zp) Registration Country (cy) ---------------   Registration Attribute 1 (rg1) Registration Attribute 2 (rg2) Registration Attribute 3 (rg3) Registration Attribute 4 (rg4) Registration Attribute 5 (rg5) Registration Attribute 6 (rg6) Registration Attribute 7 (rg7) Registration Attribute 8 (rg8) Registration Attribute 9 (rg9) Registration Attribute 10 (rg10) Conversion Event Variable Description Conversion Event Id (cid) Conversion Event Action Type (cat) Conversion Event Category Id (ccid) Conversion Event Points (cpt) ---------------   Conversion Event Attribute 1 (c_a1) Conversion Event Attribute 2 (c_a2) Conversion Event Attribute 3 (c_a3) Conversion Event Attribute 4 (c_a4) Conversion Event Attribute 5 (c_a5) Conversion Event Attribute 6 (c_a6) Conversion Event Attribute 7 (c_a7) Conversion Event Attribute 8 (c_a8) Conversion Event Attribute 9 (c_a9) Conversion Event Attribute 10 (c_a10) ---------------   Conversion Event Extra Field 1 (cx1) Conversion Event Extra Field 2 (cx2) Conversion Event Extra Field 3 (cx3) Conversion Event Extra Field 4 (cx4) Conversion Event Extra Field 5 (cx5) Element Variable Description Element Id (eid) Element Category (ecat) ---------------   Element Attribute 1 (e_a1) Element Attribute 2 (e_a2) Element Attribute 3 (e_a3) Element Attribute 4 (e_a4) Element Attribute 5 (e_a5) Element Attribute 6 (e_a6) Element Attribute 7 (e_a7) Element Attribute 8 (e_a8) Element Attribute 9 (e_a9) Element Attribute 10 (e_a10) Manual Variable Description Manual Link HREF (hr) Manual Link Name (nm) Manual Link Page Id (pi) Manual Page View Destination URL (ul) Manual Page View Referring URL (rf) Manual Impresssion Page Id (pi) Manual Impression Track Real Estate (cm_re) Manual Impression Track Site Promotion (cm_sp) Error Variable Description Page ID (pi) Error Category (cg) Events Variable Description Registration Registration Order Order Cart/ShopAction5 ShopAction5 Product View Productview Conversion Event Conversion Element Element Error Error Config Variable Description Client ID (ClientID) Test Client ID (TestClientID) Test Data Collection Method (TestDataCollectionMethod) Test Data Collection Domain (TestDataCollectionDomain) Advanced Setup Object (cmSetupOther) [Object] ... View more

This article describe a solution for combining the following SiteCatalyst visit details plugins into a single JavaScript Code extension: s.getVisitNum (https://marketing.adobe.com/resources/help/en_US/sc/implement/getVisitNum.html) s.getNewRepeat (https://marketing.adobe.com/resources/help/en_US/sc/implement/getNewRepeat.html) s.getVisitStart (https://marketing.adobe.com/resources/help/en_US/sc/implement/getVisitStart.html) s.getDaysSinceLastVisit (https://marketing.adobe.com/resources/help/en_US/sc/implement/getDaysSinceLastVisit.html) This article covers the following topics: Table of Contents Placeholder How it Works The cpde sample in this article and the attached sitecatalyst-visit-details-code.txt file contains the JavaScript required to create a custom plugin. The plugin creates five (5) variables in the Tealium Data Layer that can then be mapped to a SiteCatalyst tag. Creating and Deploying the Extension Use the following steps to create and deploy the custom SiteCatalyst Visit Details extension: Add a JavaScript code extension. In the Title field, enter SiteCatalyst Visit Details Extension. In the Scope field, keep the default setting, All Tags to ensure that new variables are available to all of your tags. You can optionally set scope to the SiteCatalyst tag to reserve the functionality for SiteCatalyst. In the Execution field, keep the After Load Rules (default) setting. In the Configuration field, paste the code from your clipboard into the form box. Click the Data Layer tab. Define the following variables: _visit_page_num _visit_return _visit_start _visit_number _visit_type Map the new variables to the corresponding Adobe variables. Click Save/Publish. Sample SiteCatalyst Visit Details JavaScript The following sample and attached sitecatalyst-visit-details-code.txt  text file contains the JavaScript required to create this custom plugin.   // change the following as appropriate var visit_timer = 30; //days since last visit // end changes (function (a, c, d, e, f, g, h, i, k, l, m, n, o, p, q, r, s, t,v) { a = a ? parseInt(a) : 30; n = v = 1; r = function (w, x, y, z) { // read cookie x = w + "="; y = document.cookie.split(';'); for (var i = 0; i < y.length; i++) { z = y[i]; while (z.charAt(0) == ' ') z = z.substring(1, z.length); if (z.indexOf(x) == 0) return z.substring(x.length, z.length); } return ""; }; q = function (x, y, z) { // set cookie if (typeof z == "number") z = new Date(z); document.cookie = x + "=" + y + ";path=/;domain=" + utag.cfg.domain + ";expires=" + (z?z.toGMTString():""); //b["cp."+x] = y; // add cookie to udo }; d = new Date(); e = d.getTime(); f = 'utag_vnum'; g = 'utag_invisit'; o = 'utag_vs'; p = 'utag_dslv'; // get visit num and new/repeat d.setTime(e + a*24*60*60*1000); h = r(f); if (h) { i = h.substring(h.indexOf('&vn=') + 4, h.length); k = h.substring(0, h.indexOf('&vn=')); } if (r(g)) { if (i) { // return same visit num if already in visit q(g, 'true', d.setTime(e + 30*60*1000)); m = i; l = (e-(parseInt(k)-(a*24*60*60*1000)) < 30*60*1000) ? "New" : "Repeat"; } else { // in case the cookie has been altered m = l = "unknown"; } } else { if (i) { // increment visit num i++; q(f, k+'&vn='+i, d.setTime(k)); q(g, 'true', d.setTime(e + 30*60*1000)); m = i; l = "Repeat"; } else { // set initial visit q(f, e + a*24*60*60*1000 +'&vn=1', d); q(g, 'true', d.setTime(e + 30*60*1000)); m = 1; l = "New"; } } // visit start and page number if (!(r(o))) { v = 1; } if (r(o)) { n = 0; v=r(o); v++; } if (!q(o, v, new Date().setTime(new Date().getTime() + 1800000))) q(o, v, 0); if (!r(o)) n = v = 0; // days since last visit code s = new Date(); t = new Date(); c = s.getTime(); d = 24 * 60 * 60 * 1000; s.setTime(c + 3 * 365 * d); t.setTime(c + 30 * 60 * 1000); f = c - r(p); if (r(p).length == 0) { q(p, c, s); q(p + '_s', 'First Visit', t); } else { q(p, c, s); if (d > 30 * 60 * 1000) { if (f > 30 * d) { q(p + '_s', 'More than 30 days', t); } else if (f < 30 * d + 1 && f > 7 * d) { q(p + '_s', 'More than 7 days', t); } else if (f < 7 * d + 1 && f > d) { q(p + '_s', 'Less than 7 days', t); } else if (f < d + 1) { q(p + '_s', 'Less than 1 day', t); } else { q(p, c, -1); h = ''; } } else { q(p + '_s', r(p + '_s'), t); } } e = r(p + '_s'); if (e.length == 0) h = 'Cookies Not Supported'; else if ( e != 'First Visit' && e != 'More than 30 days' && e != 'More than 7 days' && e != 'Less than 7 days' && e != 'Less than 1 day' ) h = ''; else h = e; b['_visit_page_num'] = v; b['_visit_return'] = h; b['_visit_start'] = n; b['_visit_number'] = m; b['_visit_type'] = l; })(visit_timer);   ... View more