Skip to main content
All CollectionsINTEGRATIONUSER IDENTIFICATION
How does edrone identify customers?
How does edrone identify customers?
Klaudia Lewandowska avatar
Written by Klaudia Lewandowska
Updated over a year ago

How does edrone identify customers?

We have several ways to identify users:

Identification by entering an email on the site

This is the simplest type of identification. The customer enters an email address on the store page. At the same time, in addition to the email address, two additional identifiers are transmitted:

  • cookie (ccid) - given when communicating with edrone servers

  • identifier in LocalStorage (cid) - a unique identifier generated by the browser.

All of this information is saved by edrone, which allows for the later identification of a non-logged-in user.

Identification after client has previously visited the store and entered an email address

Here we use the information stored in the "identification after entering email on the site" situation. Based on the cookie (ccid) and/or the identifier from local storage (cid) we find the email address.

Limitations:

● If a given computer/browser is used by more than one person, it may

lead to incorrect action assignment (we do not know which person is currently using the computer and browser)

Identification when the email is opened

There are so-called tracking pixels in emails sent by edrone. In addition to counting openings, this mechanism is used for identification. When a user opens an email, the browser sends a request to the edrone system. It contains the individual ID of the client - i.e. the recipient of that particular email. In response to the request, the system returns a cookie (ccid), which is set by the recipient's browser.

When visiting the store, the assigned cookie (ccid) is sent as part of the

event, which allows the user to be identified, even if the email address is not provided on the site.

Limitations:

● Some mail systems (such as Gmail) use proxy mechanisms to send requests for images. In this situation, openings are usually credited, but a cookie is not given to the

recipient's browser.

● Some mail systems and email programs do not download images at all. This makes it impossible to count opens as well as identify when an email has been opened.

● Not all browsers allow you to set a cookie in this way.

● If a given computer/browser is used by more than one person, this can lead to incorrect action assignment (we do not know which person is currently using the computer).

● If the email is forwarded to a third party, then it is their browser will be marked with a cookie (ccid). This can lead to misalignment of actions performed by the third party to the original recipient.

Identification when the email is clicked

In the emails sent by edrone, the links contain an individual identifier of the customer - i.e. the recipient of the email. In addition to counting clicks, this mechanism is used for identification

When a user clicks on a link, the browser sends a request to our system.

In response to the request, the edrone system redirects to the target page (e.g. view

product) and returns a cookie (ccid), which is set by the recipient's browser. During

visiting a store, the assigned cookie (ccid) is sent as part of an event, which

allows the user to be identified, even if the address is not provided on the page.

Limitations:

● If the link is passed to a third party, then it is their browser that will be marked with a cookie (ccid). This can lead to a misattribution of actions performed by the third party to the original recipient.

● If a computer/browser is used by more than one person, this can lead to incorrect action assignment (we do not know which person is currently using the computer).

You can find more information about cookies and other identifiers that are used to identify and collect customer data in our technical documentation: https://docs.edrone.me/visitors.html


Need more help?

If you have any further questions about the identification, please do not hesitate to contact us at hello@edrone.me


Did this answer your question?