V19 membership lifespan clarification

[Dhinesh KaNnan]

Hi GAds Team,

We were previously using version 17 of the API and have now started testing with version 19. I noticed that in v19, the lifespan for customer list members is set to 540 days, whereas earlier we used a default of 10,000 days.

I would like to clarify whether the lifespan applies at the member/user level or at the customer list level.

For example:

If I upload 1,000 PII records to Customer List A and another 1,000 records to Customer List B, and

In the following month, I refresh Customer List A with 500 new records,

Will the entire Customer List A get its lifespan reset to 540 days, or will only the new 500 records have the 540 days lifespan from their upload date, while the existing records retain their original expiry timeline?

Your clarification on this would be very helpful for our planning and implementation.

[Google Ads API Forum Advisor]

Hi,

Thank you for reaching out to the Google Ads API support team.​

Please note that, starting on April 7, 2025, requests to set the UserList.membership_life_span field in the Google Ads API to greater than 540 will return a RangeError.TOO_HIGH error. We recommend you check your current implementation to make sure you no longer set the field value to greater than 540.​ ​ ​ ​ ​ ​ ​

Additionally, for existing user lists with membership_life_span field in the Google Ads API greater than 540, starting from April 7, 2025 customer data user lists will be automatically migrated to have a membership life span of the maximum 540 days. If you need to update your code to regularly refresh your customer lists, check out our guide for examples. And no action is required if you do not set the membership_life_span field in the Google Ads API and you regularly refresh your customer lists. Leaving the field unset has the same effect as setting it to the maximum 540 days value.

You may find more details in this customer match document and blog post. 

Thanks,
 

Google Ads API Team

Feedback
How was our support today?

               
[2025-06-17 08:47:03Z GMT] This message is in relation to case "ref:!00D1U01174p.!500Ht01rfTU0:ref" (ADR-00314635)