Update time: June 1, 2024
This article introduces FPID in server-side deployment.
What is FPID
The full name of FDID is First-party device IDs, which is actually an ID managed by the user server. It is also the first-party Cookie ID.
Since many browsers are now restricting first-party cookies, the ID created by the user on the server can be better maintained and more effectively marked to track the user.
Advantages of FPID
First-party device IDs have the following advantages:
- FPID will continue to exist and can avoid the impact of browser policies. For example, if Client ID and ECID are cleared, FPID is still there and can effectively identify the user. For example, the first-party cookie generated through CNAME in Safari will expire after 7 days. If cleared, the number of users will be inaccurately calculated.
- HTTPOnly, this cookie can only be obtained through the server, ensuring that the value cannot be accessed by any client script, which is safer.
FPID is not without its shortcomings. Its shortcoming is that if the browser’s subsequent policy changes, it can restrict the first-party device ID.
FPID Example
FPID is only available for server tracking.
Adobe Launch
The FPID is generated by the user’s own server, but the FPID follows the UUIDv4 format, such as
ac619d0b-0bce-4c92-ae26-75b4e93083bd
Generate UUIDv4 and write the UUIDv4 value into cookie to achieve the following effect:
Google Tag Manager
