Thanks. I was confusing "verify" and "publish" as the same thing. I see my
misunderstanding now and I will give this a try. Thanks for all of your
help!
On Thursday, December 8, 2022 at 4:48:18 AM UTC-8 adsapi wrote:
> Hello,
>
> The workaround I suggested already should circumvent this limit.
Hello,
The workaround I suggested already should circumvent this limit. I have
suggested that you publish your app (i.e. don't leave it in testing) which will
allow refresh tokens to persist beyond 7 days. Your app will be unverified,
which has some limitations (100 total refresh tokens and a w
For reference:
https://support.google.com/cloud/answer/10311615#zippy=%2Ctesting
" Authorizations by a test user will expire seven days from the time of
consent. "
On Wednesday, December 7, 2022 at 3:17:02 PM UTC-8 Chad Wood wrote:
> Thanks :) I appreciate the help.
> Regarding the refresh toke
Thanks :) I appreciate the help.
Regarding the refresh token expiring every 7 days then. Is there no
workaround on this for me?
On Tuesday, December 6, 2022 at 6:30:38 AM UTC-8 adsapi wrote:
> Hello,
>
> I'm fairly certain that you actually don't need to get your app "approved"
> or "verified"
Hello,
I'm fairly certain that you actually don't need to get your app "approved" or
"verified" in order to use it for your use case. You can't generate more than
100 refresh tokens (but you only need one), and your app will show a warning on
the consent screen (but you're the only one using th
Hello, just checking back on this.
I am fine with submitting the app for approval under the notion that it is
for external use -- even though it is not for external use.
At the end of the day, I only care to make ends meet and keep security
tight.
However, I don't want the review process to d
What about the review process. I assume that, despite my edge-case, I will
still be required to submit for “external app approval”, yes?
On Wed, Nov 30, 2022 at 5:58 PM Chad Wood wrote:
> I see. Correct me if I’m wrong here, but I think I’m starting to
> understand. Practically speaking in this
I see. Correct me if I’m wrong here, but I think I’m starting to
understand. Practically speaking in this case, there really isn’t a
difference between my my app being published versus unpublished, except
that the limitations (of 100users and 7days/refresh token) are lifted. Is
this right? Because
Hello,
Essentially, if you have a Google Workspace setup, then Google can handle some
parts of the authentication for you, and ensure that only users within your
Workspace domain are able to create refresh tokens.
If you aren't using that, then Google does not do any checking of this sort on
o
What is it entailing by "your app will become available to anyone with a
Google account"?
Does Google start hosting the app somewhere? In the Google Pay Market
maybe? I honestly have no idea. How would an external person find my app,
even if accidentally, should I choose to publish?
On Wednesda
Hello,
As for that screenshot, you are still in control of your app. It is a piece of
software you are developing, so you can build whatever feature you want in it.
Namely, if you build some kind of custom login system into your app, and then
only provide logins to authorized users, it's not li
Hello,
Thanks for getting back. Yes that is was I figured sadly. Honestly though,
I'm happy with any solution that makes it so that the refresh token doesn't
need to be retrieved every week. Security implication are a concern though,
which is why I was unsure about publishing the app.
[image: 2
Hello,
I happened to bring this up with one more coworker and I have what I hope may
be some good news.
If you mark your app as external (even though it is technically internal), then
the following restrictions would apply:
You would be limited to 100 total refresh tokens.
Your app would have
Hello,
I've heard back an answer, and unfortunately, it sounds like the system is
working as intended, and your understanding is perfectly accurate. There is no
bug here, and you are in an unfortunate situation that wasn't really accounted
for in the system's design. I know this isn't what you
Thanks, I will keep a watch out until then!
On Friday, November 18, 2022 at 6:10:26 AM UTC-8 adsapi wrote:
> Hello,
>
> Thank you for your detailed response. I'm sharing this information with
> our OAuth team and working with them to try to figure out the best steps to
> proceed. I will let you
Hello,
Thank you for your detailed response. I'm sharing this information with our
OAuth team and working with them to try to figure out the best steps to
proceed. I will let you know when I have any new information to share, or if I
need more information from you.
Regards,
Mike, Google Ads AP
I just provided the client ID via private email. It's worth mentioning that
this is probably not a bug--no error code, as I believe things are
functioning as they were designed to.
But the design does not seem to take my edge-case into consideration. What
do users do in the event that they want
Hello,
The team is going to need some more information to completely debug. Since this
support avenue is not available for external clients, I will have to serve in
the middleman in this exchange. Keep in mind that I don't actually have much
expertise in the OAuth console, so I will generally b
Thanks! I'll stay on the lookout.
On Tuesday, November 15, 2022 at 12:17:21 AM UTC-8 adsapi wrote:
> Hello,
>
> Thank you for confirming. I'm reaching out to some more extended internal
> contacts to try to find a solution here, and will let you know if I learn
> anything, or if I need any furt
Thanks, and you are correct. What you describe is the issue exactly, please
just read over my message stamped for Oct 17, 2022, 3:12:03 PM.
We know why this is happening. The need to get a new refresh token every 7
days IS because the app is in 'testing' and not in 'production'.
See, we can not
Hello,
All I've been able to discover so far is that the requirement for you to get a
new refresh token every week may be associated with you being in some sort of
"testing" mode, rather than a "production" mode. As I'm not terribly familiar
with that interface, I wouldn't know where to look to
+ checking for update
On Wednesday, October 19, 2022 at 9:49:41 AM UTC-7 Chad Wood wrote:
> Thanks Mike. I'll keep an eye on this thread until then.
>
> On Wednesday, October 19, 2022 at 7:04:38 AM UTC-7 adsapi wrote:
>
>> Hello,
>>
>> This case has been escalated to me.
>>
>> I'm looking into th
Thanks Mike. I'll keep an eye on this thread until then.
On Wednesday, October 19, 2022 at 7:04:38 AM UTC-7 adsapi wrote:
> Hello,
>
> This case has been escalated to me.
>
> I'm looking into the best way to proceed here. My team generally doesn't
> have full expertise on the OAuth sign up flow
Hello,
This case has been escalated to me.
I'm looking into the best way to proceed here. My team generally doesn't have
full expertise on the OAuth sign up flow specifically; we focus in the steps
after that, once you're using the API.
But I am trying to find the right person to get in touch
Thanks Darwin,
In the meantime, I had a colleague propose just publishing the app and
making the link to access it super obscure. The idea is that,
theoretically, nobody would ever find it and we could still have our
business needs met. This obviously does not utilize your technology in the
wa
Hi Chad,
Thank you for getting back to us. I hope you are doing well today.
Moving forward to your concern about the refresh token automatically expires
after 7 days and cannot "publish"/"verify". Allow me to raise this issue to my
team for further checking. Rest assured that we will provide
Well, there is another limitation I am now running into and I don't think
this was considered in our conversation.
It's been awhile, so here's the recap/update:
- My company used a gmail to create our accounts for google
applications, like Google Ads. We've also verified ownership of our
Hi Chad,
Hope you are doing fine. This is Carmela from the Google Ads API team as well.
Thank you for getting back to us.
With regards to your concerns, you may see the below items:
"They were able to establish all of these environments and build atop of them
without being required comply with
Thanks Peter, but I'm not sure I'm following.
I would like to address how the companies Google Ads, Firebase, Google
Analytics, and Google Tag Manager account were all made with an email like
mycomp...@gmail.com
They were able to establish all of these environments and build atop of
them withou
Alright, I found this information on Stack:
You should write your code to anticipate the possibility that a granted
token might no longer work. A token might stop working for one of these
reasons: The user has revoked access. The token has not been used for six
months. The user account has exce
Based on our conversion, it appears that I do have the domain specific
requirement of impersonation.
Are we out of luck?
On Friday, October 7, 2022 at 8:37:54 AM UTC-7 Chad Wood wrote:
> Thanks Adsapi,
>
> I guess I am confused then. My company already established a Google Ads
> account using
Thanks Adsapi,
I guess I am confused then. My company already established a Google Ads
account using an @gmail email account. They weren't required to comply with
workspace requirements when they created the Ads account. Same goes for
GTM, GA4, and Firebase. Our presence on these platforms is a
Hi Chad,
Thank you for getting back to us. I work with Peter and allow me to assist you
here. I hope you are doing well today.
Please see my response to your query below.
1.) Alright, it's becoming more clear now.
Correct me if I am wrong, but here's what I think is going on:
* I created t
Well, I just got it working via OAUTH2. Like I said though, it won't make
sense for us to use this method long-term. The program will run
automatically every day, and while it may not take much effort to perform
this one little manual task every day -- Lots of little manual tasks add up
into in
adding to my prior message:
Can I perform this task (Domain Wide Delegation) with the Essentials
Starter Edition of Workspace?
I just signed up for that version. But now I'm at a roadblock. The *main
email**, associated with our Ads account, Firebase, GA4, etc... is an
@gmail domain email. Ho
Alright, it's becoming more clear now.
Correct me if I am wrong, but here's what I think is going on:
* I created the service account for API use to Google Analytics 4, and
I just added the service account to the authorized users as view-only.
* Google Ads REQUIRES that invitees accept t
Hi Chad,
Thank you for your response and for the additional details.
Before I raise this to the rest of our support team, could you also clarify
first the below items :
As per the prerequisites section, were you also able to setup a Google
Workspace domain?
In the first Key point section of th
Hi Chad,
Thank you for the reply. I am also a member of the Google Ads API team and let
me provide support to your concern.
To answer the below question first, yes, I can confirm that your understanding
is correct. But the human interactions that are referring to the other
authentication flow
Sadly, the system we're building will need to operate without human
interaction. Otherwise, I'd love to take the easier option. I understand
that any option for connecting to Google Ads via API (beside service
accounts) would require a user to interact with the application, even if
just to ente
Hi Chad,
Thank you for your reply.
Interactions are sometimes made private due to the sensitive information being
shared. Regarding your issue with the service account authentication, and for
this "User in the cookie is not a valid Ads user." issue, this appears to be
related to the NOT_ADS_US
@adsapi,
While researching this issue, I plugged the error code into google and did
an Exact Match search. Only three results. I played around with my search
and eventually found more results, but there was a trend of responses
asking for replies as private messages. This trend resulted in myse
Hi Chad,
Thank you for reaching us out. I am Sherwin from Google Ads API support team. I
hope that you are doing well today.
Since you mentioned that your implementation is Service account flow, please
check this document if you implemented it properly specially if you met the
prerequisites. I
My error has progressed.
Please tell me someone recognizes this. Does it have to do with me using
Jupyter Notebook?
*``` *
*usage: ipykernel_launcher.py [-h] -c CUSTOMER_ID ipykernel_launcher.py:
error: the following arguments are required: -c/--customer_id *
*An exception has occurred, use %t
Hi David,
Thank you for reaching out to us.
With regard to creating a test account, you can refer to this guide on how you
can create your test account. Kindly note that test accounts can only be
created through the Google Ads API, though they can be viewed in the UI. Let me
know if you need a
44 matches
Mail list logo
