Hi @CreamDevelopment. Thank you for your contribution!
Here are some useful tips on how you can test your changes using Magento test environment.

❗ Automated tests can be triggered manually with an appropriate comment:

• @magento run all tests - run or re-run all required tests against the PR changes
• @magento run <test-build(s)> - run or re-run specific test build(s)
  For example: @magento run Unit Tests

<test-build(s)> is a comma-separated list of build names.

You can find more information about the builds here
ℹ️ Run only required test builds during development. Run all test builds before sending your pull request for review.

For more details, review the Code Contributions documentation.
Join Magento Community Engineering Slack and ask your questions in #github channel.

@CreamDevelopment, please sign CLA

@ihor-sviziev It has bene signed.

Maybe _kx can be added as well? It was proposed in https://github.com/magento/magento2/pull/36796/files#r1095535697, but that PR got closed unfortunately.
_kx seems to be related with Klaviyo: https://help.klaviyo.com/hc/en-us/articles/115005076767

@hostep I do agree, but we also have a separate fixes for that in #35228, so I would just test these 2 Pull Requests together

@hostep @CreamDevelopment @ihor-sviziev maybe we can add a configuration field for this?

@peterjaap, I think it would be too complicated. I think having it like that should be enough

Hi @CreamDevelopment,

Thank you for your contribution!

We are not able to update your PR branch now as the fork is not updated. Can you please update your branch so that we can proceed further on this PR.

Thank you!

As we are unable to update the branch in order to proceed ahead as mentioned in here, closing this PR now. Please feel free to reopen once you are done with the needed.