Using labels to prevent data from going to edge | Community
Skip to main content
M
MauriP
Level 2
February 18, 2026
Solved

Using labels to prevent data from going to edge

  • February 18, 2026
  • 4 replies
  • 46 views

Hey,

 

I’d have a need to exclude some attributes going from the hub to edge (profile). Suggested approach is to use data governance labels (https://experienceleague.adobe.com/en/docs/experience-platform/data-governance/labels/reference). None of the ootb labels seem to be related to the edge case specifically. Anyone who have done this exercise and would know what labels to use?


Attributes should still be usable for personalization cases that rely on data in the hub.

    Best answer by Sukrity_Wadhwa

    Hi ​@MauriP,

    Since there hasn’t been any recent activity on this thread and as suggested by ​@bjoern__koth and ​@arpan-garg, this use case should be addressed with the help of Adobe Support, so, we’ll be closing this question for now.

    If you have any related questions or updates to share, please don’t hesitate to request to reopen this one or start a new thread. We’d be happy to take another look.

    Thanks!

    4 replies

    bjoern__koth
    Community Advisor and Adobe Champion
    bjoern__kothCommunity Advisor and Adobe Champion
    Community Advisor and Adobe Champion
    February 19, 2026

    Hi ​@MauriP 

    what is your use case or why is data not allowed to end up on the Edge Profile?

    In general, having the Profile on the Edge does not mean it will leave the experience platform nor can it be read out by anyone. It just means that the Profile is considered “interesting”, and you can access the data in real-time personalization.

    The governance labels and policies are the recommended approach to make sure the fields cannot be activated (intentionally or unintentionally) to destinations.

    Cheers from Switzerland!
      M
      MauriPAuthor
      Level 2
      February 19, 2026

      Thanks ​@bjoern__koth for a quick reply.

      It is a security decision. We have a BYOK implementation covering the hub but it does not extend to Adobe’s edge servers, hence the need for preventing PII data from going to edge. We’ve used labels for destinations use cases.

        bjoern__koth
        Community Advisor and Adobe Champion
        bjoern__kothCommunity Advisor and Adobe Champion
        Community Advisor and Adobe Champion
        February 19, 2026

        Thanks for clarifying!

        I did some quick digging but could not find a real solution yet.

        Maybe it's worthwhile reaching out to support 

        Cheers from Switzerland!
        arpan-garg
        Community Advisor
        arpan-gargCommunity Advisor
        Community Advisor
        February 19, 2026

        Hi ​@MauriP  - Are all the profiles attributes from hub getting synced to edge? From my understanding attributes are synced from hub to edge only when you use those attributes in edge decisioning or edge segmentation. 

        Thanks,

        Arpan

          M
          MauriPAuthor
          Level 2
          February 19, 2026

          Not all, your understanding is correct. However, we cannot rely on business users not to include sensitive attributes in segmentation or personalization level, we’d need sandbox level mechanism to block those.

            arpan-garg
            Community Advisor
            arpan-gargCommunity Advisor
            Community Advisor
            February 20, 2026

            Hi ​@MauriP - In that case i would suggest to raise a support ticket to get an answer.

            Sukrity_Wadhwa
            Community Manager
            Sukrity_WadhwaCommunity ManagerAccepted solution
            Community Manager
            March 2, 2026

            Hi ​@MauriP,

            Since there hasn’t been any recent activity on this thread and as suggested by ​@bjoern__koth and ​@arpan-garg, this use case should be addressed with the help of Adobe Support, so, we’ll be closing this question for now.

            If you have any related questions or updates to share, please don’t hesitate to request to reopen this one or start a new thread. We’d be happy to take another look.

            Thanks!

            Sukrity Wadhwa
            Parvesh_Parmar
            Community Advisor
            Parvesh_ParmarCommunity Advisor
            Community Advisor
            March 2, 2026

            Hi @MauriP,

            I’ve completed a similar exercise for a client. If the client requires BYOK (Bring Your Own Key), you must avoid creating any Edge audiences or use cases that move data to the Edge layer. Here’s why:

            Edge is implemented on AWS Cloud and is separate from:
            Profile (Cosmos DB)
            Data Lake (Blob Storage).
            With managed keys, you can encrypt data only in these two layers (Profile/Data Lake), not on Edge.

            Key considerations:

            Data movement to Edge:

            By default, data is not moved to Edge unless explicitly ingested for Edge-specific use cases (e.g., audiences).
            If data is ingested via files or HTTP API, it typically stays in Profile/Data Lake—but confirm this with Adobe to be sure.

            Edge data retention:

            Data only moves to Edge if there’s an active use case (e.g., real-time segmentation).
            Unused Edge data is automatically purged after around 14 days (default Adobe behavior).

            Hope it will help.

            Kr,

            Parvesh

            Parvesh Parmar – Adobe Community Advisor https://www.linkedin.com/in/parvesh-parmar/
            Terms & ConditionsAccessibility statement

            Loading footer...