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 Google Analytics Goal Tracking | Event Espresso - Staging Server
I’d like to add a goal in Google Analytics for every user that registers for an event. What ‘head’, ‘expression’ or ‘exact match’ URL should I use for the receipt/completion page?
It may be possible to do this if you’re using a payment gateway like PayPal or Stripe. In these cases, the registrant is taken to an actual thank you page on your site.
First, check for the page that is set as the “Thank You” page, it will have the [ESPRESSO_PAYMENTS] shortcode on it. You can use the permalink for that page as the URL and set the Analytics software to use a “Head Match” for the match type.
Is it correct that neither goal tracking nor ecommerce tracking is available unless we use on these gateways? It doesn’t currently appear possible as successful/unsuccessful payment transactions currently resolve to the same url.
Which gateways are you referring to? While the URL would work fine if you were tracking registrations, the payment data would be different since that currently happens after registration.
The support post ‘Google Analytics Goal Tracking’ 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.