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
Revisit: Updating referrer attribution of a visit when 2 channels are used within a same visit (current behavior is to override a "Direct" channel whenever possible) #19657
Comments
This issue has been mentioned on Matomo forums. There might be relevant details there: https://forum.matomo.org/t/multi-channel-conversion-attribution-models-comparison/45580/12 |
This issue has been mentioned on Matomo forums. There might be relevant details there: https://forum.matomo.org/t/marketing-campaigns-tracking-cross-site/47909/2 |
Hi, are there any updates on this issue? I still have problems that sessions wherein a visitor pays via paypal are attributed to paypal as a referrer, which makes ad attribution impossible,. Thanks Jens P.S.: I think this is the biggest show stopper in matomo which makes it impossible to use it in a professional way. Currently, if you really want to attribute sales when using Google ads, the only way forward is to use Google Analytics, since all payments via paypal are not attributed correctly. Am I really the only user that wants to use Matomo in a professional way? Also, how can Motomo expect to sell the Google Ads plugin for 150 $/year if the majority of sales cannot be attributed to the Google Ads channel? |
Hi @frimipiso |
This issue has been mentioned on Matomo forums. There might be relevant details there: https://forum.matomo.org/t/setconversion-attributionfirstreferrer-is-not-working/53798/2 |
This issue has been mentioned on Matomo forums. There might be relevant details there: |
This issue has been mentioned on Matomo forums. There might be relevant details there: |
This is a follow-up issue to the discussion in #18612
Summary
When a visitor visits the page, the visit will be attributed to a certain referrer. This can currently be
website
,campaign
,search engine
orsocial network
. If non of this referrer can be detected the visit will be attributed asdirect
.When a visitor afterwards revisits the page coming from another referrer and the referrer was previously attributed as
direct
, we currently may update the attribution to this new referrer. See workflow below:Current Attribution workflow
Conclusion
Updating the referrer in that case might not be correct, as the visitor initially came directly to the page, but would then be attributed to another channel.
As far as I know the code to update the referrer was initially added to fix some issue, where the referrer was not yet set with the first tracking request, but was sent with a later one. Not updating the referrer in that case, would then mean incorrectly attributing the visit as direct, instead of the correct referrer.
A possible solution could be to only set/update the referrer until the very first page view tracking request of a visit. This would solve the issue, that other tracking requests might have already created a visit without a referrer, as it would then be updated with the page view request.
Changing any behavior in referrer attribution might result in differently tracked data and thus changing numbers. As this might bring trouble, we should not change that outside of a major release.
Also we should consider to do that using a config flag, that will only be activated for new installs automatically, so it won't harm any existing install by default.
The text was updated successfully, but these errors were encountered: