-
-
Notifications
You must be signed in to change notification settings - Fork 3k
Remove Identify visitor by tracking url configuration setting #14974
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
Conversation
…espace in ContactRequestHelper files
Codecov ReportAll modified and coverable lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@
## 7.x #14974 +/- ##
============================================
- Coverage 66.49% 66.47% -0.02%
+ Complexity 35186 35178 -8
============================================
Files 2317 2317
Lines 141875 141855 -20
============================================
- Hits 94335 94305 -30
- Misses 47540 47550 +10
🚀 New features to boost your workflow:
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
As far as I know, the feature places the contact email address as part of the URL to help the tracking script understand who is that contact to then create a cookie
This seemed particularly useful for cases when GDPR or business privacy choices are limited by anonymized IP and the website has cookie modules for blocking everything before users can or not set their consent, or when you need to identify the contact within a CMS based on the email contained on the URL
I feel the removal might break some of the use cases, what do you think?
@andersonjeccel I'm not sure what you're referring to. Just a few lines above (https://github.com/mautic/mautic/pull/14974/files#diff-ff1cf0e25a20c2ebe5f252374318df2cb7aa36bb6c880db1a693f3e2e2e4ec8cR120) does the same thing. Identify contact from tracking URL by default. |
@kuzmany Most things I ask as end user, just can't understand looking at the code :/ Thank you for replying |
@escopecz please |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I can't find in the email subscriber where it handles $clickthrough['lead']
like in the removed code. Can you send me a link?
@escopecz this method make it (mergeWithTrackedContact)
|
Co-authored-by: John Linhart <admin@escope.cz>
@kuzmany I went through the subscribers and couldn't see the |
|
@escopecz same subscriber as for email redirect links is for sms. These subscribers handle identification. This way what we remove still need field mark as public updateable, I guess nobody enabled it. |
@kuzmany I think we don't understand each other. You are removing code that is getting the identification from the clickthrough array based on the Does that mean that this clicktrhough key is unused and other keys are used to identify the contact? |
@escopecz I understand what you are trying to say. But this feature is so complicated and not useful. And require manual steps to use it (nobody use it) Main purpose build it years ago was identify contact from redirect links from emails. This is now cover in subscriber for email redirect links and for sms as well. Identify from email tracking link is already covered. We cannot keep this old, legacy and not useful way to identify contact. Another way would be improve it without use publicly updateable option. But If you decide, you can close it. |
@kuzmany I'm all for removing stuff that no one uses. My only worry is that we'll break something. I can't spend hours researching each PR that I'm asked to review. Even when I try to timebox every review I still am behind and the queue is getting worse every day. That's why I'm asking dumb questions that I could answer myself with my own research. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I believe you are correct. Using the contact ID isn't optimal and seems like an outdated way to do it. It was replaced with the LeadEvents::ON_CLICKTHROUGH_IDENTIFICATION
event and every plugin can hook into that. The EmailBundle is implementing it and finds the contacts based on the email stat hash. That is present since 2018 so I think the email links generated before that are irrelevant these days and it's safe to remove it.
The new implementation is here:
$stat = $this->statRepository->findOneBy(['trackingHash' => $clickthrough['stat']]); |
This pull request has been mentioned on Mautic Forums. There might be relevant details there: https://forum.mautic.org/t/public-release-of-mautic-7-0-alpha/36111/2 |
Let's get this merged into M7-alpha as it's a BC break. Too bad there isn't any second reviewer. |
I do not really know how to test because my understandings of tracking are not that good but with a little help I would test it |
|
Remove Identify visitor by tracking url configuration settings usage
Description
📋 Steps to test this PR:
Seems like we do not need this option in configuration. From some refactoring, contacts are identified by CT parameter by default with the line: https://github.com/mautic/mautic/pull/14974/files#diff-ff1cf0e25a20c2ebe5f252374318df2cb7aa36bb6c880db1a693f3e2e2e4ec8cL122