ÃÛ¶¹ÊÓƵ

First-party device IDs in Web SDK

The ÃÛ¶¹ÊÓƵ Experience Platform Web SDK assigns ÃÛ¶¹ÊÓƵ Experience Cloud IDs (ECIDs) to website visitors by using cookies, to track user behavior. To account for browser restrictions on cookie lifespans, you can choose to set and manage your own device identifiers instead. These are referred to as first-party device IDs (FPIDs).

This document explains how to configure first-party device IDs for your Web SDK implementation.

Prerequisites

This guide assumes you are familiar with how identity data works for the Platform Web SDK, including the role of ECIDs and identityMap. See the overview on identity data in the Web SDK for more information.

Using first-party device IDs (FPIDs) using-fpid

First-party device IDs (FPIDs) track visitors by using first-party cookies. First-party cookies are most effective when they are set using a server that uses a DNS (for IPv4) or (for IPv6), as opposed to a DNS CNAME or JavaScript code.

Once an FPID cookie is set, its value can be fetched and sent to ÃÛ¶¹ÊÓƵ as event data is collected. Collected FPIDs are used as seeds to generate ECIDs, which continue to be the primary identifiers in ÃÛ¶¹ÊÓƵ Experience Cloud applications.

To send an FPID for a website visitor to the Edge Network, you must include the FPID in the identityMap for that visitor. See the section further down in this document on using FPIDs in identityMap for more information.

First-party device ID formatting requirements formatting-requirements

The Edge Network only accepts IDs that comply with the . Device IDs that are not in UUIDv4 format will be rejected.

Generation of a UUID will almost always result in a unique, random ID, with the probability of a collision occurring being negligible. UUIDv4 cannot be seeded using IP addresses or any other personal identifiable information (PII). UUIDs are ubiquitous and libraries can be found for virtually every programming language to generate them.

Setting a first-party ID cookie in the Datastreams UI setting-cookie-datastreams

You can specify a cookie name in the Datastreams user interface, where the FPID can reside, rather than having to read the cookie value and include the FPID in the identity map.

See the datastreams documentation for detailed information on how to configure a datastream.

When configuring your datastream, enable the First Party ID Cookie option. This setting tells the Edge Network to refer to a specified cookie when looking up a first-party device ID, rather than looking up this value in the identity map.

See the documentation on first-party cookies for more details on how they work with ÃÛ¶¹ÊÓƵ Experience Cloud.

When enabling this setting, you must provide the name of the cookie where the ID is expected to be stored.

When you use first-party IDs, you cannot perform third-party ID syncs. Third-party ID syncs rely on the Visitor ID service and the UUID generated by that service. When using the first-party ID functionality, the ECID is generated without the use of the Visitor ID service, which makes third-party ID syncs impossible.

When you use first-party IDs, Audience Manager capabilities targeted towards activation in partner platforms are not supported, given that Audience Manager Partner ID syncs are mostly based on UUIDs or DIDs. The ECID that is derived off a first-party ID is not linked to a UUID, making it unaddressable.

Setting a cookie using your own server set-cookie-server

When setting a cookie using a server that you own, you can use various methods to prevent the cookie from being restricted due to browser policies:

When to set the cookie when-to-set-cookie

The FPID cookie should ideally be set before making any requests to the Edge Network. However, in scenarios where that is not possible, an ECID is still generated using existing methods and acts as the primary identifier as long as the cookie exists.

Assuming the ECID is eventually impacted by a browser deletion policy, but the FPID is not, the FPID will become the primary identifier on the next visit and will be used to seed the ECID on each subsequent visit.

Setting the expiration for the cookie set-expiration

Setting the expiration of a cookie is something that should be carefully considered as you implement the FPID functionality. When deciding this, you should consider the countries or regions in which your organization operates along with the laws and policies in each one of those regions.

As part of this decision, you may want to adopt a company-wide cookie-setting policy or one that varies for users in each locale where you operate.

Regardless of the setting you choose for the initial expiration of a cookie, you must ensure you include logic that extends the expiration of the cookie each time a new visit to the site occurs.

Impact of cookie flags cookie-flag-impact

There are various cookie flags that impact how cookies are treated across different browsers:

HTTPOnly http-only

Cookies set using the HTTPOnly flag cannot be accessed using client-side scripts. This means that if you set an HTTPOnly flag when setting the FPID, you must use a server-side scripting language to read the cookie value for inclusion in the identityMap.

If you choose to have the Edge Network read the value of the FPID cookie, setting the HTTPOnly flag ensures that the value is not accessible by any client-side scripts but will not have any negative impact on the Edge Network’s ability to read the cookie.

Secure secure

Cookies set with the Secure attribute are only sent to the server with an encrypted request over the HTTPS protocol. Using this flag can help ensure that man-in-the-middle attackers cannot easily access the value of the cookie. When possible, it is always a good idea to set the Secure flag.

SameSite same-site

The SameSite attribute lets servers determine whether cookies are sent with cross-site requests. The attribute provides some protection against cross-site forgery attacks. Three possible values exist: Strict, Lax, and None. Consult your internal team to determine which setting is right for your organization.

If no SameSite attribute is specified, the default setting for some browsers is now SameSite=Lax.

Using FPIDs in identityMap identityMap

Below is an example of how you would set an FPID in the identityMap:

{
  "identityMap": {
    "FPID": [
      {
        "id": "123e4567-e89b-42d3-9456-426614174000",
        "authenticatedState": "ambiguous",
        "primary": true
      }
    ]
  }
}

As with other identity types, you can include the FPID with other identities within identityMap. The following is an example of the FPID included with an authenticated CRM ID:

{
  "identityMap": {
    "FPID": [
      {
        "id": "123e4567-e89b-42d3-9456-426614174000",
        "authenticatedState": "ambiguous",
        "primary": false
      }
    ],
    "EMAIL": [
      {
        "id": "email@mail.com",
        "authenticatedState": "authenticated",
        "primary": true
      }
    ]
  }
}

If the FPID is contained in a cookie being read by the Edge Network when first-party data collection is enabled, you should capture only the authenticated CRM ID:

{
  "identityMap": {
    "EMAIL": [
      {
        "id": "email@mail.com",
        "authenticatedState": "authenticated",
        "primary": true
      }
    ]
  }
}

The following identityMap would result in an error response from the Edge Network since it is missing the primary indicator for the FPID. At last one of the IDs present in identityMap must be marked as primary.

{
  "identityMap": {
    "FPID": [
      {
        "id": "123e4567-e89b-12d3-a456-426614174000",
        "authenticatedState": "ambiguous"
      }
    ],
    "EMAIL": [
      {
        "id": "email@mail.com",
        "authenticatedState": "authenticated"
      }
    ]
  }
}

The error response returned by the Edge Network in this case would be similar to the following:

{
    "type": "https://ns.adobe.com/aep/errors/EXEG-0306-400",
    "status": 400,
    "title": "No primary identity set in request (event)",
    "detail": "No primary identity found in the input event. Update the request accordingly to your schema and try again.",
    "report": {
        "requestId": "{REQUEST_ID}",
        "configId": "{CONFIG_ID}",
        "orgId": "{ORG_ID}"
    }
}

Setting an FPID on your own domain setting-fpid-domain

In addition to setting the FPID in the identity map, you can set the FPID cookie on your own domain, if you have a first-party data collection CNAME configured.

When first-party data collection is enabled using a CNAME, all cookies for your domain will be sent on requests made to the data collection endpoint.

All cookies not relevant to ÃÛ¶¹ÊÓƵ’s data collection purposes are dropped. For FPID, you can specify the name of the FPID cookie in the datastream configuration. When you do this, the Edge Network will read the contents of the FPID cookie instead of looking for the FPID in the identity map.

To use this functionality, you need to set the FPID at the top level of your domain instead of a specific subdomain. If you set it on a subdomain, the cookie value will not be sent to the Edge Network and the FPID solution will not work as intended.

ID hierarchy id-hierarchy

When both an ECID and FPID are present, the ECID is prioritized in identifying the user. This ensures that when an existing ECID is present in the browser cookie store, it remains the primary identifier and existing visitor counts do not risk being affected. For existing users, the FPID will not become the primary identity until the ECID expires or is deleted as a result of a browser policy or manual process.

Identities are prioritized in the following order:

Migrating to first-party device IDs migrating-to-fpid

If you are migrating to first-party device IDs from a previous implementation, it may be difficult to visualize what the transition might look like at a low level.

To help illustrate this process, consider a scenario that involves a customer who has previously visited your site and what impact an FPID migration would have on how that customer is identified in ÃÛ¶¹ÊÓƵ solutions.

FAQ faq

The following is a list of answers to frequently asked questions about first-party device IDs.

How is seeding an ID different from simply generating an ID?

The concept of seeding is unique in that the FPID passed to ÃÛ¶¹ÊÓƵ Experience Cloud is converted to an ECID using a deterministic algorithm. Each time the same FPID is sent to the Edge Network, the same ECID is seeded from the FPID.

When should the first-party device ID be generated?

To reduce potential visitor inflation, the FPID should be generated before making your first request using the Web SDK. However, if you are unable to do this, an ECID will still be generated for that user and will be used as the primary identifier. The FPID that was generated will not become the primary identifier until the ECID is no longer present.

Which data collection methods support first-party device IDs?

Currently only Web SDK supports first-party device IDs.

Are first-party device IDs stored on any Platform or Experience Cloud solutions?

Once the FPID has been used to seed an ECID, it is dropped from the identityMap and replaced with the ECID that has been generated. The FPID is not stored in any ÃÛ¶¹ÊÓƵ Experience Platform or Experience Cloud solutions.