관리-도구

편집 파일: .1656537082.M475012P31462.fin.finestweddingsites.com,S=17211,W=17504:2,RSaf.165310

Envelope-to: diane@finestweddingsites.com,
 Ashley@finestweddingsites.com,
 lisa@finestweddingsites.com
Delivery-date: Wed, 29 Jun 2022 16:11:22 -0500
MIME-Version: 1.0
References: <44599D59-8386-4AFB-B8EA-8CAC7848DE40@finestweddingsites.com>
In-Reply-To: <44599D59-8386-4AFB-B8EA-8CAC7848DE40@finestweddingsites.com>
From: Clint Bullock <clint@seoteric.com>
Date: Wed, 29 Jun 2022 17:09:51 -0400
Message-ID: <CAM=ijpWiOb8MRibGEnCS0LBP06zZkqz1_VHZ1T8-0unyLY2ZYA@mail.gmail.com>
Subject: Re: Website Items and Questions - 5/27
To: Lisa Mungia <lisa@finestweddingsites.com>, Matt Brooks <matt@seoteric.com>
Cc: Diane Ursprunger <diane@finestweddingsites.com>, 
	"ashley@finestweddingsites.com" <Ashley@finestweddingsites.com>
Content-Type: multipart/related; boundary="00000000000083742a05e29c932e"

--00000000000083742a05e29c932e
Content-Type: multipart/alternative; boundary="00000000000083742a05e29c932d"

--00000000000083742a05e29c932d
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

On Fri, May 27, 2022 at 5:30 PM Lisa Mungia <lisa@finestweddingsites.com>
wrote:

> *Admin Reports-*
>
>    - Some of the Requested URLs have =E2=80=9Cleads/create_single=E2=80=
=9D in the url
>    path.  Where are these leads coming from?  Why different than other le=
ads?
>    Where trying to figure out how/where the leads are coming from?
>
>
>
>    - Why/how come Google is sometimes in the Referring Domain v
>    Referrer?  What path did a person take to have Google appear in Referr=
ing
>    Domain?
>    Can you refresh me on these tracking columns? The top 2 leads are me.
>
>
Hey Lisa,

For the first item, that "leads/create_single" path was being set as the
"Request Url" in the report most likely when the user was submitting the
form multiple times due to input errors (that is, missing or incorrect form
data). That's the only way that I could reproduce the issue. The form is
being submitted (via an HTTP POST request) to the "leads/create_single"
route on the server with the "Request Url" info in it; however, if the form
was not submitted successfully, it would come back to the same page, but
the "Request Url" would now be set the route that it just came from,
"leads/create_single". You would never see this if the form was submitted
successfully on the first try. Also, you can't get to that route directly
in the web browser since it only allows POSTing form data.

As a fix, the "Request Url" is now stored in a cookie and will not change
with multiple form submissions. Technically speaking, if a request is a
HTTP POST (form submission) it will not change. It only changes on HTTP GET
requests. This change has been applied across the site, so it should fix
this for any form submissions. The "Request Url" should now always be the
page that the person was on when the lead was completed.

Here's some documentation for items 1 and 2:

Request URL:
"This is the page the person was on when the lead was completed." - Lisa

Referrer:
This is usually the last page that the person was on before arriving at the
current page. In this case, if the user is submitting the lead form, this
will usually contain the previous page that led to the page with the lead
form.

It's more complicated than that, though:

The referrer information is pulled from the HTTP Referer (sic) header on
the request, and it's pulled from the user's browser. This is an optional
header and its presence on the request is subject to browser security
settings and user preferences. That is, it's not guaranteed to be
available, and it's possible for the end user to set this to anything. That
is, this field is not guaranteed to be useful in your reporting.

Reference:
https://en.m.wikipedia.org/wiki/HTTP_referer

Referring Domain:
When someone visits your website, the onsite analytics software creates a
visit with lots of useful information. One piece is the "referring domain"
which is the domain from the referrer. This is created once when the user
first arrives at the site. Again, the referrer information coming from the
user's browser is not guaranteed to be correct or useful.

Examples:

1. The user has never been to the site. The user finds the site in
   Google. The user clicks on a link to the site from the Google search
   results, the Visit is created and stored in the database, and the Referr=
