KR20020019495A - The procedure for cutting off duplicated E-mail addresses on sending messages for marketing and infomation using E-mail - Google Patents

Abstract

The present invention relates to a method of proactively preventing duplicate sending to the same email address in online marketing and information transmission using email, and simultaneously or mutually at each computer in a process or network in a single computer. Even if it is sent on different date, it can be sent only once to the duplicate email address. This can be done by separately operating the database for redundancy check. Compared to the database for redundancy check before e-mail transmission, it cancels the transmission if it is already sent and records it before it is recorded.

This eliminates the user's efforts due to redundant data processing and can be effective for more effective and reliable email marketing and information delivery.

Description

The procedure for cutting off duplicated E-mail addresses on sending messages for marketing and infomation using E-mail}

The present invention is a technology of the field of e-mail transmission (DB marketing and Email marketing) linked to a database, and in the past, an email address which is not duplicated in advance by cleaning or filtering the original database itself in order to prevent sending to a duplicate email address. Sent only to. This approach, despite much effort, can prevent a single duplication, but it cannot fundamentally prevent duplicates from different dates and from different computers.

The ultimate object of the present invention is to maximize the effect of online marketing and information transmission by blocking the same information is repeatedly transmitted to the same person through e-mail. There are many situations in which duplicate transmissions exist, so it is a basic task that duplicate transmissions should be blocked in all expected situations. It can be divided into detailed tasks as follows.

1. There should not be duplicate e-mails sent simultaneously by multiple processes on the same computer.

2. There should not be duplicate e-mails sent on different dates on the same computer.

3. There should not be duplicate e-mails sent from multiple computers at the same time.

4. There should be no duplicate sending of e-mails sent by different computers on different dates.

5. The user should be able to specify an arbitrary duration for blocking duplicate transmissions.

6. Users should be able to specify whether to use duplicate transmission blocking. In other words, the user should be able to arbitrarily set the data to prevent duplicate transmission and the data that does not.

In the present invention, in order to block duplicate transmissions in all of the above circumstances, the present invention is characterized by operating a separate database by creating a new database for checking duplicates or by designating a new database . In other words, it prevents duplicate transmissions by recording the email addresses of all messages that are sent and other needs in a specified database, and by checking the email addresses and other needs of messages that are sent later in the specified database before sending. will be.

FIG. 1 schematically illustrates the simplest form of redundant transmission blocking method to help understand the present invention. (Note: Drawings in this specification are not treated as identifiers due to SGML conversion errors.)

Figure 1. Schematic diagram for blocking redundant transmission

The email sending computer is configured to compare the email address to be sent now and other needs in a predefined or newly created database for duplicate checking, as shown in FIG. 1, before all emails are actually sent. If there is no previous transmission record after the comparison, it is sent to the final recipient after the recording. If there is a record, the transmission is canceled. This is a different concept from the traditional removal of redundant data from data files before they are sent. You can send it unknowingly, whether or not you check for duplicates.

The creation of a database for redundancy checks is described later in the specification by way of examples included in the solution.

As a concrete comparison method, the SQL statement as shown in the following example can be used. The following statement is the simplest form of duplicate comparison.

Comparative syntax example 1)

Select [Email] From [Duplicate Table] Where [Email] = 'aaaa@company.com'

In the above syntax, "aaaa@company.com" refers to the email address to be sent, which is variable.

If there is a record returned as a result of executing the above statement, the "aaaa@company.com" email address is not determined to be a duplicate email address previously sent and is not sent.

In addition, the redundancy check database is not temporary but semi-permanent, so the redundancy of email addresses sent on different dates can be checked without any extra work.

For the date comparison, the comparison syntax with the date condition added in Example 1) can be written as in the example below.

Comparative syntax example 2)

Select [Email] From [Duplicate Table] Where [Email] = 'aaaa@company.com' And

(Now-[Send_Date] <= custom date value)

For example, a custom date value of 15 will only check for redundancy within 15 days, and email addresses sent before the 15th will be excluded from the duplicate evaluation. That is, if the "aaaa@company.com" email address has not been sent within 15 days, it is sent again.

