From 187e86db8233eb4439f7f4b9f06e6e7d5d9d6ff5 Mon Sep 17 00:00:00 2001 From: Juan Langlois Date: Tue, 7 Jan 2025 09:23:57 -0300 Subject: [PATCH] fix: improve opaque user id definition --- topsort-api-v2.yml | 12 +++++++----- 1 file changed, 7 insertions(+), 5 deletions(-) diff --git a/topsort-api-v2.yml b/topsort-api-v2.yml index e246038..03bab8d 100644 --- a/topsort-api-v2.yml +++ b/topsort-api-v2.yml @@ -411,11 +411,13 @@ components: OpaqueUserID: type: string description: - Ideally the same user for events. The opaque user ID allows correlating user activity, such as Impressions, Clicks and Purchases, - whether or not they are actually logged in. It must be long lived (at least a year) so that Topsort can - attribute purchases. If your users are always logged in you may use a hash of your customer ID. If your users - may interact with your app or site while logged out we recommend generating a random identifier (UUIDv4) on - first load and store it on local storage (cookie, local storage, etc) and let it live for at least a year. + An anonymized unique identifier that maps to the original user ID without revealing the original value. + Ideally the same user for events. The opaque user ID allows correlating user activity, such as Impressions, + Clicks and Purchases, whether or not they are actually logged in. It must be long lived (at least a year) so + that Topsort can attribute purchases. If your users are always logged in you may use a hash of your customer ID. + If your users may interact with your app or site while logged out we recommend generating a random identifier + (UUIDv4) on first load and store it on local storage (cookie, local storage, etc) and let it live for at least + a year. example: 71303ce0-de89-496d-8270-6434589615e8 PlacementId: