Best practices

Keep the following best practices in mind when using the Data Manager API.

Send all user identifiers

Whether sending audience members or events with UserData , include as many user_identifiers as possible, including sending multiple identifiers of the same type.

For example, if you have multiple email addresses for a user, include a separate UserIdentifier for each email address. Similarly, if you have identifiers of different types for a user, such as email addresses, phone numbers, and addresses, add a separate UserIdentifier for each identifier, up to the maximum identifier count .

Optimize requests

To reduce the likelihood of exceeding daily request limits, batch as many items as possible in each request, up to the per-request limits .

For example, if you want to add 10,000 audience members to an audience, add all 10,000 members in the audience_members list in one IngestAudienceMembersRequest . Batching all 10,000 members in a single request is far more efficient than sending a separate request to add each audience member.

Send concurrent requests

To reduce the overall time required to ingest data, send concurrent requests to the IngestionService . We recommend sending up to 10 requests concurrently to reduce the likelihood of exceeding the requests per minute limit .

You can send concurrent requests even if the requests have the same destinations .