Thread: Google Analytics (URCHIN) & E-Commerce Tracking Integration

Part 1: URCHIN

Use the following Analytics tracking code in your skin template.ascx file(s):

Code:

<script src="https://ssl.google-analytics.com/urchin.js"
type="text/javascript">
</script>
<script type="text/javascript">
_uacct = "UA-XXXXX-X";            
urchinTracker();
</script>

Please note also that the "UA-XXXXX-X" value should be replaced with your account number.

Note the use of HTTPS and different url. This avoids the browser security warning pop-up message on every secure page. This HTTPS link can also be invoked on non-secure pages also, so embedding in the skin is fine. We place this in template.ascx just before the closing body tag.

You must sign up for a Google Urchin account first of course. Note that stats reporting into google can often be delayed a bit (up to 1 DAY), so once you first add this to your skin template, it will NOT show up that very second...give it a day to ensure it's working.

PART 2 (optional)

To Track "e-commerce transactions", see:

http://adwords.google.com/support/bi...y?answer=55528

For assistance, please see Google. Some notes are below:

a) make sure you setup your site as e-commerce site as "yes"

b) use https://www.yourdomain.com/orderconfirmation.aspx as the sales goal page

c) (optional) use your own checkout page sequence as your goal funnel. All sites are different. Examples are shoppingcart.aspx -> createaccount.aspx -> checkoutshipping.aspx -> checkoutpayment.aspx -> checkoutreview.aspx -> orderconfirmation.aspx, or shoppingcart.aspx -> checkout1.aspx -> orderconfirmation.aspx. If you are skipping shipping it's different, etc.

d) (note) the urchin tracker code will ALREADY be in your orderconfirmation pages and checkout pages if you did the PART 1 steps above! do not repeat this on the orderconfirmation page.

e) add this new parser tag just below the urchin javascript block in your template.ascx file:

(!GOOGLE_ECOM_TRACKING!)

That's it. This will be in fully supported (included in the core dll's) in builds 7.0.1.0+.

PRIOR VERSION USERS

For prior version users, you have to also make some code mods to add this:

1. change the order.cs object to have the m_AffiliateID to be of type int (not string).

2. add these new changes to order.cs:

Code:

        public int AffiliateID
        {
            get
            {
                return m_AffiliateID;
            }
        }

        public String AffiliateName
        {
            get
            {
                String tmpS = String.Empty;
                if (AffiliateID > 0)
                {
                    EntityHelper AffiliateHelper = AppLogic.LookupHelper(EntityDefinitions.readonly_AffiliateEntitySpecs.m_EntityName);
                    tmpS = AffiliateHelper.GetEntityName(AffiliateID, Localization.GetWebConfigLocale());
                }
                return tmpS;
            }
        }

3. Add this new Parser Token in Parser.cs:ReplacePageDynamicTokens:

Code:

                if (s.IndexOf("(!GOOGLE_ECOM_TRACKING!)") != -1)
                {
                    if (CommonLogic.GetThisPageName(false).ToLowerInvariant().StartsWith("orderconfirmation.aspx"))
                    {
                        ht.Add("GOOGLE_ECOM_TRACKING", AppLogic.GetGoogleEComTracking(ThisCustomer));
                    }
                    else
                    {
                        ht.Add("GOOGLE_ECOM_TRACKING", String.Empty);
                    }
                }

4. Add this new routine in AppLogic.cs:

