We were reviewing this documentation and came across a question we couldn't answer that is also reflected in our data.
In all of the examples provided, the OPEN does not have a UUID, except for in the case of "Henry":
We could not find any documentation as what would cause an open to generate a UUID vs not having one. In our own data, it seems fairly sporadic as to whether the UUID is registered with an open or not, with no clear commonalities. The linked documentation is pretty useful in walking people through how recipients, forwards, and people are captured but this element doesn't appear to have any explanation. Any help is appreciated!
Hi @StevenMcGloin ,
It can be the case that the browser the Customer is using can be an incognito or the browser is not able to calculate the Unique ID to send back to Adobe Campaign, but if we receive the Requestor UUID Data, it will be populated in the trackingLog Schema.
Based on the information provided, it seems like you are referring to some documentation or examples related to a system or application that involves the concept of "open" and "UUID."
In the context you mentioned, the presence or absence of a UUID for an "open" event is not explained in the documentation you reviewed. Without further information about the specific system or application you are referring to, it is difficult to determine the exact reason behind this inconsistency.
Note that the UUID might be optional for specific events or objects depending on the level of data integrity required. If the system can uniquely identify and process the "open" events without relying on a UUID, it might not be necessary to include it in those cases.
Also, the absence of a UUID in some cases might result from historical data or older system versions. Newer versions or updated data might include UUIDs consistently for all relevant events or objects.