Skip to content

UID2-6917 Add 20 concurrent requests restriction for /identity/map #1012

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
swibi-ttd wants to merge 2 commits into
base: main
Choose a base branch
from
+26 −6
Open

UID2-6917 Add 20 concurrent requests restriction for /identity/map #1012

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
cca9582
add 20 concurrent requests restriction
swibi-ttd Apr 17, 2026
1331325
add Documentation Updates entry
swibi-ttd Apr 17, 2026
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
4 changes: 2 additions & 2 deletions docs/endpoints/post-identity-map-v2.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -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.
Copy link
Copy Markdown
Collaborator

@genwhittTTD genwhittTTD Apr 17, 2026

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Say "can" rather than "may" here. We're not giving them permission, we're stating capabilities. (though per the description this is a recommendation? Either way it's not quite right. But we should be clear whether it's a recommendation or a requirement. Suggest:

Suggested change
- 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.

Or if it's an even more firm recommendation, we could say:

Do not send more than 20 batches in parallel.

That also leaves me wondering why, though. If there's anything we can comfortably share it would be good. Very likely not but checking in case we could say something like this:

To avoid processing delays, do not send more than 20 batches in parallel.

That gives them a purpose. Though, again, it might be too much info.

- Be sure to store mappings of email addresses, phone numbers, or their respective hashes.<br/>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
Expand Down
4 changes: 2 additions & 2 deletions docs/endpoints/post-identity-map.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -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.
Copy link
Copy Markdown
Collaborator

@genwhittTTD genwhittTTD Apr 17, 2026

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Same here.

- Be sure to store mappings of email addresses, phone numbers, or their respective hashes.<br/>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
Expand Down
24 changes: 22 additions & 2 deletions docs/ref-info/updates-doc.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -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
Copy link
Copy Markdown
Collaborator

@genwhittTTD genwhittTTD Apr 17, 2026

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

We only announce major documents, basically... not small fixes like this. Suggest just remove the new section (leave the fix of course since it's a correction to existing content). Though actually my comment applies to the Rate Limiting changes also.

If there's some specific reason we should include it, OK... but there have been many, many changes that we don't announce. I looked over the doc and appreciate that this isn't clear from the heading.

This is something I'll ask SW and KK about. I'll copy you on it. For now, your call.


The following documents were released in the first quarter of 2026.
The following documents were released in the second quarter of 2026.

<CustomTagsContainer tags="Endpoints">

### Request Parallelization Updates for POST /identity/map

April 17, 2026

The [POST&nbsp;/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.
Copy link
Copy Markdown
Collaborator

@genwhittTTD genwhittTTD Apr 17, 2026

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Just saying in case you end up keeping it -- the way this is written it doesn't sound like a limit. It sounds like we're recommending sending lots. Suggest use the same rewording as on the other entries, if that makes sense.

Added a recommendation to send not more than 20 batches in parallel.

Something like that. But better we don't list a doc change this small.


These changes apply to both [v2](../endpoints/post-identity-map-v2.md) and [v3](../endpoints/post-identity-map.md) endpoints.

<!-- UID2-6917 -->

</CustomTagsContainer>

<CustomTagsContainer tags="Endpoints">

Expand All @@ -41,6 +57,10 @@ These changes apply to both [v2](../endpoints/post-identity-map-v2.md) and [v3](

</CustomTagsContainer>

## Q1 2026

The following documents were released in the first quarter of 2026.

<CustomTagsContainer tags="Endpoints, SDKs, Opt-Out">

### Removal of optout_check Parameter
Expand Down
Loading