-
Notifications
You must be signed in to change notification settings - Fork 17
finished first stage #1243
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
base: main
Are you sure you want to change the base?
finished first stage #1243
Conversation
|
The latest updates on your projects. Learn more about Vercel for Git ↗︎
|
| ### Fingerprint Browser Agent on Page Load | ||
|
|
||
| The JavaScript agent is loaded at page load time, and the function to get the visitor ID is run right away. For more information, refer to [Fingerprint on Page Load](get-started-fingerprinting.md#fingerprint-on-page-load). | ||
| The script used to activate the agent affects the performance of the Fingerprint service. For example, activating the Javascript agents at page load time also runs a function that generates the `visitorId`, improving the speed and performance, unlike the script that activates the agent after clicking on a button, which takes longer. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I dont think we should say it like this in customer facing docs.
The point is that with FPS, the end user is free to choose when they want to call the service - either on page load or button click, etc. It is the way it is for flexibility and has no direct correlation with FPS performance.
| First-party cookies are created by the host domain, i.e., the website the user visits. For example, when visiting example.com, the cookies stored by example.com are first-party cookies. This class of cookies helps improve user experience and is considered non-intrusive. Some examples of these cookies include: | ||
|
|
||
| - **User authentication cookies:** These cookies help store login and authentication details. | ||
| - **Language preference cookies :** Cookies in this class are offered by multi-lingual sites and help to store your preferred language so that subsequent visits to the same site display in your preferred language. | ||
| - **Personalization cookies:** Personalization cookies store your preferred browsing settings and preferences to ensure a seamless browsing experience. | ||
| - **Session management cookies:** These cookies improve browsing sessions by keeping track of changes during a previous session as a user moves from page to page. | ||
|
|
||
| Other first-party cookies include analytics, security, and e-commerce shopping cart cookies. | ||
|
|
||
| ### Using First-party Cookies | ||
|
|
||
| Information collected by first-party cookies are only shared with the host website. They also help improve the user experience when navigating a site by storing login details, personalizing website settings, and tracking user behavior for the site's own analytics. | ||
|
|
||
| ### Data Privacy Concerns and Implications | ||
|
|
||
| Data privacy laws consider first-party cookies essential as they are | ||
| generally considered less intrusive in terms of privacy, as their usage often occurs by the site the user has chosen to visit. However, they can still raise privacy concerns, especially when collecting sensitive information. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Do we really need all this explaining first & third party in the FPS docs?
Rewrote some sections. Will be adding to it with time.