From 02eadae40752ac7c549ca28c0c013ac778178bc7 Mon Sep 17 00:00:00 2001 From: Juan Langlois Date: Fri, 10 Jan 2025 11:09:31 -0300 Subject: [PATCH] fix: opaque user id delete second "year long" --- topsort-api-v2.yml | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/topsort-api-v2.yml b/topsort-api-v2.yml index 4a90d7a..897742e 100644 --- a/topsort-api-v2.yml +++ b/topsort-api-v2.yml @@ -417,7 +417,7 @@ components: logged out, we recommend generating a random identifier (UUIDv7) on the first load, storing it on local storage (cookie, local storage, etc), and letting it live for at least a year. Otherwise, if your users are always logged in for interactions, you may use a hash of your customer ID. Correct purchase attribution requires - long-lived (at least a year) opaque user IDs consistent between auction and event requests. + long-lived opaque user IDs consistent between auction and event requests. example: 71303ce0-de89-496d-8270-6434589615e8 PlacementId: