관리-도구

편집 파일: .1656627206.M252281P14087.fin.finestweddingsites.com,S=24714,W=25296:2,Saf.142364

Envelope-to: diane@finestweddingsites.com,
 Ashley@finestweddingsites.com
Delivery-date: Thu, 30 Jun 2022 17:13:26 -0500
User-Agent: Microsoft-MacOutlook/16.61.22050700
Date: Thu, 30 Jun 2022 15:13:24 -0700
Subject: Re: Website Items and Questions - 5/27
From: Lisa Mungia <lisa@finestweddingsites.com>
To: Diane Ursprunger <diane@finestweddingsites.com>
CC: "ashley@finestweddingsites.com" <Ashley@finestweddingsites.com>
Message-ID: <EC54CDAA-947A-42ED-886D-09C3E2289793@finestweddingsites.com>
Thread-Topic: Website Items and Questions - 5/27
References: <44599D59-8386-4AFB-B8EA-8CAC7848DE40@finestweddingsites.com>
 <CAM=ijpWiOb8MRibGEnCS0LBP06zZkqz1_VHZ1T8-0unyLY2ZYA@mail.gmail.com>
 <FEC0FE7C-E707-48A9-922B-FF781D45A747@finestweddingsites.com>
In-Reply-To: <FEC0FE7C-E707-48A9-922B-FF781D45A747@finestweddingsites.com>
Mime-version: 1.0
Content-type: multipart/alternative;
	boundary="B_3739446805_207805338"

> This message is in MIME format. Since your mail reader does not understand
this format, some or all of this message may not be legible.

--B_3739446805_207805338
Content-type: text/plain;
	charset="UTF-8"
Content-transfer-encoding: quoted-printable

I need more time to review all Clint=E2=80=99s stuffs!=C2=A0 But his email from last =
night and today are on my radar! =F0=9F=98=8A=20

=20

From: Diane Ursprunger <diane@finestweddingsites.com>
Date: Thursday, June 30, 2022 at 1:59 PM
To: "lisa@finestweddingsites.com" <lisa@finestweddingsites.com>
Cc: "ashley@finestweddingsites.com" <Ashley@finestweddingsites.com>
Subject: Re: Website Items and Questions - 5/27

=20

Have you had time to review Clints comments on the Admin Reports edit below=
 regarding our questions about Requested URL=E2=80=99s and Referring domain ?

=20

I=E2=80=99m kinda lost=E2=80=A6..not fully following this. Do you feel like you underst=
and and our questions got answered adequately?

=20

Diane Ursprunger | Owner=20
Arizona's Finest Wedding Sites & Services=20
480.970.1948 | finestweddingsites.com=20
diane@finestweddingsites.com

=20

On Jun 29, 2022, at 5:09 PM, Clint Bullock <clint@seoteric.com> wrote:

=20

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

<image003.png>

Admin Reports-

=C2=B7         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 lea=
ds?  Where trying to figure out how/where the leads are coming from?
=20