ing
   Domain value would "www.google.com"
   2. The user has never been to the site. The user opens the browser,
   types in your site, and loads it directly. The Visit is created, but the
   Referring Domain is blank since no link to your site has been clicked.

Thanks,
Clint

--00000000000083742a05e29c932d
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><div dir=3D"ltr"><br></div><div class=3D"gmail_quote"><div=
 dir=3D"ltr" class=3D"gmail_attr">On Fri, May 27, 2022 at 5:30 PM Lisa Mung=
ia &lt;<a href=3D"mailto:lisa@finestweddingsites.com">lisa@finestweddingsit=
es.com</a>&gt; wrote:</div><blockquote class=3D"gmail_quote" style=3D"margi=
n:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex=
"><div lang=3D"EN-US" style=3D"overflow-wrap: break-word;"><p class=3D"MsoN=
ormal"><u></u></p><p class=3D"MsoNormal"><u></u><img width=3D"32" height=3D=
"32" style=3D"width: 0.3333in; height: 0.3333in;" src=3D"cid:181b1403fb9692=
e333"><u></u><u></u><u></u></p><p class=3D"MsoNormal"><b>Admin Reports-</b>=
<u></u><u></u></p><ul type=3D"disc"><li class=3D"MsoNormal" style=3D"margin=
-left:0.25in"><span style=3D"color:rgb(64,64,64)">Some of the Requested URL=
s have =E2=80=9Cleads/create_single=E2=80=9D in the url path.=C2=A0 Where a=
re these leads coming from?=C2=A0 Why different than other leads?=C2=A0 Whe=
re trying to figure out how/where the leads are coming from?<br></span>=C2=
=A0</li></ul><p class=3D"MsoNormal"><u></u></p><ul style=3D"margin-top:0in"=
 type=3D"disc"><li style=3D"margin-left:0.25in"><span style=3D"color:black"=
>Why/how come Google is sometimes in the Referring Domain v Referrer?=C2=A0=
 What path did a person take to have Google appear in Referring Domain?<br>=
</span><span style=3D"color:rgb(64,64,64)">Can you refresh me on these trac=
king columns?=C2=A0The top 2 leads are me.</span></li></ul></div></blockquo=
te><p dir=3D"auto" style=3D"box-sizing:border-box;margin-bottom:16px;color:=
rgb(36,41,47);font-family:-apple-system,BlinkMacSystemFont,&quot;Segoe UI&q=
uot;,Helvetica,Arial,sans-serif,&quot;Apple Color Emoji&quot;,&quot;Segoe U=
I Emoji&quot;;font-size:14px;margin-top:0px"><span style=3D"box-sizing:bord=
er-box;font-weight:600"><br></span></p><p style=3D"box-sizing:border-box;ma=
rgin-bottom:16px;color:rgb(36,41,47);font-family:-apple-system,BlinkMacSyst=
emFont,&quot;Segoe UI&quot;,Helvetica,Arial,sans-serif,&quot;Apple Color Em=
oji&quot;,&quot;Segoe UI Emoji&quot;;font-size:14px;margin-top:0px"><span s=
tyle=3D"box-sizing:border-box">Hey Lisa,</span></p><p style=3D"box-sizing:b=
order-box;margin-bottom:16px;color:rgb(36,41,47);font-family:-apple-system,=
BlinkMacSystemFont,&quot;Segoe UI&quot;,Helvetica,Arial,sans-serif,&quot;Ap=
ple Color Emoji&quot;,&quot;Segoe UI Emoji&quot;;font-size:14px;margin-top:=
0px"><span style=3D"box-sizing:border-box">For the first item, that &quot;l=
eads/create_single&quot; path was being set as the &quot;Request Url&quot; =
in the report most likely when the user was submitting the form multiple ti=
mes due to input errors (that is, missing or incorrect form data). That&#39=
;s the only way that I could reproduce the issue. The form is being submitt=
ed (via an HTTP POST request) to the=C2=A0</span>&quot;leads/create_single&=
quot; route on the server with the &quot;Request Url&quot; info in it; howe=
ver, if the form was not submitted successfully, it would come back to the =
same page, but the &quot;Request Url&quot; would now be set the route that =
it just came from, &quot;leads/create_single&quot;. You would never see thi=
s if the form was submitted successfully on the first try. Also, you can&#3=
9;t get to that route directly in the web browser since it only allows POST=
ing form data.</p><p style=3D"box-sizing:border-box;margin-bottom:16px;colo=
r:rgb(36,41,47);font-family:-apple-system,BlinkMacSystemFont,&quot;Segoe UI=
&quot;,Helvetica,Arial,sans-serif,&quot;Apple Color Emoji&quot;,&quot;Segoe=
 UI Emoji&quot;;font-size:14px;margin-top:0px">As a fix, the &quot;Request =
