Deprecated Audience Segments - Life Events

[Isabelle Samways]

I'm creating campaigns using `mutateOperations`, and I send everything to be create on these operations.

When I try to create I get an error about audience dimension. Basically I tested with all Life Events and I got a list from all Life Events deprecated. I got all the errors, also those aren't showing up on the ads pannel too.

Deprecated Life Events:
95014 - "Recently Engaged"
95029 - "Becoming an Empty Nester"
95030 - "Last Child Moving Out Soon"
95031 - "Last Child Recently Moved Out"
95035 - "Purchasing First Home Soon"
95036 - "Recently Purchased First Home"
95037 - "Taking a Trip"
95038 - "Researching Destinations"
95039 - "Preparing for Upcoming Trip"
95040 - "Currently Traveling"
95041 - "Recently Returned from Trip"

However, I still can get these deprecated Life Events when I pull all of it on the  search call with no filter and with filter by the id.

I saw in this documentation that the Life Event has an attribute called `launched_to_all` and the attribute description is: "True if the life event is launched to all channels and locales." Is this attribute for this kind of information that I need? All deprecated Life Events are returning with this attribute as "true", so how can I know that the Life Event is in fact deprecated thru the API? Also, I only confirm that these Life Events are not available when I try to get on the ads pannel and this is unacceptable. I didn't find a link at least that we can see which ones are deprecated.

Also, I'd like to take this oppportunity to extand this question to the other audience segments,

If you need any further information, please ask me.

[Google Ads API Forum Advisor]

Hi,

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

I understand that you're encountering an error about audience dimensions. You may check the LifeEventInfo for more information. In order to investigate the issue further, provide us with the complete API logs (request and response with request-id and request header) generated at your end.

If you are using a client library and haven't enabled the logging yet, I would request you to enable logging for the specific client library that you are using. You can refer to the guides Java, .Net, PHP, Python, Ruby or Perl to enable logging at your end. For REST interface requests, you can enable logging via the curl command by using the -i flag.

You can send the details via Reply privately to the author option, or direct private reply to this email.
 

This message is in relation to case "ref:!00D1U01174p.!5004Q02tJKZY:ref" (ADR-00240781)

Thanks,
 

Google Ads API Team

Register for the upcoming workshop: Performance Max and the Google Ads API!