Code:

        public static String GetGoogleEComTracking(Customer ThisCustomer)
        {
            if (!AppLogic.AppConfigBool("UseLiveTransactions") || ThisCustomer == null || !CommonLogic.GetThisPageName(false).ToLowerInvariant().StartsWith("orderconfirmation.aspx") || CommonLogic.QueryStringUSInt("OrderNumber") == 0)
            {
                return String.Empty;
            }

            try
            {
                int OrderNumber = CommonLogic.QueryStringUSInt("OrderNumber");
                Order ord = new Order(OrderNumber, Localization.GetWebConfigLocale());

                if (ThisCustomer.CustomerID != ord.CustomerID)
                {
                    return String.Empty;
                }

                StringBuilder tmpS = new StringBuilder(1024);
                tmpS.Append("<form style=\"display:none;\" name=\"utmform\">\n");
                tmpS.Append("<textarea id=\"utmtrans\">\n");
                tmpS.Append(String.Format(" UTM:T|{0}|{1}|{2}|{3}|{4}|{5}|{6}|{7} \n", 
                    ord.OrderNumber.ToString(), 
                    ord.AffiliateName, 
                    Localization.CurrencyStringForGatewayWithoutExchangeRate(ord.Total(true)),
                    Localization.CurrencyStringForGatewayWithoutExchangeRate(ord.TaxTotal(true)),
                    Localization.CurrencyStringForGatewayWithoutExchangeRate(ord.ShippingTotal(true)),
                    ord.BillingAddress.m_City, 
                    ord.BillingAddress.m_State, 
                    ord.BillingAddress.m_Country
                    ));

                foreach(CartItem c in ord.CartItems)
                {
                    tmpS.Append(String.Format(" UTM:I|{0}|{1}|{2}|{3}|{4}|{5} \n", 
                        ord.OrderNumber.ToString(), 
                        c.m_SKU, 
                        c.m_ProductName,
                        AppLogic.GetFirstProductEntity(AppLogic.LookupHelper(EntityDefinitions.readonly_CategoryEntitySpecs.m_EntityName),c.m_ProductID,false,Localization.GetWebConfigLocale()), 
                        Localization.CurrencyStringForGatewayWithoutExchangeRate(c.m_Price), 
                        c.m_Quantity.ToString()
                        ));
                }

                tmpS.Append("</textarea>");
                tmpS.Append("</form>\n");
                tmpS.Append("<script type=\"text/javascript\">__utmSetTrans();</script>");
                return tmpS.ToString();
            }
            catch
            {
                return String.Empty;
            }
        }

5. Recompile and test/deploy.

Again, these code mods will be in build 7.0.1.0+ automatically. You just have to add the (!GOOGLE_ECOM_TRACKING!) token to your skin file.

Just when you thought it was safe to incorperate the latest google analytic code, good old google have added a new method of reporting performance of landing pages from adwords, which looks quite interesting.

https://www.google.com/analytics/sit...ary.html#test1

The basic idea is to tag a landing page and create several versions of the page with slightly different layouts to identify what combination that performs best.

It would be useful to have this incorperated or added to the wish list for the future, at the moment I was going to use a locale varient to give a different landing page, to test the logic.

What exactly is the output of the (!GOOGLE_ECOM_TRACKING!) macro?

In other words, do I have to modify the body tag and include the __utmSetTrans call in the page as well?



From Google's documentation:

Next, somewhere in the receipt below the tracking code, the following lines need to be written by your engine. Everything in brackets should be replaced by actual values, as described in the Parameter Reference, below.

<form style="display:none;" name="utmform">
<textarea id="utmtrans">UTM:T|[order-id]|[affiliation]|
[total]|[tax]| [shipping]|[city]|[state]|[country] UTM:I|[order-id]|[sku/code]|[productname]|[category]|[price]|
[quantity] </textarea>
</form>

Finally, the utmSetTrans function must be called after the form is submitted in order to record the transaction. This can be most easily accomplished through a body onLoad event within the opening <body> tag:

<body onLoad="javascript:__utmSetTrans()">

If you don't have the ability to edit the body tag, you can call the utmSetTrans function within a separate script tag as long as you ensure that the function is called after the form:

<script type="text/javascript">
__utmSetTrans();
</script>

It outputs exactly what the documentation says. If you look at step 4 at the code that goes into AppLogic.cs, you'll see that it ouputs 'M:T|[order-id]|[affiliation]|[total]|[tax]| [shipping]|[city]|[state]|[country]' and then for each item in the cart proceeds to output 'UTM:I|[order-id]|[sku/code]|[productname]|[category]|[price]|
[quantity]' after this, the call to __utmSetTrans is already made for you. As long as you have all of the code from the first page of this thread compiled into your store then all you have to do is put the GOOGLE_ECOM_TRACKING token in your template file after the urchin tracking number portion and before the end </body> tag. If you have 7.0.1.1 then you don't even have to compile this code in...it's already there for you

I was trying to get this GOOGLE_ECOM_TRACKING to work and was doing everything by the book but somehow is was not showing on the page html code...

"Maybe it is not yet in 7.0.1.1" - I though...

After grabbing VStudio, I opened the project, searched for GOOGLE_ECOM_TRACKING and there is was in parser.cs.

