When searching for transaction receipts by Sourcepoint UUID there are generally two methods by which you can retrieve the value(s) for these UUIDs: UUID in mesage or cookies and local storage.
How your organization retrieves a UUID will decide whether any reformatting is required to successfully retrieve a record using the transaction receipts feature. In this article, we will cover the following:
Sourcepoint UUID formatting
Consent records and preferences records are stored against discrete Sourcepoint UUIDs on a per campaign basis (GDPR, U.S. Multi-State Privacy, Preferences).
Since your organization can have multiple campaigns running on a single property (e.g. GDPR and Preferences) for which the end-user has provided consent and preferences, transaction receipts enable you to search for an end-user's transactions across all of these campaigns. This is done by concatenating all of the Sourcepoint UUIDs for an end-user and delimiting by the ~ symbol.
Please review the table below for the correct formatting for each Sourcepoint UUID when utilizing transaction receipts:
| Type | Sourcepoint UUID Format | Description |
| GDPR | gdprUUID~~ |
Sourcepoint UUID for an end-user's consent to a GDPR campaign only |
| U.S. Multi-State Privacy | ~USmspsUUID~ |
Sourcepoint UUID for an end-user's consent to a U.S. Multi-State Privacy campaign only |
| Preferences | ~~preferencesUUID |
Sourcepoint UUID for an end-user's preferences for a Preferences campaign only |
| Multiple | ~gdpr~USmsps~preferences |
A concatenation of possible Sourcepoint UUIDs for multiple different campaigns. Note: The order of the Sourcepoint UUIDs and delimitation symbols matter for concatenated searches. For example, if you are searching for GDPR and Preferences records, the search should be |
UUID in cookies and local storage
If your organization is accessing the Sourcepoint UUIDs directly from cookies or local storage then you will need to manually reformat the value to adhere to the specification above.
UUID in message
To use the UUID retrieved from a message, you will just need to copy the UUID value from the message and paste it into transaction receipts when searching by Sourcepoint UUID.
When designing your first layer message, privacy managers, and/or preferences messages, your organization has the ability to add Sourcepoint UUIDs directly to the message. See below for more information:
Resources
If your organization includes the end-user UUID in your messages, Sourcepoint will surface all of the end-user's UUIDs that have been stored for the campaigns on the property. This value will be concatenated, in the correct order, and with the delimiters already applied.
Comments
0 comments