Url&quot; is now stored in a cookie and will not change with multiple form =
submissions. Technically speaking, if a request is a HTTP POST (form submis=
sion) it will not change. It only changes on HTTP GET requests. This change=
 has been applied across the site, so it should fix this for any form submi=
ssions. The &quot;Request Url&quot; should now always be the page that the =
person was on when the lead was completed.</p><p style=3D"box-sizing:border=
-box;margin-bottom:16px;color:rgb(36,41,47);font-family:-apple-system,Blink=
MacSystemFont,&quot;Segoe UI&quot;,Helvetica,Arial,sans-serif,&quot;Apple C=
olor Emoji&quot;,&quot;Segoe UI Emoji&quot;;font-size:14px;margin-top:0px">=
<br></p><p style=3D"box-sizing:border-box;margin-bottom:16px;color:rgb(36,4=
1,47);font-family:-apple-system,BlinkMacSystemFont,&quot;Segoe UI&quot;,Hel=
vetica,Arial,sans-serif,&quot;Apple Color Emoji&quot;,&quot;Segoe UI Emoji&=
quot;;font-size:14px;margin-top:0px">Here&#39;s some documentation for item=
s 1 and 2:</p><p dir=3D"auto" style=3D"box-sizing:border-box;margin-bottom:=
16px;color:rgb(36,41,47);font-family:-apple-system,BlinkMacSystemFont,&quot=
;Segoe UI&quot;,Helvetica,Arial,sans-serif,&quot;Apple Color Emoji&quot;,&q=
uot;Segoe UI Emoji&quot;;font-size:14px;margin-top:0px"><span style=3D"box-=
sizing:border-box;font-weight:600">Request URL:</span><br style=3D"box-sizi=
ng:border-box">&quot;This is the page the person was on when the lead was c=
ompleted.&quot; - Lisa</p><p dir=3D"auto" style=3D"box-sizing:border-box;ma=
rgin-top:0px;margin-bottom:16px;color:rgb(36,41,47);font-family:-apple-syst=
em,BlinkMacSystemFont,&quot;Segoe UI&quot;,Helvetica,Arial,sans-serif,&quot=
;Apple Color Emoji&quot;,&quot;Segoe UI Emoji&quot;;font-size:14px"><span s=
tyle=3D"box-sizing:border-box;font-weight:600">Referrer:</span><br style=3D=
"box-sizing:border-box">This is usually the last page that the person was o=
n before arriving at the current page. In this case, if the user is submitt=
ing the lead form, this will usually contain the previous page that led to =
the page with the lead form.</p><p dir=3D"auto" style=3D"box-sizing:border-=
box;margin-top:0px;margin-bottom:16px;color:rgb(36,41,47);font-family:-appl=
e-system,BlinkMacSystemFont,&quot;Segoe UI&quot;,Helvetica,Arial,sans-serif=
,&quot;Apple Color Emoji&quot;,&quot;Segoe UI Emoji&quot;;font-size:14px">I=
t&#39;s more complicated than that, though:</p><p dir=3D"auto" style=3D"box=
-sizing:border-box;margin-top:0px;margin-bottom:16px;color:rgb(36,41,47);fo=
nt-family:-apple-system,BlinkMacSystemFont,&quot;Segoe UI&quot;,Helvetica,A=
rial,sans-serif,&quot;Apple Color Emoji&quot;,&quot;Segoe UI Emoji&quot;;fo=
nt-size:14px">The referrer information is pulled from the HTTP Referer (sic=
) header on the request, and it&#39;s pulled from the user&#39;s browser. T=
his is an optional header and its presence on the request is subject to bro=
wser security settings and user preferences. That is, it&#39;s not guarante=
ed to be available, and it&#39;s possible for the end user to set this to a=
nything. That is, this field is not guaranteed to be useful in your reporti=
ng.</p><p dir=3D"auto" style=3D"box-sizing:border-box;margin-top:0px;margin=
-bottom:16px;color:rgb(36,41,47);font-family:-apple-system,BlinkMacSystemFo=
nt,&quot;Segoe UI&quot;,Helvetica,Arial,sans-serif,&quot;Apple Color Emoji&=
quot;,&quot;Segoe UI Emoji&quot;;font-size:14px">Reference:<br style=3D"box=
-sizing:border-box"><a href=3D"https://en.m.wikipedia.org/wiki/HTTP_referer=
" rel=3D"nofollow" style=3D"box-sizing:border-box;background-color:transpar=
ent;text-decoration-line:none">https://en.m.wikipedia.org/wiki/HTTP_referer=
</a></p><p dir=3D"auto" style=3D"box-sizing:border-box;margin-top:0px;margi=
n-bottom:16px;color:rgb(36,41,47);font-family:-apple-system,BlinkMacSystemF=
ont,&quot;Segoe UI&quot;,Helvetica,Arial,sans-serif,&quot;Apple Color Emoji=
&quot;,&quot;Segoe UI Emoji&quot;;font-size:14px"><span style=3D"box-sizing=
:border-box;font-weight:600">Referring Domain:</span><br style=3D"box-sizin=
g:border-box">When someone visits your website, the onsite analytics softwa=
re creates a visit with lots of useful information. One piece is the &quot;=
referring domain&quot; which is the domain from the referrer. This is creat=
ed once when the user first arrives at the site. Again, the referrer inform=
ation coming from the user&#39;s browser is not guaranteed to be correct or=
 useful.</p><p dir=3D"auto" style=3D"box-sizing:border-box;margin-top:0px;m=
