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 Apr 17, 2023. It is now read-only.
Currently all Twitter verification tweets include a link to https://blockstack.org/try-blockstack, even though that resource not permanently redirects to App.co.
As a consequence, Fathom is not tracking this inbound traffic by referrer, for either domain. We should update these tweets to include a link to http://app.co/ directly instead of https://blockstack.org/try-blockstack so that Fathom attributes this traffic to Twitter effectively and we can determine accurately just how much Twitter proofs are driving in-bound interest.
@CharlieC3@cuevasm@wileyj I believe this change is necessary to get a proper read on this traffic before we can make any decision as to whether we want to keep Twitter proofs or not in the legacy Blockstack Browser. Please let me know if you have any other ideas though.
The text was updated successfully, but these errors were encountered:
Currently all Twitter verification tweets include a link to https://blockstack.org/try-blockstack, even though that resource not permanently redirects to App.co.
As a consequence, Fathom is not tracking this inbound traffic by referrer, for either domain. We should update these tweets to include a link to http://app.co/ directly instead of https://blockstack.org/try-blockstack so that Fathom attributes this traffic to Twitter effectively and we can determine accurately just how much Twitter proofs are driving in-bound interest.
@CharlieC3 @cuevasm @wileyj I believe this change is necessary to get a proper read on this traffic before we can make any decision as to whether we want to keep Twitter proofs or not in the legacy Blockstack Browser. Please let me know if you have any other ideas though.
The text was updated successfully, but these errors were encountered: