I'm running an online store on Magento. I have Google Checkout as a Payment method. The problem is if someone pays using it they don't always return to the site so it throws my Google Analytics conversion rates off. Is there a way to pass this information to analytics when the people don't return to the site after the transaction?
Magento has built-in support for sending data about Google Checkout process to Google Analytics. Implementation of this functionality is done according to
http://code.google.com/intl/ru/apis/checkout/developer/checkout_analytics_integration.html
You should see all the data (e.g. pages visited) and conversions from GC normally. The customer is not required to return to your shop.
Step1: no GC conversions in GA
Allow up to 24h delay before the conversion data will appear in GA.
Step 2: After 24h you still don't see GC conversions in GA
Make sure you've enabled Google Analytics in Magento and setup it properly, because GC module in Magento sends data to GA only if it's activated and working fine.
Step 3: If steps 1-2 are done, everything works and GA is activated, but GC conversions still not visible in GA
Make sure that your design theme includes all necessary GC & GA code as made in base/default scheme. You can temporarily enable default/modern theme to check that original core Magento code works fine and then check the differences between your design theme and Magento core theme
Step 4: you've done steps 1-2-3, but no conversions are present in GA
Hire a Magento professional to find the source of a problem. In such a case this problem cannot be solved remotely.
The only data that comes back from Paypal after the customer has paid would be the IPN callback that notifies Magento of the payment. If you wanted to hook into this, you would need to find a direct URL to notify GA of the conversion and to periodically monitor the database for IPN notifications so that you could invoke that URL.
Related
I have created an ecommerce store, and I'm using PayPal "Add to Cart" Buttons with what they call 'hosted' buttons (PayPal stores the buttons on their servers) for each of my products.
For reference on how they work (and why I use them):
You create a button(product) inside your PayPal Dashboard and you define the quantity available (most of them are 1 in my case)
You copy the HTML code into your website (or just copy the link)
The user buys the product (and the quantity falls -1)
The reason I use this setup is because my website is static, and PayPal provides the Quanity (SKU) Management - so no one can buy a product that no longer exists - even if he can access the button/link.
My Problem
The PayPal GUI dashboard for creating buttons is very time-consuming, I would like to have the ability to edit/create etc. buttons in bulk.
I had search and search for a solution online but have found nothing.
Possible Solution
The only thing I've recently gave some thought was the PayPal Button Manager API and the Ruby SDK in particular, but even if I've studied programming and I'm really eager to keep learning more, I don't know yet what to do in order to make the API calls.
I can't understand from their documentation and I have found zero tutorials online for such a thing.
Failed Solution
As I was familiar with WordPress I tried installing a plugin called PayPal Button Manager but it hasn't the ability to edit in bulk, which is what I'm trying to do.
All in all, I want to:
Create, Edit, Delete, Update in bulk PayPal Hosted Add to Cart Buttons
If using the Ruby API, I would much prefer doing so in a local environment
I'm using Jekyll for my static site, so I'm having Ruby installed and have read multiple times that it's an 'easy' to learn language. But if you can think of something else, I'm open.
If you have Wordpress, then you have a local database, and might end up much happier with a solution that stores quantities locally in that database, such as the WooCommerce plugin, with the following additional plugin for payment: https://woocommerce.com/woocommerce-and-paypal/
Your proposed solution of using PayPal Standard Buttons with the legacy PayPal Button Manager API .. is extremely unconventional in contrast, and would be considered a "terrible, horrible, no good, very bad" hack by most.
I would like some advice and a little help.
A recent project I have been working one had its version of SagePay upgrade to use the version 3 protocol. The side of effects of this meant that users are no longer able to edit their billing address details. The previous protocol v2.23 did allow this in low profile mode and in normal mode.
Further more from what I have understood in the new protocol, iFrames are no longer being supported.
I have read the documentation which suggests downloading the custom templates (Card_Details.xslt and Card_Details_Low.xslt), customising them and sending over to SagePay in order to add these to the system. But I am unable to find any instructions on how to achieve this.
How I allow the customer to have the ability to change the billing address?
Any help will be appreciated.
Thanks
Change the template you are using (in My Sage Pay) to Default. That should set things back to how they were.
FYI - iframe integration is still supported in v3.00
I'm working on a joomla site for a charity event. The event has 5 causes to donate for each with its own page. I have created paypal donation buttons for each of the five causes using this site: https://www.paypal.com/cgi-bin/webscr?cmd=_donate-intro-outside. That all works fine but I need to accomplish two more things. 1) How do I display a summary of the donations for each cause on its respective page and 2) How do I display a total donations received across all 5 causes on the home page?
I am currently going into the paypal account and updating these values manually every night. I know there has to be a better way. I think I have to do something with IPN but I can't find any good documentation. I'm not a php programmer so I need some hand holding but I can get through it with some help.
I have searched high and low for a Joomla extension to do this but I just can't seem to find anything that fits my situation. Any help would be appreciated.
Thanks!
I don't think you'll be able to pull this off without some PHP programming and a good integration with Joomla.
As a general overview you will have to:
activate and configure IPN (Instant Payment Notifications) in PayPal
for your buttons configure the notify_url (the URL where PayPal should send the IPN)
on the Joomla site you will have to process those notifications and save into a database the transaction information that you get
finally - on each of your pages you will have to do a database look up and compute the totals that you require.
I have used Jumi (Joomla extension) to implement something similar to what you need, but it does require a lot of PHP programming to do it like this.
I have a Magento site using version 1.6.2.0 with which I'm experiencing problems with duplicate orders.
Having researched the subject I have found mostly forum threads explaining that 1.4.x had problems with duplicate orders and the solutions mentioned (even those on SO which I have found) merely suggest the user updates Magento to >1.4.
I have also found a proposed solution here but am reluctant to delete observers which will prevent downloadable purchases working.
I've also spotted the Array Of Death fix mentioned a few times (e.g. here) but this problem isn't present in 1.6.x, Zend appears to have resolved it.
There are a couple of Javascript hacks suggested whereby the Confirm Order button is hidden upon submission but Magento 1.6.x already does this.
I have increased the payment gateway timeout configuration variable to 120 seconds and am as yet to see if it yields results. I can't test it as the problem is intermittent (and probably therefore caused by communication or lack thereof between the payment gateway and Magento).
I am using Sagepay as the payment gateway.
How might I further debug this?
The link you posted is correct, but I wouldn't use their fix, I would just disable the Mage_Rss module.
Mage_Rss has several observers in it that call Mage::app()->cleanCache(...) in the checkout process, which is extremely expensive if your installation is using the default filesystem cache and it's gotten large.
I found the best thing for troubleshooting Magento performance problems is to wire up Xhgui and do some profiling. Reading call stacks will help your understanding of Magento immensely also.
Oh, and I don't know if this is true for Sagepay, but I went and fixed this problem completely for PayflowPro by rewriting the method that generates transaction IDs to use the quoteID instead of generating unique IDs on every invocation. I started down the path of committing this back, but I'm on 1.4.2 still and don't have time to test in later versions and it's a pretty significant rewrite. Guess I could just put it out there for someone else to run pass Moses...
I'm having an issue with Google Analytics ecommerce tracking. I've found numerous posts about this, but none of the fixes seem to apply. We're on Magento 1.5.0.1, so all the GA code should be built in. We also installed the Fooman GA+ module, but that didn't help this issue. The tracking code IS showing up on the success page when viewing the page source, but it doesn't look right...no items listed. If I view the list of transactions in GA, it seems that they are all the Paypal transactions but credit card or money order transactions aren't coming through. We use Website Payments Pro for our Credit Card transactions, so ultimately it's all going through Paypal anyhow.
I did some digging around in the code and it seems that the "_getOrdersTrackingCode" function in Ga.php is where the problem lies. I added some logging...
$orderIds = $this->getOrderIds();
Mage::Log($orderIds);
...and found that the majority of the time, $orderIds is empty. Sometimes it isn't and that is when the tracking code works.
What's going on here? Anyone know?
I have fixed the problem. We use a 3rd party extension for checkout and it needed to be updated for 1.5.0.1 compatibility. The dispatcher of the *checkout_onepage_controller_success_action* event needs to send an array of the order ids as well. This wasn't necessary in 1.4.2.0. I updated the extension and it's working great now! I hope this helps anyone else with a similar issue.
Please note that this is an ORDER COMPLETE / SUCCESS event. You can't see the rendered code until you've completed a (test) transaction. On the order confirmation page, hit view source. In your <script /> tag's you'll see some new push code if all goes well.
Yes, Brian, your code definitely lead us in the right direction. We ended up turning the PayPal checkout to test mode = yes, debug mode = yes. We're on 1.4.2. and this worked fine. Respond to this if you need help. If I'm alive, I will try to get back to you.