From 2122212aabe51f1b192b19520296a1ab18234b0f Mon Sep 17 00:00:00 2001 From: Peixun Zhang Date: Fri, 20 Jun 2025 10:54:53 +0200 Subject: [PATCH] DATA-25163 Remove documentation asking clients not to cache things in storage --- dev-docs/modules/userid-submodules/liveintent.md | 5 +---- 1 file changed, 1 insertion(+), 4 deletions(-) diff --git a/dev-docs/modules/userid-submodules/liveintent.md b/dev-docs/modules/userid-submodules/liveintent.md index 842cdb94fb..16696bd312 100644 --- a/dev-docs/modules/userid-submodules/liveintent.md +++ b/dev-docs/modules/userid-submodules/liveintent.md @@ -106,7 +106,7 @@ The attributes `uid2`, `medianet`, `magnite`, `bidswitch`, `pubmatic`, `openx`, #### Note * `thetradedesk` will be exposed as `tdid` because of historical reasons. -* In order for `segments` to be present in `ortb2.user.data` of the bid requests, you need to configure the [liveIntentRTDProvider](/dev-docs/modules/liveIntentRtdProvider.html) module. +* In order for `segments` to be present in `ortb2.user.data` of the bid requests, you need to configure the [liveIntentRTDProvider](/dev-docs/modules/liveIntentRtdProvider.html) module. For example, in case `uid2` is configured to be requested in addition to the `nonID`, the `request.userId` object would look like the following: @@ -195,9 +195,6 @@ pbjs.setConfig({ ## LiveIntent ID configuration -{: .alert.alert-info :} -NOTE: For optimal performance, the LiveIntent ID sub-module should be called at every opportunity. It is best not to use `params.storage` with this sub-module as it has its own optimal caching mechanism. - {: .table .table-bordered .table-striped } | Param under userSync.userIds[] | Scope | Type | Description | Example |