Forum Moderators: DixonJones
So I was wondering if anybody here could help me with my problem.
I have Webtrends 7 pro on demand and want to track revenue from my Google Adwords campaign is this even possible? If so how do I go about this, the Webtrends docs aren’t helpful at all!
I’ve got as far as creating a test html page below:
<html>
<head>
<title>Test</title>
<META NAME="WT.pn" CONTENT="wigetben">
<META NAME="WT.tx_u" CONTENT="1">
<META NAME="WT.tx_s" CONTENT="101">
</head>
<body>
<!-- START OF SmartSource Data Collector TAG -->
//there long data collector
<SCRIPT LANGUAGE="Javascript">
</SCRIPT>
</body>
</html>
Will this work? Am I way of? And this there any easy way to test this without having to go live with it.
Thanks a lot
Ben
The answer to the main question is that WebTrends and almost all of the javascript tracking systems can certainly report on revenue from Google AdWords etc.
This test page is the page that is shown once the conversion has been completed e.g. "Thank you for buying this product" – so yes this is sample confirmation page.
Will that code that I posted before now show up in the “Webtrends>marketing>dashboard>Most Recent Search Engines (Organic)”?
And if so is there an easy way to test this without going live?
One thing you may have omitted is a way for WT to know whether the visits are from an organic or a paid search engine. WebTrends can recognize search engines just fine, but it needs your help to know if the search engine is a paid one or not. As you may know, there's often nothing in the log to distinguish paid from organic search visits. WT will assume all search engine-originated visits are organic except where it sees that the visit's entry page has the parameter WT.srch=1 in the URL. This, of course, is forced into the URL by you when you supply destination URLs in your paid search links. If you don't have this parameter pair in your URL for your paid links, WT will report those visits as organic.
As for your confirmation page, I think you might need pn_sku not pn, but tx_s and tx_u are right. And you need tx_e=p to tell WT that the page view signifies a purchase, I believe.
In your confirmation page, if somebody buys more than one item in an order, remember that all those WT parameters have to have double entries - 2 prices, 2 unit amounts, 2 product IDs. You may be working with older documentation that doesn't make it clear that you have to have 2 values for tx_s.
Finally, I'm curious about your comment about $$ and support. WT has an awful lot of documentation and support online, free trial copies, complete live demos of the product and so forth, plus they don't charge for phone support at all, other than the toll call. All this stuff is in the documentation several times over. Did they tell you they would charge you to help with this?
I completely over looked the fact that Webtrends wouldn’t be able to tell the difference between paid and organic.
And thanks for the idea of using the software trail to test it out (I don’t like handing my credit card out though). My problem is that I work for a large cooperation and one scripting change such as JavaScript takes a week to go live, which is very frustrating.
About my comments on support. I live all the way down in New Zealand and calling up can be quite expensive and having to worry about time zones isn’t great. The redistributes of Webtrends down here in Australia is a useless company who takes an average of two days to answer my emails. Just to find out that you have to purchase a support plan – so they did tell me they would charge me for support. Also I’ve had a good hunt around and I can’t seem to find any decent documents on setting this up a few pieces here and there but nothing definitive.
Now I would loved to be proved wrong but so far I have had a bit of trouble with Webtrends.
Any way thanks again for your comments this has cleared a lot up.
Ben
