re `tap-googleads` and the Google API: Has anyone...
# plugins-general
a
re
tap-googleads
and the Google API: Has anyone had any luck getting a long-lived refresh token for the API? The ones I can generate expire in 7 days, if I want a longer lived refresh token, I need to get my app verified, which seems to involve preparing terms of service doc and a youtube video on how my app will be used! All just to access my own org's data for ad reporting. We are an MS shop here so we dont have a proper google workspace, is that part of the issue? Are there any alternate auth pathways available? Google Analytics works fine with a simple set of client credentials in a json file. Edit: I just tried a service account flow, but without G workspace I can't able the necessary delegations for user impersonation. Any tips gratefully received.
v
There's a way to set it up to make that not happen iirc and there hasn't been any changes
There's a doc page somewhere that describes all the reasons a refresh token expires but it's buried in their docs
a
I'm just trying with a 'in production' but 'unverified' app to see if that works, I'll let you know in seven days I guess. By far and away the worst API to actually get set up with, multiple stages of this kind of stuff. I think the issue is there is only one 'google ads' access scope that gives you access to everything. So you can't give reporting access without the ability to create new ad campaigns, hence the level of security behind it. Seems bizarre though.
v
There's a doc that lays it out, I just can't find the link quickly
a
@Andy Carter Hi I ran into the same problem which googleads tap where refresh token expire in 7 days. Have you be able to generate long running refresh token? currently which method you are using to generate refresh token? I am using the google playground and not sure it is the best way to do it.
a
@alo_dring I'm expecting my token will expire any day now unfortunately, it has been 7 days since my original msg. I have my Google CLoud app in production (but not verified), so will see if that works.
I do get a 'back to safety' message when I go through the oauth process, which I would expect as the app is still 'Needs verification'
@alo_dring my refresh token is still working after nearly 2 weeks now so I think the settings above have sorted it