On January 10, 2022, the maximum number of user_identifers set in a UserData object will be reduced from 100,000 to 20. This is to clarify that each set should represent a single user.

The table below illustrates uploading UserData for two users (John Doe and Max Mustermann), each of whom has two email addresses.




Correct usage 
operations: {
  create: {
    user_identifiers {
      hashed_email: hash(“johndoe@gmail.com”)
    },
    user_identifiers {
       hashed_email: hash(“johndoe@google.com”)
    } 
  }
}
operations: {
  create: {
    user_identifiers {
      hashed_email: hash(“maxmustermann@gmail.com”)
    },
    user_identifiers {
      hashed_email: hash(“maxmustermann@google.com”)
    }
  }
}
Incorrect usage 
operations: {
  create: {
    user_identifiers { 
      hashed_email:  hash(“johndoe@gmail.com”) 
    },
    user_identifiers {
      hashed_email:  hash(“johndoe@google.com”)
    },
    user_identifiers { 
      hashed_email: hash(“maxmustermann@gmail.com”)
    },
    user_identifiers { 
      hashed_email: hash(“maxmustermann@google.com”)
    }
  }
}

UserData is used for Customer Match and store sales uploads. In a given create/remove UserData operation, each set of user_identifiers should be for a single user.

Note that the same total amount of data can be sent in a single request, but each set of user_identifiers must represent a single person.

If the number of user_identifiers for a single set exceeds the new limit of 20, a TOO_MANY_USER_IDENTIFIERS error will be generated.

This will be applied to the two Google Ads API methods that provide UserData uploads:

If you have any questions or need additional help, contact us via the forum.
, Google Ads API Team