Skip to content
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

[ECP-9592] Remove utm_nooverride parameter on checkout success #2846

Open
choussamaster opened this issue Jan 8, 2025 · 1 comment
Open
Assignees
Labels
Bug report Indicates that issue has been marked as a possible bug

Comments

@choussamaster
Copy link

Currently Google Analytics is reporting tracking issues with checkout success url due to "utm_nooverride" who's added by adyen.
This parameter is no more supported and need to be deleted.

Describe the bug
After payment the customer is redirected to /checkout/payment/sucess?utm_nooverride=1

To Reproduce
Pass an order, validate payment, check payment success page URL

Expected behavior
After payment the customer is redirected to /checkout/payment/sucess

Magento version
2.4.4

Plugin version
9.11.0

Screenshots
google_response

@choussamaster choussamaster added the Bug report Indicates that issue has been marked as a possible bug label Jan 8, 2025
@khushboo-singhvi
Copy link
Contributor

Hello @choussamaster,

Thank you for bringing this to our attention.

We’ve reviewed your report regarding the usage of the utm_nooverride parameter in the redirection logic, and we’re in the process of addressing it. An internal ticket has been created, and the necessary changes will be made to remove the deprecated parameter from the code.

We appreciate your contribution and will update you once the fix is implemented. If you have any further insights or suggestions, please don’t hesitate to share them.

Best regards,
Khushboo

@khushboo-singhvi khushboo-singhvi changed the title Remove utm_nooverride parameter on checkout success [ECP-9592] Remove utm_nooverride parameter on checkout success Jan 15, 2025
@khushboo-singhvi khushboo-singhvi self-assigned this Jan 15, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Bug report Indicates that issue has been marked as a possible bug
Projects
None yet
Development

No branches or pull requests

2 participants