Notice: Function _load_textdomain_just_in_time was called incorrectly. Translation loading for the pue-sales domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the init action or later. Please see Debugging in WordPress for more information. (This message was added in version 6.7.0.) in /home/staging-poc/public_html/wp-includes/functions.php on line 6114

Notice: Function _load_textdomain_just_in_time was called incorrectly. Translation loading for the better-click-to-tweet domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the init action or later. Please see Debugging in WordPress for more information. (This message was added in version 6.7.0.) in /home/staging-poc/public_html/wp-includes/functions.php on line 6114

Notice: Function _load_textdomain_just_in_time was called incorrectly. Translation loading for the pue-amazon domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the init action or later. Please see Debugging in WordPress for more information. (This message was added in version 6.7.0.) in /home/staging-poc/public_html/wp-includes/functions.php on line 6114

Notice: Function _load_textdomain_just_in_time was called incorrectly. Translation loading for the pue-stats domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the init action or later. Please see Debugging in WordPress for more information. (This message was added in version 6.7.0.) in /home/staging-poc/public_html/wp-includes/functions.php on line 6114

Notice: Function _load_textdomain_just_in_time was called incorrectly. Translation loading for the wordpress-seo domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the init action or later. Please see Debugging in WordPress for more information. (This message was added in version 6.7.0.) in /home/staging-poc/public_html/wp-includes/functions.php on line 6114
Implementing Ecommerce Tracking - Web Tracking (ga.js) on Event Espresso | Event Espresso - Staging Server

Support

Home Forums Event Espresso Premium Implementing Ecommerce Tracking – Web Tracking (ga.js) on Event Espresso

Implementing Ecommerce Tracking – Web Tracking (ga.js) on Event Espresso

Posted: April 3, 2014 at 7:46 pm

Viewing 0 reply threads


Rosemarie Withee

April 3, 2014 at 7:46 pm

Hi,

Our team would like to get more data from Google Analytics especially on the ecommerce side. I’ve read about this: https://developers.google.com/analytics/devguides/collection/gajs/gaTrackingEcommerce but how do i implement this on Event Espresso? Any suggestions on how to maximize Google Analytics on Event Espresso? We’re hoping to get more data than just knowing the number of visitors. thanks!


Josh

April 4, 2014 at 9:57 am

Hi Rosemarie,

It will depend on what information you want to track, and also which version of Event Espresso (3 or 4) that you’re running.

For example if you are using Event Espresso 3, your developers could add the tracking code to the end of the payment_overview.php template. To track instances of completed payments only, the tracking code code by added like so:

<?php
switch ( $payment_status ) {
  case 'Completed':
    // tracking code goes here
  break;
		
  default:
  echo "<!-- not complete -->";
  break;
}
Viewing 0 reply threads

The support post ‘Implementing Ecommerce Tracking – Web Tracking (ga.js) on Event Espresso’ is closed to new replies.

Have a question about this support post? Create a new support post in our support forums and include a link to this existing support post so we can help you.

Event Espresso - Staging Server