-
Notifications
You must be signed in to change notification settings - Fork 9.4k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Google Adwords add ability to provide transaction-specific conversion values in your conversion tracking tag #6708
Comments
@XigenDominic Unfortunately, I could not reproduce the issue as you described it. Read this article from Google about "How to track transaction-specific values on a website" and let me know if it helped you https://support.google.com/adwords/answer/6095947 |
On that link you sent Part 3: Add or modify the tag in your website's code Expand PHP: Hypertext Preprocessor (PHP) Should see "To add conversion tracking code to PHP pages using your web page editor, look to the code below, then remove from your own code the lines that are crossed out,..." [...] |
Part 3 point 5 (Optional) If you accept different currencies, add a line within the if statement to accept currency: var google_conversion_currency = $currency. In the noscript section of the tag, be sure to add ¤cy_code= $currency |
That example is from the google docs. But okay, in my case the if statement doesn't exist. |
Thank you for your submission. If you are looking for some advice or discussion on that, please refer to the Community Forums or the Magento Stack Exchange site as GitHub issue tracker is intended for technical issues only. |
Internal ticket to track issue progress: MAGETWO-71642 |
…unctional tests (#6708) * MCP-242: Extend Customer Group Limitations by websites functional tests
Google Adwords Code does not allow providing transaction-specific conversion values in your conversion tracking tag
Preconditions
Steps to reproduce
Expected result
https://support.google.com/adwords/answer/3419241?hl=en-GB
Actual result
The text was updated successfully, but these errors were encountered: