Automatically Assign a GraphID (UUID) attribute During Data Ingestion in AEP?

[JeanBaro_]

Hello,

Please, is there a way to automate the assignment of a unique custom GraphID attribute in Adobe Experience Platform (AEP) whenever data (contact information) about a user/lead/customer is ingested (via API, WebSDK, Mobile SDK, Batch import or any other ingestion method supported by AEP) without requiring a second call from the client? Essentially, like a built-in trigger in a database.

Requirements:

1. Check for Existing GraphID:

   • When new data is ingested, automatically check if the resulting graph already has a GraphID attribute.

2. Assign UUID if No GraphID is Found:

   • If there is no GraphID, generate a UUID and assign it as the GraphID attribute within this new unique profile in AEP. This should only occur for brand new unique profiles (graphs), as existing unique profiles (graphs) should already have their own GraphID attribute set, similar to how they have emails and phone numbers, but the GraphID should be a single attribute, not multiples.

Goal:

• Ensure each graph usually has a single, unique GraphID linked to it.
• If two graphs merge, the combined graph should have multiple GraphIDs, indicating the merge (which is a situation that I will handle separately).

I want this to be an automatic, atomic process within AEP, triggered with each data ingestion, to avoid requiring a second call for UUID generation and to prevent data inconsistency.

How can I set this up in AEP? Any detailed steps or documentation references would be greatly appreciated.

Thanks!

[JeanBaro_ · Accepted solution]

Complementing the scenario:

If generating a UUID directly within AEP is not feasible without external or costly solutions (such as Adobe I/O Runtime), can the caller always include a SuggestedGraphID UUID as part of the payload? This SuggestedGraphID would be used by AEP only if the GraphID is not already present, ensuring that new unique profiles receive a unique identifier automatically. If a GraphID already exists in the unique profile, the SuggestedGraphID would be discarded.

In the Data Prep scenario, having an already generated UUID in hand might simplify the solution, but I don't actually know.