Hi Bharani, Many thanks for your response. I had previously found the two links you provided, so I'm glad I'm on the right track. Regarding the credentials in #4, what I meant was: do we need to have a separate security layer on top of our data source, or does the Google Ads API handle that somehow?
For instance, our clients will be using the Google Ads API to bring their call data from our system into Google Ads. But how do we ensure that they are only pulling their own data from our system and not another client's data? Where does that authentication take place: in the Google API (such as with a token), or on our side with a login procedure the client must go through? Thanks again! Paul On Wednesday, July 31, 2019 at 10:26:17 AM UTC-4, adsapiforumadvisor wrote: > > Hello Grim, > > Sure, we will be happy to assist you with this. Please find my response > below: > > *1. Can the Google Ads API enable this functionality "as-is"? Or, do we > need to customize the API? * > Google Ads API has been moved to recently. We recommend to continue > running production systems using the AdWords API. While Google Ads API is > in “beta”, you may use the new API for testing and development work in > preparation for future migration. Please keep in mind that during this > "beta" phase, there may be breaking changes in the Google Ads API. To > import offline call conversions through AdWords API, you may refer to this > guide > <https://developers.google.com/adwords/api/docs/guides/conversion-tracking#importing_call_conversions> > > which will help you get started. > > *2. What data fields can we push to Google Ads? * > #1 should address this concern. > > *3. Does the source data need to reside anywhere in particular (e.g. > within a specific database)? * > This data should be gathered on your end. You may store them in a local > database. This help center article > <https://support.google.com/google-ads/answer/6275629> should be helpful > on how the call conversion tracking works. > > *4. How do the credentials work to ensure each client can only access > their own call data and not any other client's call data? Do we have to > build a security layer on our side to restrict access to the source data?* > Could you please confirm if you are referring to the credentials that are > used to make the API calls? If so, they will be able to access all the > accounts for which the specific user has permissions to. If your concern is > different, please elaborate. > > Let me know if you have any questions. > > Thanks, > Bharani, Google Ads API Team > > ref:_00D1U1174p._5001UEHF1g:ref -- -- =~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~ Also find us on our blog: https://googleadsdeveloper.blogspot.com/ =~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~ You received this message because you are subscribed to the Google Groups "AdWords API and Google Ads 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 and Google Ads API Forum" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/adwords-api/714ec78e-700d-46db-9e01-45660cb31fc1%40googlegroups.com.
