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
a way to trace/log purchasing process? | Event Espresso - Staging Server

Support

Home › Forums › Event Espresso Premium › a way to trace/log purchasing process?

a way to trace/log purchasing process?

Posted: February 18, 2014 at 8:45 pm

Viewing 3 reply threads


TODD

February 18, 2014 at 8:45 pm

Hello —
I have a fair number of sign-ups which are ending at the “incomplete” status and not completing the credit card processing step. Is there any way to identify why this is happening? Is there a log somewhere which shows any step the user took, i.e., clicked through to credit card screen but abandoned page, etc.? I suppose I can look at my apache log but if there is any tracking of this detail (or a way to enable it) it would help me to identify why I am getting a lot of incomplete registrations.

Please let me know.
Thanks,
-Todd
—
EE 3.1.36.4.P
EE calendar, members addon, multi-event reg, recurring events, roles & permissions pro.


Seth Shoultes

  • Support Staff

    •

February 18, 2014 at 9:17 pm

Hi Todd,

You can try checking logs in the wp-content/uploads/espresso/logs/ directory. Some payment gateways will keep a log of successful and failed transactions. If you would like to start tracking everything that happens when Event Espresso is loaded, you can turn on full logging within the Event Espresso > General Settings > Advanced Features page.


TODD

February 21, 2014 at 4:17 pm

I’ve activated the log but I’m wondering if there’s a way to see things like why someone would be marked “incomplete”. I’m getting a fair number of people that go through the registration process and stop… and result in an “incomplete” registration status. It’s driving my customer up the walls.

Can you tell me what you’d suggest as a way to identify why this is happening with the customer (and I realize they could simply think they’re done, or abandoning the process, but… it would be nice to have more detailed info, if at all possible on why it happened from event espresso side. — i.e., something technically indicated like “browser session closed”, “customer abandoned page”, …or something else?


Dean

  • Support Staff

    •

February 23, 2014 at 11:59 pm

Hi,

Everyone is marked as incomplete until they pay. The logs will provide you with more info as to whether it was a payment error or did they simply not pay.

Figuring out WHY they didn’t pay is the harder issue. Personally I would contact a few of the customers and ask them.
Viewing 3 reply threads

The support post ‘a way to trace/log purchasing process?’ 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.

The original Forum description...

Status: closed

Updated by Dean 10 years, 11 months ago ago

Topic Tags

Notifications

This topic is: not resolved
Event Espresso - Staging Server