"So it is in 7.0.1.1! Good! Now why is it failing?"

The answer to my question came from the GetGoogleEComTracking function (at AppLogic.cs):

Code:

if (!AppLogic.AppConfigBool("UseLiveTransactions") || This....

So, if we are NOT with Live Transactions, DO NOT expect to see the Google Ecommerce tracking code.

I just thought you would be happy to know because I was looking for this on my testing site and it would never work unless I was live.

fsantos

Yup...test orders doesn't make sense to "analyze".

Proper google ecom tracking for returns/voides/cancelled orders?

Hi,

Anyone implemented this for voids, cancellations? Perhaps it's already
taken care of in the admin? :-D

It is sometimes necessary to back-out or cancel an e-commerce transaction. Cancelling orders which did not go through or which were disallowed ensures that your Google Analytics reports, including Campaign Tracking reports, provide accurate information.

To cancel an order or transaction, create and load a duplicate receipt (__utmSetTrans) page containing a negative transaction total. For example, if the the original transaction total is $699, the duplicate entry should have -$699 as the transaction total. Google Analytics will record this negative value and apply it against your totals, effectively erasing the transaction.

Regards
AndreasW

RE: "Perhaps it's already taken care of in the admin? :-D"

we don't have that in the admin, but not a bad idea...i'll put it on the to-do list so it doesn't get lost at least

Has anyone got this working to track orders when they go thru Google Checkout instead of the storefront checkout?

http://code.google.com/apis/checkout...tegration.html

Third-party tracking of Google Checkout orders via Analytics is scheduled to be released in the next update. ADNSF updates are typically spaced 1-2 months apart.

Google Analytics is now offering/suggesting ga.js in place of urchin.js , and even though urchin.js will continue to work the next year, the GA Blog Entry says:

"An immediate benefit you'll notice is that the ga.js tags allow you to track ecommerce transactions in a more readable way."

Since this JUST happend, I know I can't say how true that is, but GA has already updated the Help Ctr. article on adding the new code to your RECEIPT page: http://www.google.com/support/google...n&answer=55528

Hope this is found helpful,
Raph

I found the code we are supposed to use for the new ecommerce tracking, but I'm not smart enough to figure out what I'm supposed to change to make it work with the store

Hopefully one of you more tech savy people can light the way for the rest of us

Here's the code Google says for us to use:

HTML Code:

<script type="text/javascript">
var gaJsHost = (("https:" == document.location.protocol) ? "https://ssl." : "http://www.");
document.write(unescape("%3Cscript src='" + gaJsHost + "google-analytics.com/ga.js' type='text/javascript'%3E%3C/script%3E"));
</script>

<script type="text/javascript">
  var pageTracker = _gat._getTracker("UA-XXXXX-1");
  pageTracker._initData();
  pageTracker._trackPageview();

  pageTracker._addTrans(
    "1234",                                     // Order ID
    "Mountain View",                            // Affiliation
    "11.99",                                    // Total
    "1.29",                                     // Tax
    "5",                                        // Shipping
    "San Jose",                                 // City
    "California",                               // State
    "USA"                                       // Country
  );

  pageTracker._addItem(
    "1234",                                     // Order ID
    "DD44",                                     // SKU
    "T-Shirt",                                  // Product Name 
    "Green Medium",                             // Category
    "11.99",                                    // Price
    "1"                                         // Quantity
  );

  pageTracker._trackTrans();
</script>

Now I know we replace the UA-XXXXX-1 with our analytics number, and I'm assuming we have to replace the lower stuff in quotes with something that matches what our cart provides. Can anyone here please shed some light?

Thanks!

So to my previous post... the ONLY thing I have to do in ASPDotNetStorefront to track E-commerce transactions in Google Analytics is to put

(!GOOGLE_ECOM_TRACKING!)

right below the javascript snippet that Google provides?

And everything should be golden? And if it's NOT golden then I need to contact support...?

No changes to the order confirmation page... nothing else?

Just trying to clarify that there wasn't anything else we were missing... cause it's not working. Thanks.

The new google analytics (ga.js) javascript will not work with the storefront until version 7.0.2.5. You must be using the urchin (urchin.js) javascript to use the (!GOOGLE_ECOM_TRACKING!) token. This must be in your template.ascx file:

Code:

<script src="https://ssl.google-analytics.com/urchin.js"
type="text/javascript">
</script>
<script type="text/javascript">
_uacct = "UA-XXXXX-X";            
urchinTracker();
</script>

(!GOOGLE_ECOM_TRACKING!)

If you are using the urchin.js javascript and have it pasted into your template and it's still not working...send to support. If you are using the new ga.js javascript, you will need to remove it and use the urchin.js javascript.

When 7.0.2.5 is released we will post instructions for using the ga.js javascript. It will be almost the same...but it will be a new token (we will still keep support for urchin.js as long as google still accepts it) and there will be an appconfig parameter for the analytics account rather then pasting it into the template.ascx file.

All of this stuff

Code:

<script type="text/javascript">
  var pageTracker = _gat._getTracker("UA-XXXXX-1");
  pageTracker._initData();
  pageTracker._trackPageview();

  pageTracker._addTrans(
    "1234",                                     // Order ID
    "Mountain View",                            // Affiliation
    "11.99",                                    // Total
    "1.29",                                     // Tax
    "5",                                        // Shipping
    "San Jose",                                 // City
    "California",                               // State
    "USA"                                       // Country
  );

  pageTracker._addItem(
    "1234",                                     // Order ID
    "DD44",                                     // SKU
    "T-Shirt",                                  // Product Name 
    "Green Medium",                             // Category
    "11.99",                                    // Price
    "1"                                         // Quantity
  );

  pageTracker._trackTrans();
</script>

is done behing the scenes; order information (line items and subtotals and addresses) has to be done in the code files and cannot be done in the template.ascx file. That code will not be pasted into the template.ascx page when support for ga.js is released.

there will be an appconfig parameter for the analytics account

Can you paste parameter name here plz, so we can create our own that is identical?

Google.AnalyticsAccount

and it's value will be what you used to enter for UA-XXXXX-X in the urchin code:

<script src="https://ssl.google-analytics.com/urchin.js"
type="text/javascript">
</script>
<script type="text/javascript">
_uacct = "UA-XXXXX-X";
urchinTracker();
</script>

So I added this to my template.aspx:

<script src="https://ssl.google-analytics.com/urchin.js"
type="text/javascript">
</script>
<script type="text/javascript">
_uacct = "UA-XXXXX-X";
urchinTracker();
</script>

(!GOOGLE_ECOM_TRACKING!)

Google says I'm good to go but when I look at my pages on the site I see (!GOOGLE_ECOM_TRACKING!) at the bottom. I don't think that's correct, right? I have this right before the </Body> tag.

What does (!GOOGLE_ECOM_TRACKING!) do for me that the GA script doesn't?

Thanks,
Erik

Okay, so now I'm more confused....

At the beginning of this thread you say to use the GA secure script with the https:. However, when I do that it GA doesn't like it and says the tracking code is not installed.

So, I thought all I had to do was change the GA URL to https://store.nlpco.com but then GA says the status is "Unknown" and no analytics.

I'm left with going back to the http: code and telling GA to track http://store.nlpco.com until perhaps someone can shed some light on where I messed up.

Thanks,
Erik

In the first part of the thread we say to use https:// for the urchin tracking code, which is the only google analytics tracking code supported in versions of the storefront prior to 7.0.2.5. According to Google you do not need to use separate sections of javascript when using secure or non-secure sites.

Versions prior to 7.0.2.5 must use the urchin.js javascript and must specify https:// or http:// in the reference to the urchin.js file.

Additional information on using the new ga.js tracking code in versions 7.0.2.5+ can be found in our knowledgebase

Sorry George for my confusion in my posts...I am NOT using the ga.js script but the urchin.

However, what seems to be the problem is that when I put in the secure urchin code for https://store.nlpco.com Google says it's not there.

The only urchin code I can get to work is the non-secure urchin code with the non-secure url...which of course causes our shoppers problems when then try to check out.

Any ideas?

Thanks,
Erik

This is a very well written script, but the thing is, after an hour of looking at whats wrong on my end, I found that the string that's sent to the user on the checkout pages doesn't have any quotations in the correct area. I hope this is a shortcoming on my part, I wouldn't think that ADNSF would forget such an important part of the javascript.

Do you guys find similar results? I'm running ML 7.0.2.5


Robert

Is the Google Analytics (URCHIN) & E-Commerce Tracking Integration built in the Phone order system? Can this track sales coming in from here?

Im using the urchin and Im getting the display non-secure item error

Does this actually work with a SSL without errors?? I need a page counter and used Site Meter for the past 12 years but it gives me the same error.

Help please

I am in a older version of the storefront package ( AspDotNetStorefront 6.2.1.7/6.2.1, DB Version: 6.2.1 ) and implemented the changes that were described in the first post of this thread. I am getting an error in the Parser.cs file on these lines :

if (CommonLogic.GetThisPageName(false).ToLowerInvaria nt().StartsWith("orderconfirmation.aspx"))
{
ht.Add("GOOGLE_ECOM_TRACKING", AppLogic.GetGoogleEComTracking(ThisCustomer));
}
else
{
ht.Add("GOOGLE_ECOM_TRACKING", String.Empty);
}

The bold line is where I get this error message :

Item has already been added. Key in dictionary: 'GOOGLE_ECOM_TRACKING' Key being added: 'GOOGLE_ECOM_TRACKING'

Has anyone else gotten this problem ?

How many times does the term "'GOOGLE_ECOM_TRACKING" appear in parser.cs? Looks like you have something in there twice.

RE: "I am in a older version of the storefront package..."

guys/gals. pay attention now.

Please upgrade to our current releases...We've said, emailed, and recommended this 10 times....to every customer that allows us to email them.

http://www.aspdotnetstorefront.com/t-ml711.aspx

if users are running 2 year old software now, YOU have a responsibilty to your business, and your clients, to maintain them current. Please pay attention. I'm sorry for being rude, but we send THOUSANDS of "make sure your site is current" emails, and they are usually ignored.

E-Commerce is not a free business, you don't put up a site and leave it alone for years...update to current Visa Certified PABP and maintain the best posture for your site and your business. It's time for users to pay attention to what we recommend, yes it costs money, but yes, running a business costs money...

Any questions contact our sales dept. We'll be glad to discuss this with you.

If you need, contact me personally...all 10000 customers...i'll talk to every one. This "I'm running 2-3-4 year old software" crap ends right here, and right now. You are doing an incompetent and negligent job to your business and your customers, if you are not keeping them current.

I have placed the ga.js script in the template.ascx before the </body> as google suggests. However, I have also placed this in the TOPICS "GoogleTrackingCode", recently I entered an order for a customer and noticed on the orderconfirmation.aspx page that the google ga.js script is displayed on the page just below the: "For a printable receipt, click here".

Where should the ga.js code go? Topics and Template or just Topics?

Thanks

You do not need it in the Topic. That would be redundant on your orderconfirmation pages.

Sounds like you did not paste the script into the editor correctly which is why it showed on your page. Make sure you switch the editor to Html Source mode (the brackets icon on the bottom edge) before pasting in HTML content, so that the HTML gets interpreted correctly.

Someone mentioned in a previous post that "When 7.0.2.5 is released we will post instructions for using the ga.js javascript."

Am I missing it somewhere? I have "AspDotNetStorefront ML 7.1.0.0" however the new code is not working for e-commerce tracking. Is it not supported still? Thanks.

It is supported by the (!GOOGLE_ECOM_TRACKING_V2!) token place in your skin template or a Topic.

It is supported in the orderconfirmation.aspx with AppConfig Google.EcomOrderTrackingEnabled set true.


Note, that these pull together PARAMETERS and DATA sent out via ga.js. They do not embed that actual ga.js script on the page.

You need to do exactly what you already did, adding it to your skin template.
I might suggest adding it in the head section though, so the script is loaded and ready BEFORE the token or the call in the orderconfirmation page is invoked.

Sometimes pulling the ga.js down from google takes too long and can cause javascript errors.
Some people pull it down and stick it in their own jscripts directory.
If you do that then you just need to be sure to check Google for updates to that script periodically.

Submit a ticket if you continue to have issues.

The knowledgebase says:

ga.js
Applicable Products
AspDotNetStorefront PRO 7.0.2.5 SP1 and higher
AspDotNetStorefront ML 7.0.2.5 SP1 and higher

urchin.js
Applies only to versions 7.0.1.1 or greater

We are using 7025, so should we go with urchin?

Peter