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
Additional External Form Submission AFTER payment confirmation | Event Espresso - Staging Server

Support

Home › Forums › Event Espresso Premium › Additional External Form Submission AFTER payment confirmation

Additional External Form Submission AFTER payment confirmation

Posted: October 22, 2013 at 9:04 am

Viewing 1 reply thread


Wesley Deer

October 22, 2013 at 9:04 am

We have an external CRM system (Act-On) that we’d like to pass the registrants info to..
Act-On provides code to mirror your form via PHP, jQuery, vanilla javascript, or hidden form.. but is there an event espresso custom function or page in which we can trigger this to happen after the payment confirmation?


Sidney Harrell

  • Support Staff

    •

October 22, 2013 at 11:54 am

The template payment_overview.php is triggered after the attendee comes back from a payment gateway, and you could add your code in there. We did add several hooks for adding attendee data to an external CRM system. You could add a function to the ‘action_hook_espresso_save_attendee_data’ hook, which is passed an array containing the attendee data. It is triggered before the attendee is sent off to the gateway, but there are other hooks which you can use to update the attendee’s payment status.
Viewing 1 reply thread

The support post ‘Additional External Form Submission AFTER payment confirmation’ 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 Sidney Harrell 11 years, 3 months ago ago

Topic Tags

Notifications

This topic is: not resolved
Event Espresso - Staging Server