Tagging Guide: Website and Implementation. Contents

Size: px

Start display at page:

Download "Tagging Guide: Website and Email Implementation. Contents"

Gordon Perry
10 years ago
Views:

Tagging Guide: Website and Email Implementation Contents About This Guide... 2 Your CiteID... 2 Website Implementation.

1 Tagging Guide: Website and Implementation Contents About This Guide... 2 Your CiteID... 2 Website Implementation... 2 Tag Placement... 2 Example Implementation... 5 DNS Setup... 5 Tag Placement... 5 Example... 5 Version 2-1

.. 2 Tag Placement... 2 Example... 3 Email Implementation.

2 About This Guide The following is confidential and proprietary information and is intended only for 4Cite, LLC internal, customer and partner usage. This document demonstrates how to implement the 4Cite tracking technology on a website and in outbound s. It is assumed the implementing party has an understanding of JavaScript and html methodologies. For implementation support, please contact [email protected] or contact your 4Cite representative at (518) Your CiteID When setting up the tracking code, you will need to specify a CiteID for each web entity/property you are tracking. The CiteID will be the identifier that links the activity from your properties in order to provide various 4Cite services. If you manage a single web property that may or may not span multiple domains, a single CiteID is required. Alternately, if you manage multiple brands/properties you will need a CiteID for each. In cases with multiple brands the leading component of the ID represents the global entity with a suffix representing the specific property or brand. Your CiteID is:0123_45678 Website Implementation A key component of all 4Cite digital marketing services is the tracking system utilized to capture web and activity. It is this system that allows us to identify visitors and collect behavior information that can be leveraged to drive your marketing campaigns. On your website, tracking is carried out through the execution of the JavaScript described below. The domain securedvisit.com serves the tracking functionality. Tag Placement The JavaScript will need to be placed on all participant web pages. Any page that acts as potential visitor entry points, or represents a relevant tracking event (Cart Creation, Order Confirmation) as well as any page which can be utilized to collect address must include the tracking code. It is required that the sv.js JavaScript be the first script tag placed between the <head> and </head> tags in your website code. Please realize, before any tracking events can be fired, the sv.js JavaScript file must be loaded. Page 2

It is assumed the implementing party has an understanding of JavaScript and html methodologies. For implementation support, please contact support@4cite.

3 Example Before you can make tracking calls, the sv.js file must be must be placed at the start of the document head in your website code.  <script type="text/javascript"> window._svq = window._svq []; window._svq.push(['_setaccount', 'YOUR_CITEID']); window._svq.push(['_trackpageview']); (function (d, c) { var sv = d.createelement(c); sv.type = 'text/javascript'; sv.src = '//track.securedvisit.com/js/sv.js'; var s = d.getelementsbytagname(c)[0]; s.parentnode.insertbefore(sv, s); })(document, 'script'); </script>  All variables in YELLOW should be replaced with its appropriate value. Server Side Actions The SecuredVisit servers carry out the following functions: Session/Visitor Management The JavaScript will utilize several mechanisms to identify both a visitor and a session. A firstparty cookie may be created with a visitor/session identifier. Additional DOM methods may also be deployed to identify sessions/visitors. Cookie Management Two third-party cookies set from the securedvisit.com domain (named sv_sid & sv_onid created in / path with expiration date set to 1 year from creation date) are created on first visit, or referenced for return visits. These cookies includes a unique visitor ID. On calling the tracking system, we will create a 1st party cookie which contains a unique user ID for the visitor. This is included to improve collection rates in instances which users do not accept 3rd party cookies. This is particularly important for re-targeting efforts. Visit Collection Several data elements are captured and stored including: Date-Time of the visit URL (and query string) from the page calling the pixel Tracking query string (key value pairs) address First Party Cookie Page 3

createelement(c); sv.type = 'text/javascript'; sv.src = '//track.securedvisit.com/js/sv.js'; var s = d.getelementsbytagname(c)[0]; s.parentnode.

