Hello Mike, Thanks for the reply. Shortly after posting my question I did figure out that I needed to create an installed application.
For my Use Case I am going to be tracking GCLID clicks and uploading offline conversions for a client. They have a My Client Center Account that contains many Adwords Accounts, approximately 100 Adwords accounts. When users perform google searches and click on the advertisements, the initial click makes a request to the google ad servers which returns javascript in the response that programmatically creates a link and clicks using auto executing functions. I am sure you know what I'm am talking about. The GCLID is eventually appended to the end of the url of the destination landing page. Once the landing page renders, I will be scraping that CGLID and storing it server side until I receive a notification from external processes that the particular CGLID does indeed qualify for an offline conversion. I will then kick off some server side code that will create the Offline Conversion Feed service and try to upload the offline conversion. One of the confusing questions for me is that of the Click Timestamp. At what point in the request/response life cycle of clicking an advertisement from a google search does the click get tagged with a timestamp? Does it happen at www.googleadservices.com server during the point in time when the second response returns the javascript payload that programmatically creates a link and clicks it or does it happened at the final stage when the googleadservices.com server responds with a location header to redirect to the target landing page that has the gclid appended at the end of the url? Thanks for your help Mark On Monday, March 9, 2015 at 6:50:31 AM UTC-7, Michael Cloonan (AdWords API Team) wrote: > Hello, > > You should use an Installed application rather than a Service account. > This will require a one-time user interaction to get a refresh token, and > from then on your server application can act autonomously reusing that > refresh token. This is the most frequent use case, and the one that most of > our examples use. > > Please see our AdWords-specific OAuth guide > <https://developers.google.com/adwords/api/docs/guides/authentication> for > instructions on how to set this up. > > Regards, > Mike, AdWords API Team > > On Friday, March 6, 2015 at 3:57:43 PM UTC-5, Mark Jones wrote: >> >> Hello <https://developers.google.com/adwords/api/community/>, >> >> I am developing a server side application that needs to upload offline >> conversions. I am trying to figure out if this is possible using >> Service account where our production server can make calls to the Google >> APIs on behalf of my server side application instead of an end-user. >> >> After logging into the Google developers console and navigating to APIs & >> auth --> Credentials, clicking on the Create new Client ID button, we are >> presented with three options: >> >> 1. Web application - Accessed by web browsers over a network. >> 2. Service account - Calls Google APIs on behalf of your application >> instead of an end-user. >> 3. Installed application - Runs on a desktop computer or handheld device >> (like Android or iPhone). >> >> Choosing Web application forces you to create a consent screen, but since >> I need to do all the work server-side without any user intervention the >> consent screen option does not seem to be the correct choice. Seems like a >> Service account would be the best choice, but those accounts to not create >> a ClientID, ClientSecret, and RefreshToken. >> >> All of the code examples point toward Web application where you are >> required to reference a Client ID, Client Secret, and RefreshToken. >> >> Can anyone shed some like on this topic? My goal is to upload offline >> conversions using Java and performing all the work server side. >> >> >> https://developers.google.com/adwords/api/docs/guides/importing-conversions#code_examples >> >> https://developers.google.com/adwords/api/docs/reference/v201409/OfflineConversionFeedService >> https://developers.google.com/accounts/docs/OAuth2?hl=en_US#serviceaccount >> https://developers.google.com/accounts/docs/OAuth2ServiceAccount >> >> -- -- =~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~ Also find us on our blog and Google+: https://googleadsdeveloper.blogspot.com/ https://plus.google.com/+GoogleAdsDevelopers/posts =~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~ You received this message because you are subscribed to the Google Groups "AdWords API Forum" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/adwords-api?hl=en --- You received this message because you are subscribed to the Google Groups "AdWords API Forum" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. Visit this group at http://groups.google.com/group/adwords-api. To view this discussion on the web visit https://groups.google.com/d/msgid/adwords-api/cb3c225b-5b86-4ef9-a248-36774242c97b%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
