Closed austinkregel closed 9 months ago
Hello,
I'm sorry for the late reply.
Your log shows nothing wrong on membershipLifeSpan
, so either this is a bug or a known undocumented behavior.
Since it's more related on the Google Ads API than this client library, could you please ask on the Google Ads API forum?
Thank you. Knack
@fiboknacky I have posted on the Google Ads API forum here, but I have not received a response.
Is there something I can do to try to get a response from the Google Ads team, or to help them figure out what could be wrong?
Hello,
I'm so sorry for this bad experience! While I'm checking why your case isn't responded to, I found that you're not the only person who experienced this membership_life_span
issue.
It seems other library users also encountered this, so it should be the issue on the API server.
Once I have someone respond to you on the Google Ads API forum, I'll close this issue. Let's keep this open for now.
Thank you so much ππ»
It looks like this is an intended behavior, but never properly documented. Sorry for this inconvenience. I'll use #980 to track the update of the code example.
@fiboknacky I'm not sure I understand, this feature use to work, but now it's apparently not correct.
Was there a change behind the scenes that weren't published? Why is this value ignored for the list now when it wasn't previously?
And like I mentioned, the UI does support editing the value. Would it be possible for the API to have support added for this?
The field is supposed to be set for other types of user list than FlexibleUserList
.
Do you use this type of user list or other types?
We use this type of user list.
We've been using it for years to maintain audiences window of the last 90 days for hundreds of websites.
From what I checked in the codebase, FlexibleUserList
was added in Summer 2022 and the behavior was set to be like this since its release.
So, you still can set this to 90 days in the UI, right?
Yes, I can still set the value to 90 days via the UI.
@fiboknacky My codebase in this area hasn't really changed since 2020 to create our users lists.
In order to ensure I wasn't reporting a bug in my code, I verified before creating this issue that the same issue happens with FlexibleUserLists just the same.
Thanks for more information. I'll sync with the team to see what is happening. There might be some changes in the pipeline that just surfaced this behavior recently (even though it was programmed to be like that a long time ago). By the way, from your code, it looks like you still create a non-flexible user list?
You're welcome! And thank you so much!
We are presently creating a rule based list. The only purpose of the list is to contain visitors to our website in the last 90 days. My team hasn't yet had the bandwidth to upgrade to use a flexible list yet.
I was going to upgrade to use a FlexibleUserList while I work on fixing the membership_life_span, but that's when I discovered this issue π
I see. Thanks for the context and sorry for this inconvenience. That said, I'll keep you posted in this thread.
@austinkregel I'd recommend reading the explanation by my colleague too.
@fiboknacky I'll need to speak with my colleagues on our Digital Advertising team to help determine if this could be an acquitted solution for our clients.
I hope to have an answer by the end of the week next week, if it'll work, I'll leave a note and close the issue. Otherwise, I'll update this thread when I have a more concrete answer π
@fiboknacky I'm having a little difficulty seeing where my issue overlaps with what your colleague is mentioning.
We want to track any visit to our website in the last 90 days. Exclusive logic won't explicitly facilitate that from my understanding. The screenshots I originally provided were representations of the bug in action, not the desired outcome.
This is the desired user list I'm trying to create via the API, but am unable to.
I've gone through and refactored the code I'm working with and it looks like it was upgraded from the old API incorrectly π
I've revised how our app is creating these lists and I've confirmed I can create the needed website inclusion rules. I can confirm that membership_life_span
is not needed to create the needed rules β
Instead of trying to create a UserList with a membership_life_span, I've updated our FlexibleRuleOperandInfo that sets the page url, to also have a lookback_window_days
of 90.
As far as I'm concerned, this issue can be closed in favor of the other ticket π thank you very much for all your assistance with this issue ππ»
Hey, sorry that I missed your last message. I'm glad that you could resolve this now.
And yes, what I meant in the previous reply was that you should use lookback_window_days
to do what you want.
Your client library and Google Ads API versions:
v2.13.2
V13
andV14
Your environment:
Description of the bug:
Using the example provided here in the Remarketing/AddFlexibleRuleUserList example.
Steps to reproduce:
Web page visit in the past 540 days
despite sending 365Attempting to update the membership lifespan via the API will result in no change in Google Ads.
Expected behavior: The Audience Manager should reflect the 365 day lifespan I'm sending, not 540.
Request/Response Logs: Here's the debug logs from my attempt to create a user list with the example
Anything else we should know about your project / environment: The only modification I made to the example was to add a needed
withLoginCustomerId
call to the client used so I could create the list.This behavior seems most unexpected, according to the API docs when left out, the membership lifespan should default to 30 days; but when I remove the lifespan field it is still getting set to 540 in the Google Ads UI.