FIG. 2 is an extension of the single configuration of FIG. 1 to a network. In other words, put the database for redundancy checking in a shareable location on the network (for example, in a shared folder or an RDBMS DB such as SQL Server) and access it from multiple computers simultaneously.

Figure 2. System Conceptual Diagram for Blocking Multiple Redundant Transmissions

This prevents repetitive transmissions to duplicate email addresses even in group work environments.

By specifying the same database for duplicate checking on all email sending computers shown in FIG. 2, duplicate sending by group can be prevented in advance.

Among SK Soft's products, the method of the present invention is specifically included in the Email marketing and customer management solution, which is a good example applied to the real industry.

3 shows an example of a detailed configuration of a screen for setting a database for duplicate checking in an email marketing and customer management solution.

Figure 3. Example screen configuration for setting up a database for redundancy checking

In FIG. 3, if a database for duplicate checking has already been created, it can be designated by clicking the [Browse] button. If it is not already created, it can be created by pressing the [New] button.

The table structure of the redundancy check database shown in FIG. 3 is as follows.

Table Structure (Table Name: Email)

Field name Data format size Usage

Serial Number Serial Number 4 Sequence Layout

Source Table Name Text 255 Trace Source Data File

Recipient Text 255 Recipient Display

Email Text 255 For Email Address Duplicate Checking

Ship Date Date / Time 8 Purpose of Duplicate Period

Send Time Date / Time 8 Use Hourly Statistics

From text 255 Statistics by contact

From Email Text 255 Using Statistics

Title Text 255 Using Statistics

Computer Text 255 Using Statistics

Note Text 255 Notes Note

In the structure of the entire table above, the [Email] field and the [Send date] field are used to evaluate redundancy, and the email address and the date sent are recorded respectively.

In addition, in FIG. 3, a user can be arbitrarily designated whether or not to use the database setting for duplicate checking, and a user can be arbitrarily designated for a specific period of time.

The program (Email marketing and customer management solution) will be blocked or transmitted based on the flow chart shown in FIG. At this point, the email address is usually taken from a data file (usually a database), so it will repeat until the email is sent.

Figure 4. Redundant Block Diagram Included in Email Marketing and Customer Care Solutions

In FIG. 4, a function including the following SQL statement was used for the redundancy evaluation.

Public Function IsSent (ByVal RcpAddress As String) As Boolean

On Error Resume Next

Dim sql As String, rs As Recordset

If UseDoubleExpire Then 'If user-specified date duplication is set

sql = "Select [Email] From [Email] Where ([Email] = '" & RcpAddress

& "') And (Date ()-[Send Date] <" & ExpireDate & ")"

Else 'If you don't want to send only duplicate addresses

sql = "Select [Email] From [Email] Where [Email] = '" & RcpAddress

& "'"

End if

Set rs = DoubleDB.OpenRecordset (sql, dbOpenDynaset)

If rs.RecordCount> 0 Then

IsSent = True 'The address has already been sent.

Else

IsSent = False 'The address has not yet been sent.

End if

rs.Close

Set rs = Nothing

End function

By doing the above, it is possible to prohibit the transmission of duplicate email addresses within a certain period of time specified by the user.

Using a separate database for redundancy evaluation without editing the original database to prevent duplicate transmissions can save a lot of work and time for the practitioner.

Recipients can improve the reliability of the company by not receiving the same information or information from the same company more than once in a short period of time. By deciding on that, the deduplication-related task is completely gone.

Therefore, ultimately, the company will not only improve its image, but will also be able to devote surplus time to other productive tasks, thereby contributing to productivity.

Claims (1)

In order to prevent duplicate sending to the same email address in online marketing and information transmission using email, Creating a new database for redundancy checking or designating an already created database as a redundancy check database. Compared with the email address data and the transmission date and the email address to be transmitted, which are stored in the redundancy check database, if it is determined that there is no duplication, the transmission step is recorded after the transmission information is recorded and if it is determined that the duplicate is not duplicated To Prevent Duplicate Sending of Email