=C2=B7         Why/how come Google is sometimes in the Referring Domain v Refer=
rer?  What path did a person take to have Google appear in Referring 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 "R=
equest 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 su=
bmitted (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 subm=
itted successfully, it would come back to the same page, but the "Request Ur=
l" 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 firs=
t try. Also, you can't get to that route directly in the web browser since i=
t only allows POSTing form data.

As a fix, the "Request Url" is now stored in a cookie and will not change w=
ith multiple form submissions. Technically speaking, if a request is a HTTP =
POST (form submission) it will not change. It only changes on HTTP GET reque=
sts. 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.

=20

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 w=
ill usually contain the previous page that led to the page with the lead for=
m.

It's more complicated than that, though:

The referrer information is pulled from the HTTP Referer (sic) header on th=
e request, and it's pulled from the user's browser. This is an optional head=
er and its presence on the request is subject to browser security settings a=
nd 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 no=
t 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 v=
isit with lots of useful information. One piece is the "referring domain" wh=
ich is the domain from the referrer. This is created once when the user firs=
t arrives at the site. Again, the referrer information coming from the user'=
s browser is not guaranteed to be correct or useful.

Examples:
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 Referring Domain value would=
 "www.google.com"
The user has never been to the site. The user opens the browser, types in y=
our site, and loads it directly. The Visit is created, but the Referring Dom=
ain is blank since no link to your site has been clicked.
=20

Thanks,

Clint

=20

--B_3739446805_207805338
Content-type: text/html;
	charset="UTF-8"
Content-transfer-encoding: quoted-printable

<html xmlns:o=3D"urn:schemas-microsoft-com:office:office" xmlns:w=3D"urn:schema=
s-microsoft-com:office:word" xmlns:m=3D"http://schemas.microsoft.com/office/20=
04/12/omml" xmlns=3D"http://www.w3.org/TR/REC-html40"><head><meta http-equiv=3DC=
ontent-Type content=3D"text/html; charset=3Dutf-8"><meta name=3DGenerator content=3D=
"Microsoft Word 15 (filtered medium)"><style></style></head><body lang=3DEN-US link=3Dblue vlink=3Dpurple style=3D'word-wrap:=
break-word;-webkit-nbsp-mode: space;line-break:after-white-space'><div class=
=3DWordSection1><p class=3DMsoNormal><span style=3D'font-family:"Calibri Light",sa=
ns-serif;color:#404040'>I need more time to review all Clint=E2=80=99s stuffs!=C2=A0 B=
ut his email from last night and today are on my radar! </span><span style=3D'=
font-family:"Apple Color Emoji";color:#404040'>&#128522;</span><span style=3D'=
font-family:"Calibri Light",sans-serif;color:#404040'> <o:p></o:p></span></p=
><p class=3DMsoNormal><span style=3D'font-family:"Calibri Light",sans-serif;colo=
r:#404040'><o:p>&nbsp;</o:p></span></p><div style=3D'border:none;border-top:so=
lid #B5C4DF 1.0pt;padding:3.0pt 0in 0in 0in'><p class=3DMsoNormal><b><span sty=
le=3D'font-size:12.0pt;color:black'>From: </span></b><span style=3D'font-size:12=
.0pt;color:black'>Diane Ursprunger &lt;diane@finestweddingsites.com&gt;<br><=
b>Date: </b>Thursday, June 30, 2022 at 1:59 PM<br><b>To: </b>&quot;lisa@fine=
stweddingsites.com&quot; &lt;lisa@finestweddingsites.com&gt;<br><b>Cc: </b>&=
quot;ashley@finestweddingsites.com&quot; &lt;Ashley@finestweddingsites.com&g=
t;<br><b>Subject: </b>Re: Website Items and Questions - 5/27<o:p></o:p></spa=
n></p></div><div><p class=3DMsoNormal><o:p>&nbsp;</o:p></p></div><p class=3DMsoN=
ormal>Have you had time to review Clints comments on the Admin Reports edit =
below regarding our questions about Requested URL=E2=80=99s and Referring domain ?=
<o:p></o:p></p><div><p class=3DMsoNormal><o:p>&nbsp;</o:p></p></div><div><p cl=
ass=3DMsoNormal>I=E2=80=99m kinda lost=E2=80=A6..not fully following this. Do you feel lik=
e you understand and our questions got answered adequately?<o:p></o:p></p></=
div><div><p class=3DMsoNormal><o:p>&nbsp;</o:p></p></div><div><p class=3DMsoNorm=
al><o:p>&nbsp;</o:p></p></div><div><p class=3DMsoNormal><o:p>&nbsp;</o:p></p><=
div><div><div><div><p class=3DMsoNormal><span style=3D'font-size:10.5pt;color:bl=
ack'>Diane Ursprunger | Owner&nbsp;<br>Arizona's Finest Wedding Sites &amp;&=
nbsp;Services&nbsp;<br>480.970.1948 |&nbsp;<a href=3D"http://finestweddingsite=
s.com">finestweddingsites.com</a>&nbsp;<br><a href=3D"mailto:diane@finestweddi=
ngsites.com">diane@finestweddingsites.com</a><o:p></o:p></span></p></div><di=
v><p class=3DMsoNormal><span style=3D'color:black'><o:p>&nbsp;</o:p></span></p><=
/div></div><p class=3DMsoNormal><span style=3D'color:black'><o:p>&nbsp;</o:p></s=
pan></p></div><p class=3DMsoNormal style=3D'margin-bottom:12.0pt'><o:p>&nbsp;</o=
:p></p></div><div><p class=3DMsoNormal><br><br><o:p></o:p></p><blockquote styl=
e=3D'margin-top:5.0pt;margin-bottom:5.0pt'><div><p class=3DMsoNormal>On Jun 29, =
2022, at 5:09 PM, Clint Bullock &lt;<a href=3D"mailto:clint@seoteric.com">clin=
t@seoteric.com</a>&gt; wrote:<o:p></o:p></p></div><p class=3DMsoNormal><o:p>&n=
bsp;</o:p></p><div><div><div><p class=3DMsoNormal><o:p>&nbsp;</o:p></p></div><=
div><div><p class=3DMsoNormal>On Fri, May 27, 2022 at 5:30 PM Lisa Mungia &lt;=
<a href=3D"mailto:lisa@finestweddingsites.com">lisa@finestweddingsites.com</a>=
&gt; wrote:<o:p></o:p></p></div><blockquote style=3D'border:none;border-left:s=
olid #CCCCCC 1.0pt;padding:0in 0in 0in 6.0pt;margin-left:4.8pt;margin-right:=
0in'><div><p class=3DMsoNormal style=3D'mso-margin-top-alt:auto;mso-margin-botto=
m-alt:auto'>&lt;image003.png&gt;<o:p></o:p></p><p class=3DMsoNormal style=3D'mso=
-margin-top-alt:auto;mso-margin-bottom-alt:auto'><b>Admin Reports-</b><o:p><=
/o:p></p><p class=3DMsoNormal style=3D'mso-margin-top-alt:auto;mso-margin-bottom=
-alt:auto;margin-left:.75in;text-indent:-.25in;mso-list:l2 level1 lfo1'><![i=
f !supportLists]><span style=3D'font-size:10.0pt;font-family:Symbol'><span sty=
le=3D'mso-list:Ignore'>=C2=B7<span style=3D'font:7.0pt "Times New Roman"'>&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; </span></span></span><![endif]><span =
style=3D'color:#404040'>Some of the Requested URLs have =E2=80=9Cleads/create_single=
=E2=80=9D in the url path.&nbsp; Where are these leads coming from?&nbsp; Why diff=
erent than other leads?&nbsp; Where trying to figure out how/where the leads=
 are coming from?<br></span>&nbsp;<o:p></o:p></p><p class=3DMsoNormal style=3D'm=
so-margin-top-alt:auto;mso-margin-bottom-alt:auto;margin-left:.75in;text-ind=
ent:-.25in;mso-list:l0 level1 lfo2'><![if !supportLists]><span style=3D'font-s=
ize:10.0pt;font-family:Symbol'><span style=3D'mso-list:Ignore'>=C2=B7<span style=3D'=
font:7.0pt "Times New Roman"'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p; </span></span></span><![endif]>Why/how come Google is sometimes in the Re=
ferring Domain v Referrer?&nbsp; What path did a person take to have Google =
appear in Referring Domain?<br><span style=3D'color:#404040'>Can you refresh m=
e on these tracking columns?&nbsp;The top 2 leads are me.</span><o:p></o:p><=
/p></div></blockquote><p class=3DMsoNormal style=3D'margin-bottom:12.0pt;box-siz=
ing:border-box'><b><span style=3D'font-size:10.5pt;font-family:-apple-system;c=
olor:#24292F'><br><br></span></b><span style=3D'font-size:10.5pt;font-family:-=
apple-system;color:#24292F'><o:p></o:p></span></p><p class=3DMsoNormal style=3D'=
margin-bottom:12.0pt;box-sizing:border-box'><span style=3D'font-size:10.5pt;fo=
nt-family:-apple-system;color:#24292F'>Hey Lisa,<o:p></o:p></span></p><p cla=
ss=3DMsoNormal style=3D'margin-bottom:12.0pt;box-sizing:border-box'><span style=3D=
'font-size:10.5pt;font-family:-apple-system;color:#24292F'>For the first ite=
m, that &quot;leads/create_single&quot; path was being set as the &quot;Requ=
est Url&quot; in the report most likely when the user was submitting the for=
m multiple times due to input errors (that is, missing or incorrect form dat=
a). That's the only way that I could reproduce the issue. The form is being =
submitted (via an HTTP POST request) to the&nbsp;&quot;leads/create_single&q=
uot; route on the server with the &quot;Request Url&quot; info in it; howeve=
r, if the form was not submitted successfully, it would come back to the sam=
e page, but the &quot;Request Url&quot; would now be set the route that it j=
ust came from, &quot;leads/create_single&quot;. 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 da=
ta.<o:p></o:p></span></p><p class=3DMsoNormal style=3D'margin-bottom:12.0pt;box-=
sizing:border-box'><span style=3D'font-size:10.5pt;font-family:-apple-system;c=
olor:#24292F'>As a fix, the &quot;Request Url&quot; is now stored in a cooki=
e 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 ch=
anges on HTTP GET requests. This change has been applied across the site, so=
 it should fix this for any form submissions. The &quot;Request Url&quot; sh=
ould now always be the page that the person was on when the lead was complet=
ed.<o:p></o:p></span></p><p class=3DMsoNormal style=3D'margin-bottom:12.0pt;box-=
sizing:border-box'><span style=3D'font-size:10.5pt;font-family:-apple-system;c=
olor:#24292F'><o:p>&nbsp;</o:p></span></p><p class=3DMsoNormal style=3D'margin-b=
ottom:12.0pt;box-sizing:border-box'><span style=3D'font-size:10.5pt;font-famil=
y:-apple-system;color:#24292F'>Here's some documentation for items 1 and 2:<=
o:p></o:p></span></p><p class=3DMsoNormal style=3D'margin-bottom:12.0pt;box-sizi=
ng:border-box'><b><span style=3D'font-size:10.5pt;font-family:-apple-system;co=
lor:#24292F'>Request URL:</span></b><span style=3D'font-size:10.5pt;font-famil=
y:-apple-system;color:#24292F'><br>&quot;This is the page the person was on =
when the lead was completed.&quot; - Lisa<o:p></o:p></span></p><p class=3DMsoN=
ormal style=3D'margin-bottom:12.0pt;box-sizing:border-box'><b><span style=3D'fon=
t-size:10.5pt;font-family:-apple-system;color:#24292F'>Referrer:</span></b><=
span style=3D'font-size:10.5pt;font-family:-apple-system;color:#24292F'><br>Th=
is is usually the last page that the person was on before arriving at the cu=
rrent 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.<=
o:p></o:p></span></p><p class=3DMsoNormal style=3D'margin-bottom:12.0pt;box-sizi=
ng:border-box'><span style=3D'font-size:10.5pt;font-family:-apple-system;color=
:#24292F'>It's more complicated than that, though:<o:p></o:p></span></p><p c=
lass=3DMsoNormal style=3D'margin-bottom:12.0pt;box-sizing:border-box'><span styl=
e=3D'font-size:10.5pt;font-family:-apple-system;color:#24292F'>The referrer in=
formation is pulled from the HTTP Referer (sic) header on the request, and i=
t's pulled from the user's browser. This is an optional header and its prese=
nce on the request is subject to browser security settings and user preferen=
ces. 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.<o:p></o:p></span></p><p class=3DMsoNormal style=3D'=
margin-bottom:12.0pt;box-sizing:border-box'><span style=3D'font-size:10.5pt;fo=
nt-family:-apple-system;color:#24292F'>Reference:<br><a href=3D"https://en.m.w=
ikipedia.org/wiki/HTTP_referer">https://en.m.wikipedia.org/wiki/HTTP_referer=
</a><o:p></o:p></span></p><p class=3DMsoNormal style=3D'margin-bottom:12.0pt;box=
-sizing:border-box'><b><span style=3D'font-size:10.5pt;font-family:-apple-syst=
em;color:#24292F'>Referring Domain:</span></b><span style=3D'font-size:10.5pt;=
font-family:-apple-system;color:#24292F'><br>When someone visits your websit=
e, the onsite analytics software creates a visit with lots of useful informa=
tion. One piece is the &quot;referring domain&quot; 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 guara=
nteed to be correct or useful.<o:p></o:p></span></p><p class=3DMsoNormal style=
=3D'margin-bottom:12.0pt;box-sizing:border-box'><span style=3D'font-size:10.5pt;=
font-family:-apple-system;color:#24292F'>Examples:<o:p></o:p></span></p><ol =
start=3D1 type=3D1><li class=3DMsoNormal style=3D'color:#24292F;mso-margin-top-alt:a=
uto;mso-margin-bottom-alt:auto;mso-list:l1 level1 lfo3;box-sizing:border-box=
'><span style=3D'font-size:10.5pt;font-family:-apple-system'>The user has neve=
r 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 st=
ored in the database, and the Referring Domain value would &quot;<a href=3D"ht=
tp://www.google.com/">www.google.com</a>&quot;<o:p></o:p></span></li><li cla=
ss=3DMsoNormal style=3D'color:#24292F;margin-top:3.0pt;mso-margin-bottom-alt:aut=
o;mso-list:l1 level1 lfo3;box-sizing:border-box'><span style=3D'font-size:10.5=
pt;font-family:-apple-system'>The user has never been to the site. The user =
opens the browser, types in your site, and loads it directly. The Visit is c=
reated, but the Referring Domain is blank since no link to your site has bee=
n clicked.<o:p></o:p></span></li></ol><div><p class=3DMsoNormal>&nbsp;<o:p></o=
:p></p></div><div><p class=3DMsoNormal>Thanks,<o:p></o:p></p></div><div><p cla=
ss=3DMsoNormal>Clint<o:p></o:p></p></div></div></div></div></blockquote></div>=
<p class=3DMsoNormal><o:p>&nbsp;</o:p></p></div></div></body></html>

--B_3739446805_207805338--