4 Cross Domain Session Sharing (if applicable) Cross domain session sharing occurs when you want to share a visitor s session on your website with another website. This is useful when a website handles order fulfillment on a third party website. When redirecting a visitor to a third party page to complete an action, the visitor s SecuredVisit cookie on the referring site must be passed to the third party so the visitor s session remains synchronized. An example would be YourSite.com using a third party website, Orders.com, to place an order. 4Cite JavaScript is required on the third party website to capture any cart and order tracking. See below for code to modify an existing link on your web page: Modifying a link on YourSite.com to place an order via a button or event. <a href=" onclick="_svt.push(['_link', this.href]); return false;">click me</a> Orders.com needs to have 4Cite tracking code on the landing page. In doing so, the 4Cite tracking code can now identify the order being placed on the website with the SecuredVisit cookie that was provided. 4Cite tracking code will automatically use the cookie passed in, and the third party website, Orders.com, will be responsible for implementing Cart Tracking and Order Tracking code on its website. Use _link() to get the SecuredVisit cookie. Example: window._svt.gettracker()._link() If using a form: _linkbypost() This method passes the SecuredVisit cookies from the referring form to another site in a string appended to the action value of the form (HTTP POST). This method is typically used when tracking user behavior from one site to a 3rd-party shopping cart site, but can also be used to send cookie data to other domains in pop-ups or in iframes. Example: <form action=" name="f" method="post" onsubmit="_svt.push(['_linkbypost', this]);">... </form> To modify the URL to add 4Cite cookie data: _getlinkerurl() Enables cross-domain user tracking specifically for iframes and links that open in a new window. Returns a string of all the SecuredVisit cookie data from the initiating link by appending it to the URL parameter. This can then be passed on to another site or iframe. Example: var pagetracker = _svt._gettrackerbyname(); // Gets the default tracker var linkerurl = pagetracker._getlinkerurl(' Page 4

When redirecting a visitor to a third party page to complete an action, the visitor s SecuredVisit cookie on the referring site must be passed to the third party so the visitor s session remains

Email Implementation A key component in 4Cite s identification and tracking capabilities is driven by capturing email opens each time a recipient opens an email you have sent to them.

5 Implementation A key component in 4Cite s identification and tracking capabilities is driven by capturing opens each time a recipient opens an you have sent to them. The pixel call is an invisible image embedded in the body of your sends. When a user opens their , this invisible image is opened, 4Cite s servers receive that information, and 4Cite now knows the user has opened an from you. To enable this functionality there are 2 steps you need to complete as follows: DNS Setup A new DNS CNAME (Canonical Name) entry needs to be added to the same domain that is represented in your From address. This entry will be a for a new child zone below your existing sending domain entry. Zone is often times also referred to as node, alias or sub-domain. Once created, this entry will link this new zone to our back-end servers that facilitate the pixel receipt operations. CNAME creation is one of the most common DNS configuration carried out. Systems/network administrators are very familiar with this process and it is a simple single step to complete. Specific details are as follows: New Entry: Domain: MYFROMDOMAIN.COM Alias/Zone/Node: svopn Type: CNAME Points To: MYCOMPANY.open.securedvisit.com TTL: Default Results in: svopn.myfromdomain.com -> MYCOMPANY.open.securedvisit.com Note: The propagation of this change across the global DNS system is typically same day, but it may take up to 72 hours. This step must be completed before moving on to Template Setup. Tag Placement To be placed between the <body> and </body> in the HTML versions of outbound s. Example <img src=" height="1" width="1" /> Note: https is not supported with basic setup but can be supported with client supplied certificate. All variables in YELLOW should be replaced with its appropriate value. Replace MYFROMDOMAIN with the domain represented in your From Address. Replace YOUR_CITEID with the CiteID provided on page 3 of this document. Replace RAW with the syntax of your ESP for actual address. Replace SOURCE with a source code for reporting purposes. This is optional. Page 5

When a user opens their email, this invisible image is opened, 4Cite s servers receive that information, and 4Cite now knows the user has opened an email from you.

Implementing Sub-domain & Cross-domain Tracking A Complete Guide

Implementing Sub-domain & Cross-domain Tracking A Complete Guide Prepared By techbythebay.com 1 Contents 1. Sub Domain & Cross Domain Tracking for GA (asynchronous) I. Standard HTML/JavaScript Implementation