[FX.php List] [OFF] How to create a web bug

Jonathan Schwartz jschwartz at exit445.com
Thu Dec 13 21:45:27 MST 2007 

DC, Steve, Alex, Bob,

Per my earlier email, I quickly gave up on the idea after it was 
confirmed that this is not an above board activity. My server is 
squeaky clean and I intend to keep it that way.

Thanks for the feedback.

Jonathan

At 10:52 PM -0500 12/13/07, DC wrote:
>if you decide to test the idea... spam filters be damned (or just 
>not an issue) you can make a script that outputs an image that's 1 
>pixel by 1 pixel and serve it via php's image and header commands.
>
><img src="http://example.com/we_are_tracking_you.php?SSN=123-45-6789">
>
>obviously, your tracking code would go in there somewhere - 
>different for each person.
>
>still, you won't see any image 'loads' for people who read mail with 
>image loading off (most start with it off, but i noticed that 
>leopard's mail.app switched mine to load images in mail - bad 
>kitty!). also, the image will load multiple times (one for each time 
>the person "loads" it into email). so, if a person "reads" your 
>email then lets it sit there while they delete other messages, 
>you'll see a stream of "reads" one after the other. it's actually 
>one indication that they are saving your message.
>
>also, you'll get tagged by some email readers as a web bug and it 
>will increase you spam score.
>
>the best way to get people to reply is to promise money. failing 
>that, hold their internet service hostage. failing that, offer some 
>other incentive.
>
>failing that, send paper - registered mail.
>
>dan
>
>
>On Dec 13, 2007, at 10:03 AM, Jonathan Schwartz wrote:
>
>>  Hi Folks,
>>
>>  I'm about to launch a project that starts with an outbound email 
>>requesting registrants to update their information.  The email 
>>contains a personalized link that automatically logs the use in to 
>>the web site.
>>
>>  Experience shows, however, that many folks don't bother to respond 
>>because their information has not changed.  In this case, we get no 
>>response...and don't know whether the person has received the email 
>>or not.
>>
>>  Is there an easy way to incorporate a "web bug" that essentially 
>>contacts a web server (fx.php?) to confirm that the email has been 
>>viewed?  I know that this applies only to html mail...but it's 
>>better than nothing.
>>
>>  I'm also aware that there might be downsides to using a web bug.
>>
>>  Anyone have experience in this area?
>>
>>  Thx
>>
>>  Jonathan
>>
>>
>>
>>
>>  --Jonathan Schwartz
>>  Exit 445 Group
>>  jonathan at exit445.com
>>  http://www.exit445.com
>>  415-381-1852
>>  _______________________________________________
>>  FX.php_List mailing list
>>  FX.php_List at mail.iviking.org
>>  http://www.iviking.org/mailman/listinfo/fx.php_list
>
>
>
>
>Steve Winter had written:
>>Hi Jonathan,
>>
>>You could try asking for a read receipt... in many mail clients when you
>>open an email which has requested a receipt a dialog automatically pops up,
>>which you can click send on... because it's 'In their face' more people
>>might be inclined to hit 'Send'...
>>
>>Then if the reply-to address for the message was a mailbox specifically for
>>that purpose, you could have FMP gather that mail, match the email address
>>to the specific user, and create a new record saying 'they read the mail'...
>>
>>(Have been there, have done very similar, though not with read receipts so
>>don't know what your specific take up would be...)
>>
>>Cheers
>>Steve
>>
>>-----Original Message-----
>>From: fx.php_list-bounces at mail.iviking.org
>>[mailto:fx.php_list-bounces at mail.iviking.org] On Behalf Of Jonathan Schwartz
>>Sent: 13 December 2007 16:22
>>To: alex at gandrpublishing.com; FX.php Discussion List
>>Subject: Re: [FX.php List] [OFF] How to create a web bug
>>
>>Thanks Alex and Bob,
>>
>>You've confirmed my suspicions about web bugs.
>>
>>I can easily handle responses if they click the link.  However, we 
>>just have to guess that non-response equates to either approval, 
>>indifference or non-receipt of email.
>>
>>Their loss. ;-)
>>
>>J
>>
>>
>>At 10:02 AM -0600 12/13/07, Alex Gates wrote:
>>>A agree with Bob -
>>>I think the headache with spam blockers will outweigh the possible
>>benefits.
>>>Perhaps you could add a link to change information and also 
>>>another link that users could click on to indicate their 
>>>information is still current.
>>>
>>>
>>>Bob Patin wrote:
>>>>I'd avoid that... that's how a lot of spammers work, and I'm 
>>>>wondering whether your emails might get flagged because they're 
>>>>sending something back.
>>>>
>>>>I think that the easiest method would be to put a confirm link in 
>>>>the email itself.
>>>>
>>>>http://domain.com/confirm.php&r=123
>>>>
>>>>You could put the id# in the email by generating emails from 
>>>>FileMaker, and then when they click the link it'd write to the 
>>>>database and perhaps create a log file showing who read the 
>>>>email, and when.
>>>>
>>>>Just an idea,
>>>>
>>>>Bob Patin
>>>>Longterm Solutions
>>>>bob at longtermsolutions.com
>>>>615-333-6858
>>>>http://www.longtermsolutions.com
>>>>Member of FileMaker Business Alliance and FileMaker TechNet
>>>>
>>>>   CONTACT US VIA INSTANT MESSAGING:
>>>>      AIM or iChat: longterm1954
>>>>      Yahoo: longterm_solutions
>>>>      MSN: tech at longtermsolutions.com
>>>>      ICQ: 159333060
>>>>
>>>>--------------------------
>>>>Contact us for FileMaker hosting and programming for all versions 
>>>>of FileMaker
>>>>PHP * CDML * Full email services * Free DNS hosting * Colocation *
>>Consulting
>>>>On Dec 13, 2007, at 9:03 AM, Jonathan Schwartz wrote:
>>>>
>>>>>Hi Folks,
>>>>>
>>>>>I'm about to launch a project that starts with an outbound email 
>>>>>requesting registrants to update their information.  The email 
>>>>>contains a personalized link that automatically logs the use in 
>>>>>to the web site.
>>>>>
>>>>>Experience shows, however, that many folks don't bother to 
>>>>>respond because their information has not changed.  In this 
>>>>>case, we get no response...and don't know whether the person has 
>>>>>received the email or not.
>>>>>
>>>>>Is there an easy way to incorporate a "web bug" that essentially 
>>>>>contacts a web server (fx.php?) to confirm that the email has 
>>>>>been viewed?  I know that this applies only to html mail...but 
>>>>>it's better than nothing.
>>>>>
>>>>>I'm also aware that there might be downsides to using a web bug.
>>>>>
>>>>>Anyone have experience in this area?
>>>>>
>>>>>Thx
>>>>>
>>>>>Jonathan
>>>>>
>>>>>
>>>>>
>>>>>
>>>>>--
>>>>>Jonathan Schwartz
>>>>>Exit 445 Group
>>>>>jonathan at exit445.com
>>>>>http://www.exit445.com
>>>>>415-381-1852
>>>>>_______________________________________________
>>>>>FX.php_List mailing list
>>>>>FX.php_List at mail.iviking.org
>>>>>http://www.iviking.org/mailman/listinfo/fx.php_list
>>>>_______________________________________________
>>>>FX.php_List mailing list
>>>>FX.php_List at mail.iviking.org
>>>>http://www.iviking.org/mailman/listinfo/fx.php_list
>>>>
>>>_______________________________________________
>>>FX.php_List mailing list
>>>FX.php_List at mail.iviking.org
>>>http://www.iviking.org/mailman/listinfo/fx.php_list
>>
>>
>_______________________________________________
>FX.php_List mailing list
>FX.php_List at mail.iviking.org
>http://www.iviking.org/mailman/listinfo/fx.php_list


-- 
Jonathan Schwartz
Exit 445 Group
jonathan at exit445.com
http://www.exit445.com
415-381-1852

More information about the FX.php_List mailing list