From 6fad52f837c73bdd69671ccbcd2f28b3509bab58 Mon Sep 17 00:00:00 2001 From: Juan Langlois Date: Tue, 7 Jan 2025 09:29:28 -0300 Subject: [PATCH] chore: rerun prettier --- topsort-api-v2.yml | 10 +++++----- 1 file changed, 5 insertions(+), 5 deletions(-) diff --git a/topsort-api-v2.yml b/topsort-api-v2.yml index 03bab8d..d039d3f 100644 --- a/topsort-api-v2.yml +++ b/topsort-api-v2.yml @@ -411,12 +411,12 @@ components: OpaqueUserID: type: string description: - 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 + 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 + 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