argin-bottom:16px;color:rgb(36,41,47);font-family:-apple-system,BlinkMacSys=
temFont,&quot;Segoe UI&quot;,Helvetica,Arial,sans-serif,&quot;Apple Color E=
moji&quot;,&quot;Segoe UI Emoji&quot;;font-size:14px">Examples:</p><ol dir=
=3D"auto" style=3D"box-sizing:border-box;padding-left:2em;margin-top:0px;co=
lor:rgb(36,41,47);font-family:-apple-system,BlinkMacSystemFont,&quot;Segoe =
UI&quot;,Helvetica,Arial,sans-serif,&quot;Apple Color Emoji&quot;,&quot;Seg=
oe UI Emoji&quot;;font-size:14px;margin-bottom:0px"><li style=3D"box-sizing=
:border-box;margin-left:0px">The user has never been to the site. The user =
finds the site in Google. The user clicks on a link to the site from the Go=
ogle search results, the Visit is created and stored in the database, and t=
he Referring Domain value would &quot;<a href=3D"http://www.google.com">www=
.google.com</a>&quot;</li><li style=3D"box-sizing:border-box;margin-top:0.2=
5em;margin-left:0px">The user has never been to the site. The user opens th=
e browser, types in your site, and loads it directly. The Visit is created,=
 but the Referring Domain is blank since no link to your site has been clic=
ked.</li></ol><div>=C2=A0</div><div>Thanks,</div><div>Clint</div></div></di=
v>

--00000000000083742a05e29c932d--
--00000000000083742a05e29c932e
Content-Type: image/png; name="image003.png"
Content-Disposition: inline; filename="image003.png"
Content-Transfer-Encoding: base64
Content-ID: <181b1403fb9692e333>
X-Attachment-Id: 181b1403fb9692e333

iVBORw0KGgoAAAANSUhEUgAAACAAAAAgCAYAAABzenr0AAAAAXNSR0IArs4c6QAAAGxlWElmTU0A
KgAAAAgABAEaAAUAAAABAAAAPgEbAAUAAAABAAAARgEoAAMAAAABAAIAAIdpAAQAAAABAAAATgAA
AAAAAACQAAAAAQAAAJAAAAABAAKgAgAEAAAAAQAAACCgAwAEAAAAAQAAACAAAAAAxqyL9QAAAAlw
SFlzAAAWJQAAFiUBSVIk8AAAAChJREFUWAnt0IEAAAAAw6D5Ux/khVBhwIABAwYMGDBgwIABAwYM
vA8MECAAAc4qtccAAAAASUVORK5CYII=
--00000000000083742a05e29c932e--