Welcome to WebmasterWorld Guest from 22.214.171.124
Forum Moderators: buckworks
Google is offering merchants free use of its online payment service as it squares off against eBay's market-leading PayPal.
The Internet search giant introduced Google Checkout in June, with sweeteners such as free ad credits for merchants. In November, it began offering rebates to consumers, $10 off $30 purchases. PayPal quickly matched the offer.
Wednesday, Google ratchets up the pressure by dropping merchant fees through 2007.
Ecommerce: Google Offer Takes on PayPal [usatoday.com]
There was, what seems like a similar issue when AdSense came out, (no tracking)...
There may be some clues in that thread about how to code your own tracking --- you'd still never see past the checkout point, but at least you'd have some solid data on who you sent there, when, what they clicked.. etc..
If your affiate check is big money from certain merchants, this may help you negotiate some type of payment (if the affiliate code was scrubbed if your referrals ...and if they value your traffic).
...and discovered I needed to be located in the USA
AlexK, thanks for saving my time.
...I escalated this to the Google Checkout folks as soon as I heard about it, so I know they're looking to see if there's anything they can do pretty quickly to help on this issue.
I don't know the names of the tech folks at CJ & LS, but Larry Adams would be the tech person to contact at Peformics and Brian Littleton (the Pres. & CEO) at Shareasale for input - all of which would probably also pertain to tracking for the indies as well.
Please allow me to go on record saying that I have no problem at all, whatsoever, with creating a Google account. In fact I've already done so, as well as running the Google Toolbar in IE 24/7, using the customized G homepage and using Gmail, and staying logged in to all - all the time, including my Gmail (for which I have the homepage preview enabled), and GoogleGroups - Webmaster Help included, under the watchful eye of Adam L. (LOL) - as well as having set up a GoogleGroup and Calendar for my church's website - without even one, single, solitary, little itty-bit of paranoia.
There's simply no place for tinfoil hats when it comes down to the practical reality of effective ecommerce and internet marketing. Reality rules.
Did the fact that I used the cute cartoon of you pushing Checkout in my blog help get your attention? ;-)
I'll be sure to let people know in the forums and blogs discussing this that Checkout is looking into it, thanks to you! I'm in a private affiliate manager only forum discussing this with affiliate managers from many of the top etailers and will them know too. You ROCK!
Thanks for the help,
I think PayPal now supports Micropayments for UK sellers
Thank you for that.
I found the relevant page by searching for "PayPal Integration Center micropayments" (HTTPS and cannot be linked here).
url = [paypal.com...]
The page states:
PayPal offers support for Micropayments to merchants for US to US, GB to GB, AU to AU, and EU to EU transactions for Business and Premier accounts. This feature is offered at a special rate of 5% + $0.05 per transaction.
I guess that the point re:Google is that their micro-payments are now the lowest on the market... as long as you are resident in the USA, of course.
Please allow me to go on record saying that I have no problem at all, whatsoever, with creating a Google account.
I have no problem with it whatsoever either - personally. But my problem is that I cannot integrate Google Checkout as a primary form of payment collection into my various ecommerce clients' sites when it requires a Google Account first - most of these are B2B sites, and we're already concerned with the time it takes for users to create a store account, without adding the creation of a Google Account into the process as well. The business users are an impatient bunch - most don't use PayPal for business transactions either.
This is kind of a downside since its real nice to use the same login for adsense, adwords, checkout, etc..
1 Only for USA
2 The buyer has to create a Google account first
Of course, if they fix these we're very interested.
Re.2: buyer has to create a Google account first
Perhaps I misunderstand a previous post. I assumed the post meant the buyer has to setup a Google account. I don't care about setting up an account, but site visitors wanting to buy stuff should not have to jump through that hoop. This is one reason we didn't use PayPal, they changed (ie you don't have to have a PayPal account to buy) so now we setup PayPal on some sites.
IMO PayPal is the most confusing payment provider (for the buyer), so I tend to recommend other providers. Last month I setup a test group and watched them all try to use PayPal (most of them for the first time ever). These were inteligent folk, most of them were Managers of teams in a Global company. It was staggering to watch, about half of them made serious mistakes and could not complete their transaction. The problem with PayPal is the extra links that confuse non-web-savy buyers e.g. 'Click here to setup your PayPal account, or click here to just buy the damn thing...' (well, something like that). There has to be a linear checkout WITHOUT ANY side-tracks to get lost in. Protx does this very well, but PayPal is a nightmare.
Documentation for pixel tracking went live I believe late last night:
I think pixel tracking in Google Checkout should help with this issue.
(Also posting this on TW and the original SEJ article)
I want to say, "Why the hell would you give a basically unknown website your credit card info and not Paypal" but you just can't do that with a customer.
I am anxiously awaiting Google Checkout but it has to break out of the US and cover ALL countries in the world where primary method of travel is not a donkey.
(1) How many people here are wondering whether an account is required for a customer to check out? That's because Google doesn't bother to make that information clear, up front.
(2) I took a look at the docs to see how I might convert from PayPal, and there's all kinds of technical jargon, like API's, XML, parameterized URL's, etc. I'm not keen on learning several new concepts/technologies just to add a different checkout option, especially when my PayPal solution is already working, and all it required was some simple HTML (and Perl to receive the order info back from PayPal to put it in a database).
(3) How do I pass custom info to Checkout that I can get back once the order is completed (e.g., affiliate ID, referral URL, etc.)? PayPal gives you a simple custom field (<input type=hidden name=custom value=whatever-you-want>), but I didn' see any such in the Google docs. Instead of a simple custom field I'm supposed to use PIXEL tracking?! Are they NUTS!? Granted, this is more of a problem with their implementation than with their documentation, but still....
(4) Knowing that many people considering Google Checkout will be migrating from PayPal, the obvious thing to do is to have a PAYPAL MIGRATION GUIDE that helps such webmasters along the way. (e.g., a two-column table, with the headings "How you did it in PayPal" and "How you'll do it with Google Checkout") A side-by-side feature comparison wouldn't be a bad idea, either, showing what features that are available in one service but not the other.
Is it inevitable that as companies grow and get older they also get lame?
Extremely unimpressed. I'll stick with PayPal (which is already set up and works) for the 2.5% transaction fee.
A lot of things really take being made "idiot proof" to be easily understandable to everyone at all levels, especially those who are in a hurry - which is a lot of people nowadays.
Unfortunately, there aren't a whole lot of technically challenged people at Google - at least I imagine not - so what they need is some volunteer "token idiots" to alpha or beta test not only their offerings' features, but to check for how understandable documentation is, very early on.
so what they need is some volunteer "token idiots" to alpha or beta test not only their offerings' features, but to check for how understandable documentation is, very early on.
I wholeheartedly agree! Why Google thought they could skip this step is a mystery. Perhaps they think they know best and don't need to know what their customers think -- which is a kind of corporate arrogance. If they keep it up, it will limit their success. They've certainly lost me as a potential merchant, even though I was *anxious* to try a viable alternative to PayPal.
I've almost finished coding an affiliate program from scratch, and before I launch it to the world the first thing I will do is ask a couple of non-techie, simple webmaster friends to go to the site and sign up for the affiliate program. I won't give them any further direction or explanation, they need to get everything from the site. And I'll be able to find out from them what questions weren't answered, what was confusing, what they would have preferred to see, etc.
Now, I have far less resources than Google. I'm a one-person shop. Surely Google could out-perform me in this department...if they wanted to.
Google Checkout, matched with AdWords, will definitely be a hard product to beat since they will provide promotions for use with both.
PayPal has no real tactic except that they are established. Ebay and Paypal are both products that are not going to survive well placed competition. Their customer support is worse than horrendous and their products and mechanisms are not very good. Amazon, for example, is far more attractive than Ebay for resellers.
That being said, Google has to expand and offer the perks they are offering. But they NEED international support. They need to at least match Paypal in usability.
Once they do this, I have no doubt that Google's ability to create easy to use systems with top notch tech support will make google checkout a great product. The google brand is also extremely trustworthy in the eyes of both merchants and consumers.
All they have to do is make a payment gateway:
- With the Google brand, for trust.
- As easy to pay for stuff as Protx or WorldPay,
- No funny hoops to confuse buyers (like setup an account to pay).
- Provide the Merchant Account for those who don't have one,
- As easy to setup as PayPal,
- A helpline for webmasters.
Bang! They will be taking a commission on millions of sales per day, and become the worlds most popular payment gateway.
So, why are they making it difficult?
I remember a few years back before the big IPO, Jill Whalen made the prediction: "If Google goes public, expect them to start to suck within a year." Maybe she was right, though not necessarily on the timeframe.
technical jargon, like API's, XML, parameterized URL's
I don't understand what you expect. If you want to run a shopping cart online, you need to understand that stuff because it's not jargon it's technology. If you don't feel like learning it, you hire someone who's competent with the technologies involved. Sheesh.
Żes user-friendly documentation is always a plus but theres only so far you can lower the denominator before the techies complain that theres too much fluff.
I don't understand what you expect.
I thought I made that clear: Documentation that's as easy to understand as PayPal's.
PP's documentation could be improved, to be sure, but it was mostly enough to get me up and running. I certainly didn't have to screw around with XML, API's, or parameterized URL's.
Bottom line: If Google wants the small webmaster as a customer, they need to make their docs accessible. Faced with the choice of either "hiring someone competent with the technologies" or just sticking with PayPal, which do you think the small webmaster will choose?
I know what I chose.
NO WAY is Google on the downhill path since or because of going public. There is no way stockholders, who may have investment smarts but little else technical and otherwise, could know about how to operate search quality or algo construction, etc., etc., and have any say in the functioning of those.
I fail to see what could be objectionable about making documentation replete with essential details and the kind of clarity that's understandable for all levels of users. Unfortunately, geeks and techies are not necessarily capable orf writing idiot-proof instructions and documentation.