Identification of the recipient of the letter or nonsense?

Question

Email Marketing

Is there a program or way to identify each email sent?

Let's say he sent a letter to user "A", he opened it, read it and went to the signature on the site - in Metrica it was reflected in me - user "A" went to the site from the letter.
Further, the user "B" was also reflected too, but under a different value.

As a result, I will have the visibility and identification of each user on the site and through the letter, even if he opens this letter in half a year.

Or nonsense?

Answer 1

tools.ietf.org/html/rfc822 actually this is our everything, the unique header of the letter is described in 4.6.1. MESSAGE-ID / RESENT-MESSAGE-ID is what we need. In free translation:
This header should be a unique string generated by the server in its absence or by the client (Bingo!!!). Look further we see headings
4.6.2. IN-REPLY-TO
4.6.3. REFERENCES
Of course they are optional, but normal clients put them (Bingo!!!)
And here is an example

using (var client = new SmtpClient())
using(var message = new MailMessage("[email protected]",model.To,model.Subject,model.Body))
{
  int requestId = 1977;
  var messageid = string.Format("<{0}_{1}>", Guid.NewGuid().ToString("D"), requestId);
  message.Headers.Add("Message-ID", messageid);
                    client.Send(message);
}

You also need to make a link in the letter to go.
https://site.com/api/promote/45555-66666-888_1977
and process this transition on the server, then setting 301 status to redirect to the desired section

Answer 2

Marketing email services like MailChimp, SendInBlue and a bunch of others have long solved this business problem for their customers.
Each email is generated with unique link tags. All link clicks go through their counter system and are then redirected to the target location.
upd. for the love of cycling, you can, of course, write your own. The meaning is the same: to create each letter individually, prescribing a parameter that identifies the recipient in all links in this letter. for example

<!-- было -->
Смотрите <a href="https://example.com/catalog">наш каталог</a>

<!-- стало -->
Смотрите <a href="https://example.com/catalog?uuid=09076506-5f26-11eb-9b96-005056111e65">наш каталог</a>

plus add standard utm tags for general statistics of the same Yandex. They do not allow the identification of a specific user.
Next, the ball is on the side of the site: collect statistics inside or throw it into Yandex.Metrica. For Metrica, you will need to write a small JS that, when loading any page on your site, will look to see if there is a parameter in the address uuidand, if found, throw an event in Metrica. For example, you can assign this UUID as the UserID of the Metric using the setUserId() method

Answer 3

he opened it, read it and went to the signature on the site

And if you opened it, read it, but did not go through it?
And if you opened it, but preliminarily cutting out the entire html?
And if you opened it, but preliminarily deleting all unnecessary headers?
On the client side, I can do whatever I want with the letter. I want - I accept, I want - I refuse.

Answer 4

UTM tags in theory.