You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Jun 2, 2021. It is now read-only.
When the signature comes from a visitor without utm parameters, the widget generate "fake" ones with:
utm (website,referrer,hostname+pathname)
We already "socialise" and if the url is facebook or twitter, we update the utm to (social, twitter|facebook)
The next step (on the server, can be a batch running) would be to transform the utm coming from a known webmail domain (mail.google.com, gmx.de...) into a utm(mail, webmail)
We have probably enough actions to get a good overview of the most common webmail domains (in europe)
The text was updated successfully, but these errors were encountered:
When the signature comes from a visitor without utm parameters, the widget generate "fake" ones with:
utm (website,referrer,hostname+pathname)
We already "socialise" and if the url is facebook or twitter, we update the utm to (social, twitter|facebook)
The next step (on the server, can be a batch running) would be to transform the utm coming from a known webmail domain (mail.google.com, gmx.de...) into a utm(mail, webmail)
We have probably enough actions to get a good overview of the most common webmail domains (in europe)
The text was updated successfully, but these errors were encountered: