From cca95828602cba432bfe10b5d6809629b898055f Mon Sep 17 00:00:00 2001 From: sean wibisono Date: Fri, 17 Apr 2026 14:28:00 +1000 Subject: [PATCH 1/5] add 20 concurrent requests restriction --- docs/endpoints/post-identity-map-v2.md | 4 ++-- docs/endpoints/post-identity-map.md | 4 ++-- 2 files changed, 4 insertions(+), 4 deletions(-) diff --git a/docs/endpoints/post-identity-map-v2.md b/docs/endpoints/post-identity-map-v2.md index 6c0d9406c..a36267e3b 100644 --- a/docs/endpoints/post-identity-map-v2.md +++ b/docs/endpoints/post-identity-map-v2.md @@ -23,12 +23,12 @@ This documentation is for version 2 of this endpoint, which is not the latest ve If you're using an earlier version, we recommend that you upgrade as soon as possible, to take advantage of improvements. For migration guidance, see [Migration from v2 Identity Map](post-identity-map.md#migration-from-v2-identity-map). For deprecation information, see [Deprecation Schedule: Endpoint Versions](../ref-info/deprecation-schedule.md#endpoint-versions). ::: -## Batch Size Requirements +## Batch Size and Request Parallelization Requirements Here's what you need to know: - The maximum request size is 1MB. -- To map a large number of email addresses, phone numbers, or their respective hashes, send them in batches with a maximum of 5,000 items per batch. +- To map a large number of email addresses, phone numbers, or their respective hashes, send them in batches with a maximum of 5,000 items per batch. You may send up to 20 batches in parallel. - Be sure to store mappings of email addresses, phone numbers, or their respective hashes.
Not storing mappings could increase processing time drastically when you have to map millions of email addresses or phone numbers. Recalculating only those mappings that actually need to be updated, however, reduces the total processing time because only about 1/365th of raw UID2s need to be updated daily. See also [Advertiser/Data Provider Integration Overview](../guides/integration-advertiser-dataprovider-overview.md) and [FAQs for Advertisers and Data Providers](../getting-started/gs-faqs.md#faqs-for-advertisers-and-data-providers). ## Rate Limiting diff --git a/docs/endpoints/post-identity-map.md b/docs/endpoints/post-identity-map.md index a55a44ba2..d90a64279 100644 --- a/docs/endpoints/post-identity-map.md +++ b/docs/endpoints/post-identity-map.md @@ -23,12 +23,12 @@ This documentation is for the latest version of this endpoint, version 3. If needed, documentation is also available for the previous version: see [POST /identity/map (v2)](post-identity-map-v2.md). -## Batch Size Requirements +## Batch Size and Request Parallelization Requirements Here's what you need to know: - The maximum request size is 1MB. -- To map a large number of email addresses, phone numbers, or their respective hashes, send them in batches with a maximum of 5,000 items per batch. +- To map a large number of email addresses, phone numbers, or their respective hashes, send them in batches with a maximum of 5,000 items per batch. You may send up to 20 batches in parallel. - Be sure to store mappings of email addresses, phone numbers, or their respective hashes.
Not storing mappings could increase processing time drastically when you have to map millions of email addresses or phone numbers. Recalculating only those mappings that actually need to be updated, however, reduces the total processing time because only about 1/365th of UID2s need to be updated daily. See also [Advertiser/Data Provider Integration Overview](../guides/integration-advertiser-dataprovider-overview.md) and [FAQs for Advertisers and Data Providers](../getting-started/gs-faqs.md#faqs-for-advertisers-and-data-providers). ## Rate Limiting From 133132574a78e3bf93aa8e01c9145b344b59f43e Mon Sep 17 00:00:00 2001 From: sean wibisono Date: Fri, 17 Apr 2026 15:18:56 +1000 Subject: [PATCH 2/5] add Documentation Updates entry --- docs/ref-info/updates-doc.md | 24 ++++++++++++++++++++++-- 1 file changed, 22 insertions(+), 2 deletions(-) diff --git a/docs/ref-info/updates-doc.md b/docs/ref-info/updates-doc.md index 2fdea7742..5a2cc3227 100644 --- a/docs/ref-info/updates-doc.md +++ b/docs/ref-info/updates-doc.md @@ -20,9 +20,25 @@ Check out the latest updates to our UID2 documentation resources. Use the Tags toolbar to view a subset of documentation updates. ::: -## Q1 2026 +## Q2 2026 -The following documents were released in the first quarter of 2026. +The following documents were released in the second quarter of 2026. + + + +### Request Parallelization Updates for POST /identity/map + +April 17, 2026 + +The [POST /identity/map](../endpoints/post-identity-map.md) endpoint documentation has been updated with the following changes: + +- Added a recommendation to send up to 20 /identity/map batches in parallel. + +These changes apply to both [v2](../endpoints/post-identity-map-v2.md) and [v3](../endpoints/post-identity-map.md) endpoints. + + + + @@ -41,6 +57,10 @@ These changes apply to both [v2](../endpoints/post-identity-map-v2.md) and [v3]( +## Q1 2026 + +The following documents were released in the first quarter of 2026. + ### Removal of optout_check Parameter From 5454cd19d1e0b0702eb4cab1109f42056f869fb8 Mon Sep 17 00:00:00 2001 From: sean wibisono Date: Mon, 20 Apr 2026 17:11:58 +1000 Subject: [PATCH 3/5] remove entry from Documentation Updates --- docs/ref-info/updates-doc.md | 16 ---------------- 1 file changed, 16 deletions(-) diff --git a/docs/ref-info/updates-doc.md b/docs/ref-info/updates-doc.md index 5a2cc3227..335dfa053 100644 --- a/docs/ref-info/updates-doc.md +++ b/docs/ref-info/updates-doc.md @@ -26,22 +26,6 @@ The following documents were released in the second quarter of 2026. -### Request Parallelization Updates for POST /identity/map - -April 17, 2026 - -The [POST /identity/map](../endpoints/post-identity-map.md) endpoint documentation has been updated with the following changes: - -- Added a recommendation to send up to 20 /identity/map batches in parallel. - -These changes apply to both [v2](../endpoints/post-identity-map-v2.md) and [v3](../endpoints/post-identity-map.md) endpoints. - - - - - - - ### Rate Limiting and Parallel Request Updates for POST /identity/map April 1, 2026 From f25e1a731d97a812d054bd8561a832ee0b58c66f Mon Sep 17 00:00:00 2001 From: swibi-ttd Date: Mon, 20 Apr 2026 17:12:48 +1000 Subject: [PATCH 4/5] Update wording for concurrency recommendation Co-authored-by: Gen Whitt <107279666+genwhittTTD@users.noreply.github.com> --- docs/endpoints/post-identity-map-v2.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/endpoints/post-identity-map-v2.md b/docs/endpoints/post-identity-map-v2.md index a36267e3b..dfe44d160 100644 --- a/docs/endpoints/post-identity-map-v2.md +++ b/docs/endpoints/post-identity-map-v2.md @@ -28,7 +28,7 @@ If you're using an earlier version, we recommend that you upgrade as soon as pos Here's what you need to know: - The maximum request size is 1MB. -- To map a large number of email addresses, phone numbers, or their respective hashes, send them in batches with a maximum of 5,000 items per batch. You may send up to 20 batches in parallel. +- To map a large number of email addresses, phone numbers, or their respective hashes, send them in batches with a maximum of 5,000 items per batch. We recommend sending no more than 20 batches in parallel. - Be sure to store mappings of email addresses, phone numbers, or their respective hashes.
Not storing mappings could increase processing time drastically when you have to map millions of email addresses or phone numbers. Recalculating only those mappings that actually need to be updated, however, reduces the total processing time because only about 1/365th of raw UID2s need to be updated daily. See also [Advertiser/Data Provider Integration Overview](../guides/integration-advertiser-dataprovider-overview.md) and [FAQs for Advertisers and Data Providers](../getting-started/gs-faqs.md#faqs-for-advertisers-and-data-providers). ## Rate Limiting From f20d8b7fcdaed1d970d1daf77d7dd854ed33dcce Mon Sep 17 00:00:00 2001 From: sean wibisono Date: Mon, 20 Apr 2026 17:14:10 +1000 Subject: [PATCH 5/5] update wording for concurrency recommendation --- docs/endpoints/post-identity-map.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/endpoints/post-identity-map.md b/docs/endpoints/post-identity-map.md index d90a64279..13738bf7c 100644 --- a/docs/endpoints/post-identity-map.md +++ b/docs/endpoints/post-identity-map.md @@ -28,7 +28,7 @@ If needed, documentation is also available for the previous version: see [POST / Here's what you need to know: - The maximum request size is 1MB. -- To map a large number of email addresses, phone numbers, or their respective hashes, send them in batches with a maximum of 5,000 items per batch. You may send up to 20 batches in parallel. +- To map a large number of email addresses, phone numbers, or their respective hashes, send them in batches with a maximum of 5,000 items per batch. We recommend sending no more than 20 batches in parallel. - Be sure to store mappings of email addresses, phone numbers, or their respective hashes.
Not storing mappings could increase processing time drastically when you have to map millions of email addresses or phone numbers. Recalculating only those mappings that actually need to be updated, however, reduces the total processing time because only about 1/365th of UID2s need to be updated daily. See also [Advertiser/Data Provider Integration Overview](../guides/integration-advertiser-dataprovider-overview.md) and [FAQs for Advertisers and Data Providers](../getting-started/gs-faqs.md#faqs-for-advertisers-and-data-providers). ## Rate Limiting