Re: ManagedCustomerService vs CustomerService
Can you use *get()* on *ManagedCustomerService* w/ a selector that just asks for certain *Fields[]* to get all accounts? On Tue, Sep 6, 2016 at 2:47 PM Tejas Manohar <te...@segment.com> wrote: > What's the actual method being used to get account hierarchy? I don't see > it listed here- > https://developers.google.com/adwords/api/docs/reference/v201607/ManagedCustomerService > > On Tue, Sep 6, 2016 at 2:43 PM 'Shwetha Vastrad (AdWords API Team)' via > AdWords API Forum <adwords-api@googlegroups.com> wrote: > >> Hi Tejas, >> >> I would recommend that you use ManagedCustomerService >> <https://developers.google.com/adwords/api/docs/reference/v201607/ManagedCustomerService> >> to >> get all the accounts accessible by the user authenticated in the request. >> You could use the GetAccountHierarchy >> <https://github.com/googleads/googleads-java-lib/blob/master/examples/adwords_axis/src/main/java/adwords/axis/v201607/accountmanagement/GetAccountHierarchy.java> >> Java >> example to get the account hierarchy under the current account. Example >> code in other languages is available here >> <https://developers.google.com/adwords/api/docs/clientlibraries>. >> >> Regards, >> Shwetha, AdWords API Team. >> >> -- >> -- >> =~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~ >> 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 adwords-api@googlegroups.com >> To unsubscribe from this group, send email to >> adwords-api+unsubscr...@googlegroups.com >> 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 a topic in the >> Google Groups "AdWords API Forum" group. >> To unsubscribe from this topic, visit >> https://groups.google.com/d/topic/adwords-api/uhbsu9rbTIM/unsubscribe. >> To unsubscribe from this group and all its topics, send an email to >> adwords-api+unsubscr...@googlegroups.com. >> Visit this group at https://groups.google.com/group/adwords-api. >> To view this discussion on the web visit >> https://groups.google.com/d/msgid/adwords-api/55da0517-d25e-4c61-8699-7add7dae1eca%40googlegroups.com >> <https://groups.google.com/d/msgid/adwords-api/55da0517-d25e-4c61-8699-7add7dae1eca%40googlegroups.com?utm_medium=email_source=footer> >> . >> For more options, visit https://groups.google.com/d/optout. >> > -- > > Best regards, > > Tejas Manohar > -- Best regards, Tejas Manohar -- -- =~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~ 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 adwords-api@googlegroups.com To unsubscribe from this group, send email to adwords-api+unsubscr...@googlegroups.com 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 adwords-api+unsubscr...@googlegroups.com. Visit this group at https://groups.google.com/group/adwords-api. To view this discussion on the web visit https://groups.google.com/d/msgid/adwords-api/CAJU0XY5FGQSf04MDN44vibdP9d0Cpsr79Xfhy79uFC-Fm1pUeQ%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
Re: ManagedCustomerService vs CustomerService
What's the actual method being used to get account hierarchy? I don't see it listed here- https://developers.google.com/adwords/api/docs/reference/v201607/ManagedCustomerService On Tue, Sep 6, 2016 at 2:43 PM 'Shwetha Vastrad (AdWords API Team)' via AdWords API Forum <adwords-api@googlegroups.com> wrote: > Hi Tejas, > > I would recommend that you use ManagedCustomerService > <https://developers.google.com/adwords/api/docs/reference/v201607/ManagedCustomerService> > to > get all the accounts accessible by the user authenticated in the request. > You could use the GetAccountHierarchy > <https://github.com/googleads/googleads-java-lib/blob/master/examples/adwords_axis/src/main/java/adwords/axis/v201607/accountmanagement/GetAccountHierarchy.java> > Java > example to get the account hierarchy under the current account. Example > code in other languages is available here > <https://developers.google.com/adwords/api/docs/clientlibraries>. > > Regards, > Shwetha, AdWords API Team. > > -- > -- > =~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~ > 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 adwords-api@googlegroups.com > To unsubscribe from this group, send email to > adwords-api+unsubscr...@googlegroups.com > 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 a topic in the > Google Groups "AdWords API Forum" group. > To unsubscribe from this topic, visit > https://groups.google.com/d/topic/adwords-api/uhbsu9rbTIM/unsubscribe. > To unsubscribe from this group and all its topics, send an email to > adwords-api+unsubscr...@googlegroups.com. > Visit this group at https://groups.google.com/group/adwords-api. > To view this discussion on the web visit > https://groups.google.com/d/msgid/adwords-api/55da0517-d25e-4c61-8699-7add7dae1eca%40googlegroups.com > <https://groups.google.com/d/msgid/adwords-api/55da0517-d25e-4c61-8699-7add7dae1eca%40googlegroups.com?utm_medium=email_source=footer> > . > For more options, visit https://groups.google.com/d/optout. > -- Best regards, Tejas Manohar -- -- =~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~ 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 adwords-api@googlegroups.com To unsubscribe from this group, send email to adwords-api+unsubscr...@googlegroups.com 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 adwords-api+unsubscr...@googlegroups.com. Visit this group at https://groups.google.com/group/adwords-api. To view this discussion on the web visit https://groups.google.com/d/msgid/adwords-api/CAJU0XY4nu7VJ1GQayDqfDAVhVXTVwV_WvdjyoyZfGs9S-eQcEA%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
Re: Suggestion: Go library
Thanks! Right now, we've been using Python internally, but it would be nice to be able to use the same technology throughout (but also seems like a lot of work to maintain an external client). On Tue, Aug 30, 2016 at 2:23 PM 'Vishal Vinayak (Adwords API Team)' via AdWords API Forum <adwords-api@googlegroups.com> wrote: > Hi Tejas, > > Appreciate your suggestion. I have conveyed the same to the team. > > Regards, > Vishal, AdWords API Team > > -- > -- > =~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~ > 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 adwords-api@googlegroups.com > To unsubscribe from this group, send email to > adwords-api+unsubscr...@googlegroups.com > 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 a topic in the > Google Groups "AdWords API Forum" group. > To unsubscribe from this topic, visit > https://groups.google.com/d/topic/adwords-api/qNuy68tIBx0/unsubscribe. > To unsubscribe from this group and all its topics, send an email to > adwords-api+unsubscr...@googlegroups.com. > Visit this group at https://groups.google.com/group/adwords-api. > To view this discussion on the web visit > https://groups.google.com/d/msgid/adwords-api/200591ad-bcdf-4562-966c-b7ece3eb6d8e%40googlegroups.com > <https://groups.google.com/d/msgid/adwords-api/200591ad-bcdf-4562-966c-b7ece3eb6d8e%40googlegroups.com?utm_medium=email_source=footer> > . > For more options, visit https://groups.google.com/d/optout. > -- Best regards, Tejas Manohar -- -- =~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~ 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 adwords-api@googlegroups.com To unsubscribe from this group, send email to adwords-api+unsubscr...@googlegroups.com 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 adwords-api+unsubscr...@googlegroups.com. Visit this group at https://groups.google.com/group/adwords-api. To view this discussion on the web visit https://groups.google.com/d/msgid/adwords-api/CAJU0XY7agXbF-Lr9wcxQj0nRYV_BV2ctNm9sh1_-9E2qGhzToQ%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
Re: AdWords API Python - Internal Error or Parsing Error
Ah yes, i tried utf8 yesterday and t worked. Thanks a lot Mark! :) On Fri, Aug 26, 2016 at 10:55 AM Mark Saniscalchi < msanis88.adxbuyerapiadvi...@gmail.com> wrote: > Hello Tejas, > > The googleads library is compatible with Python 3, as indicated by the > fact that the report data was successfully retrieved. However, if you're > decoding the report output (containing non-ascii data) to ascii at some > point, that will raise an Exception. Often times, the encoding will default > to the system encoding, which could potentially be something other than > utf-8. If an option to set the encoding is offered, try setting it to utf-8. > > Regards, > Mark > > > On Thursday, August 25, 2016 at 5:07:01 PM UTC-4, Tejas Manohar wrote: > >> Moreover, looks like TextIOWrapper accepts an encoding option... >> https://docs.python.org/2/library/io.html#io.TextIOWrapper - what would >> you suggest here (considering what sort of data the googleadwords lib / >> AdWords API is returning)? >> >> On Thu, Aug 25, 2016 at 2:05 PM Tejas Manohar <te...@segment.com> wrote: >> > *from csv import DictReader as parse_csv* >>> *from io import TextIOWrapper* >>> >>> Gotcha. Those are both standard library methods. Do you have an >>> alternative way you'd suggest decoding in a Python 3 environment (given the >>> Unicode changes)? I'd be happy to migrate. If really needed, I can move >>> this service to Python 2 (fixing this error is top priority)... but that >>> may require some widespread changes (though small ones). Thanks again! >>> >>> (Sorry if I've asked a stupid question. Python frankly isn't my strong >>> point. Used it because maintaining an AdWords SOAP wrapper in Go or Node is >>> quite a burden.) >>> >> On Thu, Aug 25, 2016 at 1:58 PM Mark Saniscalchi < >>> msanis88.adxb...@gmail.com> wrote: >>> >> Hello Tejas, >>>> >>>> Based on the stacktrace, I can see that the root cause is that you're >>>> decoding with ASCII specified as the encoding. That will produce a >>>> UnicodeEncode error if non-ASCII text appears in the reporting data. It >>>> appears that one of the libraries you're using is probably the culprit >>>> here, but it's hard to tell which. I'm pretty confident this isn't caused >>>> by the googleads library though. I suggest taking a closer look at >>>> TextIOWrapper and the parse_csv method. >>>> >>>> Regards, >>>> Mark >>>> >>>> >>>> On Thursday, August 25, 2016 at 4:24:43 PM UTC-4, Tejas Manohar wrote: >>>> >>>>> Hey Mark, >>>>> >>>>> The issue is back and is not being solved by retries for our customer. >>>>> Here's >>>>> code + logs- >>>>> https://gist.github.com/tejasmanohar/24f15ddb830f8bc611e9e50fdf56f688. >>>>> Let me know what other information I can provide to help you debug this. >>>>> It's currently blocking syncs with our beta AdWords Source at Segment ( >>>>> https://segment.com/sources) for a subset of customers (launch date >>>>> next week). >>>>> >>>>> On Tue, Aug 23, 2016 at 4:57 PM Tejas Manohar <te...@segment.com> >>>>> wrote: >>>>> >>>> Got it. We have not seen the error today. I'll follow-up if it comes >>>>>> back. Thanks! >>>>>> >>>>>> On Tue, Aug 23, 2016 at 4:21 PM Mark Saniscalchi < >>>>>> msanis88.adxb...@gmail.com> wrote: >>>>>> >>>>> Hello Tejas, >>>>>>> >>>>>>> The stacktrace you linked to actually seems indicative of a separate >>>>>>> issue, I suspect you're seeing this issue >>>>>>> <https://groups.google.com/forum/#!topic/adwords-api/BXnAVhYe538> >>>>>>> instead. I can tell because the UnicodeDecodeError you're receiving >>>>>>> indicates that you're likely receiving something that was gzipped, but >>>>>>> your >>>>>>> report definition indicates that you set the format to CSV. >>>>>>> >>>>>>> That said, I can't verify whether the original issue is still in >>>>>>> effect. If you're still experiencing issues with new reports, can you >>>>>>> send >>>>>>> another report definition / stacktrace? >>>>>>> >>>>
Re: AdWords API Python - Internal Error or Parsing Error
Moreover, looks like TextIOWrapper accepts an encoding option... https://docs.python.org/2/library/io.html#io.TextIOWrapper - what would you suggest here (considering what sort of data the googleadwords lib / AdWords API is returning)? On Thu, Aug 25, 2016 at 2:05 PM Tejas Manohar <te...@segment.com> wrote: > *from csv import DictReader as parse_csv* > *from io import TextIOWrapper* > > Gotcha. Those are both standard library methods. Do you have an > alternative way you'd suggest decoding in a Python 3 environment (given the > Unicode changes)? I'd be happy to migrate. If really needed, I can move > this service to Python 2 (fixing this error is top priority)... but that > may require some widespread changes (though small ones). Thanks again! > > (Sorry if I've asked a stupid question. Python frankly isn't my strong > point. Used it because maintaining an AdWords SOAP wrapper in Go or Node is > quite a burden.) > > On Thu, Aug 25, 2016 at 1:58 PM Mark Saniscalchi < > msanis88.adxbuyerapiadvi...@gmail.com> wrote: > >> Hello Tejas, >> >> Based on the stacktrace, I can see that the root cause is that you're >> decoding with ASCII specified as the encoding. That will produce a >> UnicodeEncode error if non-ASCII text appears in the reporting data. It >> appears that one of the libraries you're using is probably the culprit >> here, but it's hard to tell which. I'm pretty confident this isn't caused >> by the googleads library though. I suggest taking a closer look at >> TextIOWrapper and the parse_csv method. >> >> Regards, >> Mark >> >> >> On Thursday, August 25, 2016 at 4:24:43 PM UTC-4, Tejas Manohar wrote: >> >>> Hey Mark, >>> >>> The issue is back and is not being solved by retries for our customer. >>> Here's >>> code + logs- >>> https://gist.github.com/tejasmanohar/24f15ddb830f8bc611e9e50fdf56f688. >>> Let me know what other information I can provide to help you debug this. >>> It's currently blocking syncs with our beta AdWords Source at Segment ( >>> https://segment.com/sources) for a subset of customers (launch date >>> next week). >>> >>> On Tue, Aug 23, 2016 at 4:57 PM Tejas Manohar <te...@segment.com> wrote: >>> >> Got it. We have not seen the error today. I'll follow-up if it comes >>>> back. Thanks! >>>> >>>> On Tue, Aug 23, 2016 at 4:21 PM Mark Saniscalchi < >>>> msanis88.adxb...@gmail.com> wrote: >>>> >>> Hello Tejas, >>>>> >>>>> The stacktrace you linked to actually seems indicative of a separate >>>>> issue, I suspect you're seeing this issue >>>>> <https://groups.google.com/forum/#!topic/adwords-api/BXnAVhYe538> >>>>> instead. I can tell because the UnicodeDecodeError you're receiving >>>>> indicates that you're likely receiving something that was gzipped, but >>>>> your >>>>> report definition indicates that you set the format to CSV. >>>>> >>>>> That said, I can't verify whether the original issue is still in >>>>> effect. If you're still experiencing issues with new reports, can you send >>>>> another report definition / stacktrace? >>>>> >>>>> Regards, >>>>> Mark >>>>> >>>>> On Friday, August 19, 2016 at 10:12:39 PM UTC-4, Tejas Manohar wrote: >>>>> >>>>>> Hey Mark, >>>>>> >>>>>> Sorry for the delay here. Here's report definition + error in logs- >>>>>> https://gist.github.com/tejasmanohar/fd539957f8653a6c8375cd3b5a2cd7f5. >>>>>> How can I determine the locale of customers? Btw, this error happens on >>>>>> many reports for this customer, not just one, so I can provide more >>>>>> examples, and retries are solving the problem for now, but it slows >>>>>> everything down. >>>>>> >>>>>> Let me know what else I can provide to help. Thanks! >>>>>> >>>>>> On Fri, Jul 29, 2016 at 3:13 PM Tejas Manohar <te...@segment.com> >>>>>> wrote: >>>>>> >>>>> Hey Mark, >>>>>>> >>>>>>> Thanks! I will get all this information to you on Monday. >>>>>>> >>>>>>> On Fri, Jul 29, 2016 at 3:05 PM Mark Saniscalchi < >>>>>>> msanis88.adxb...@gmail.com> wrote: >>>>>>> >>>>>
Re: AdWords API Python - Internal Error or Parsing Error
*from csv import DictReader as parse_csv* *from io import TextIOWrapper* Gotcha. Those are both standard library methods. Do you have an alternative way you'd suggest decoding in a Python 3 environment (given the Unicode changes)? I'd be happy to migrate. If really needed, I can move this service to Python 2 (fixing this error is top priority)... but that may require some widespread changes (though small ones). Thanks again! (Sorry if I've asked a stupid question. Python frankly isn't my strong point. Used it because maintaining an AdWords SOAP wrapper in Go or Node is quite a burden.) On Thu, Aug 25, 2016 at 1:58 PM Mark Saniscalchi < msanis88.adxbuyerapiadvi...@gmail.com> wrote: > Hello Tejas, > > Based on the stacktrace, I can see that the root cause is that you're > decoding with ASCII specified as the encoding. That will produce a > UnicodeEncode error if non-ASCII text appears in the reporting data. It > appears that one of the libraries you're using is probably the culprit > here, but it's hard to tell which. I'm pretty confident this isn't caused > by the googleads library though. I suggest taking a closer look at > TextIOWrapper and the parse_csv method. > > Regards, > Mark > > > On Thursday, August 25, 2016 at 4:24:43 PM UTC-4, Tejas Manohar wrote: > >> Hey Mark, >> >> The issue is back and is not being solved by retries for our customer. Here's >> code + logs- >> https://gist.github.com/tejasmanohar/24f15ddb830f8bc611e9e50fdf56f688. >> Let me know what other information I can provide to help you debug this. >> It's currently blocking syncs with our beta AdWords Source at Segment ( >> https://segment.com/sources) for a subset of customers (launch date next >> week). >> >> On Tue, Aug 23, 2016 at 4:57 PM Tejas Manohar <te...@segment.com> wrote: >> > Got it. We have not seen the error today. I'll follow-up if it comes back. >>> Thanks! >>> >>> On Tue, Aug 23, 2016 at 4:21 PM Mark Saniscalchi < >>> msanis88.adxb...@gmail.com> wrote: >>> >> Hello Tejas, >>>> >>>> The stacktrace you linked to actually seems indicative of a separate >>>> issue, I suspect you're seeing this issue >>>> <https://groups.google.com/forum/#!topic/adwords-api/BXnAVhYe538> >>>> instead. I can tell because the UnicodeDecodeError you're receiving >>>> indicates that you're likely receiving something that was gzipped, but your >>>> report definition indicates that you set the format to CSV. >>>> >>>> That said, I can't verify whether the original issue is still in >>>> effect. If you're still experiencing issues with new reports, can you send >>>> another report definition / stacktrace? >>>> >>>> Regards, >>>> Mark >>>> >>>> On Friday, August 19, 2016 at 10:12:39 PM UTC-4, Tejas Manohar wrote: >>>> >>>>> Hey Mark, >>>>> >>>>> Sorry for the delay here. Here's report definition + error in logs- >>>>> https://gist.github.com/tejasmanohar/fd539957f8653a6c8375cd3b5a2cd7f5. >>>>> How can I determine the locale of customers? Btw, this error happens on >>>>> many reports for this customer, not just one, so I can provide more >>>>> examples, and retries are solving the problem for now, but it slows >>>>> everything down. >>>>> >>>>> Let me know what else I can provide to help. Thanks! >>>>> >>>>> On Fri, Jul 29, 2016 at 3:13 PM Tejas Manohar <te...@segment.com> >>>>> wrote: >>>>> >>>> Hey Mark, >>>>>> >>>>>> Thanks! I will get all this information to you on Monday. >>>>>> >>>>>> On Fri, Jul 29, 2016 at 3:05 PM Mark Saniscalchi < >>>>>> msanis88.adxb...@gmail.com> wrote: >>>>>> >>>>> Hello Tejas, >>>>>>> >>>>>>> I'm the owner of the Python Client Library, and am taking a look at >>>>>>> this issue. It's difficult to say for certain whether this is a client >>>>>>> or >>>>>>> server-based issue because the snippet and stacktrace are incomplete, >>>>>>> but >>>>>>> I'm leaning towards this being a server issue or a mixture of both. >>>>>>> The AdWordsReportBadRequestError is raised when a reportDownloadError is >>>>>>> detected in the response--this is usually the result of bad input. >>>>&
Re: AdWords API Python - Internal Error or Parsing Error
Hey Mark, The issue is back and is not being solved by retries for our customer. Here's code + logs- https://gist.github.com/tejasmanohar/24f15ddb830f8bc611e9e50fdf56f688. Let me know what other information I can provide to help you debug this. It's currently blocking syncs with our beta AdWords Source at Segment ( https://segment.com/sources) for a subset of customers (launch date next week). On Tue, Aug 23, 2016 at 4:57 PM Tejas Manohar <te...@segment.com> wrote: > Got it. We have not seen the error today. I'll follow-up if it comes back. > Thanks! > > On Tue, Aug 23, 2016 at 4:21 PM Mark Saniscalchi < > msanis88.adxbuyerapiadvi...@gmail.com> wrote: > >> Hello Tejas, >> >> The stacktrace you linked to actually seems indicative of a separate >> issue, I suspect you're seeing this issue >> <https://groups.google.com/forum/#!topic/adwords-api/BXnAVhYe538> >> instead. I can tell because the UnicodeDecodeError you're receiving >> indicates that you're likely receiving something that was gzipped, but your >> report definition indicates that you set the format to CSV. >> >> That said, I can't verify whether the original issue is still in effect. >> If you're still experiencing issues with new reports, can you send another >> report definition / stacktrace? >> >> Regards, >> Mark >> >> On Friday, August 19, 2016 at 10:12:39 PM UTC-4, Tejas Manohar wrote: >> >>> Hey Mark, >>> >>> Sorry for the delay here. Here's report definition + error in logs- >>> https://gist.github.com/tejasmanohar/fd539957f8653a6c8375cd3b5a2cd7f5. >>> How can I determine the locale of customers? Btw, this error happens on >>> many reports for this customer, not just one, so I can provide more >>> examples, and retries are solving the problem for now, but it slows >>> everything down. >>> >>> Let me know what else I can provide to help. Thanks! >>> >>> On Fri, Jul 29, 2016 at 3:13 PM Tejas Manohar <te...@segment.com> wrote: >>> >> Hey Mark, >>>> >>>> Thanks! I will get all this information to you on Monday. >>>> >>>> On Fri, Jul 29, 2016 at 3:05 PM Mark Saniscalchi < >>>> msanis88.adxb...@gmail.com> wrote: >>>> >>> Hello Tejas, >>>>> >>>>> I'm the owner of the Python Client Library, and am taking a look at >>>>> this issue. It's difficult to say for certain whether this is a client or >>>>> server-based issue because the snippet and stacktrace are incomplete, but >>>>> I'm leaning towards this being a server issue or a mixture of both. >>>>> The AdWordsReportBadRequestError is raised when a reportDownloadError is >>>>> detected in the response--this is usually the result of bad input. >>>>> >>>>> The UnicodeDecodeError is a bit of a mystery at the moment, as I can't >>>>> replicate it (also in Python 3) with a data source known to contain utf-8. >>>>> The fact that it seems to be expecting ascii input is telling, and I'm >>>>> wondering if something else in your program would be expecting ascii >>>>> input? >>>>> It might be the TextIOWrapper, which will default to the system encoding >>>>> (which may be ascii in your case). >>>>> >>>>> In short, I can't specifically point out what went wrong here because >>>>> I don't have the full picture. I need to at least see what the report >>>>> definition contains in order to attempt to reproduce >>>>> theAdWordsReportBadRequestError; it'd also be helpful if I knew what >>>>> locale >>>>> settings are. >>>>> >>>>> Regards, >>>>> Mark >>>>> >>>>> On Tuesday, July 26, 2016 at 9:18:17 PM UTC-4, Tejas Manohar wrote: >>>>> >>>>>> Hey Shwetha, >>>>>> >>>>>> I've confirmed that this issue is resolved by retrying, but it >>>>>> happens very consistently. Since it's resolved by retrying and I'm using >>>>>> codecs#getreader which knows how to handle Python unicode in both v2 and >>>>>> v3, I really believe this issue is due to malformed data sent back from >>>>>> the >>>>>> API as a result of an error. Let me know what more info I could provide >>>>>> to >>>>>> help. Thanks! >>>>>> >>>>>> On Wed, Jul 20, 2016 at
Re: Get Ad Performance Report for Lifetime of Ad
Alrighty. I'll write a process to handle this, but it'd be great if AWQL gets SORT someday :D On Tue, Aug 23, 2016 at 7:11 AM 'Anthony Madrigal' via AdWords API Forum < adwords-api@googlegroups.com> wrote: > Hi, > > There is a preset for that date range. It is called ALL_TIME > <https://developers.google.com/adwords/api/docs/guides/reporting#date_ranges>. > However, this date range cannot be used when using AWQL for reports > <https://developers.google.com/adwords/api/docs/guides/awql#using_awql_with_reports>. > There have been instances where data is not sorted chronologically > properly. Unfortunately, the only way to enforce this would be to sort it > after you run the report. > > Regards, > Anthony > AdWords API Team > > -- > -- > =~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~ > 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 adwords-api@googlegroups.com > To unsubscribe from this group, send email to > adwords-api+unsubscr...@googlegroups.com > 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 a topic in the > Google Groups "AdWords API Forum" group. > To unsubscribe from this topic, visit > https://groups.google.com/d/topic/adwords-api/QTMNdaamOvY/unsubscribe. > To unsubscribe from this group and all its topics, send an email to > adwords-api+unsubscr...@googlegroups.com. > Visit this group at https://groups.google.com/group/adwords-api. > To view this discussion on the web visit > https://groups.google.com/d/msgid/adwords-api/60d6c6e4-ff06-468d-9759-1874b7f66cd2%40googlegroups.com > <https://groups.google.com/d/msgid/adwords-api/60d6c6e4-ff06-468d-9759-1874b7f66cd2%40googlegroups.com?utm_medium=email_source=footer> > . > For more options, visit https://groups.google.com/d/optout. > -- Best regards, Tejas Manohar -- -- =~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~ 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 adwords-api@googlegroups.com To unsubscribe from this group, send email to adwords-api+unsubscr...@googlegroups.com 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 adwords-api+unsubscr...@googlegroups.com. Visit this group at https://groups.google.com/group/adwords-api. To view this discussion on the web visit https://groups.google.com/d/msgid/adwords-api/CAJU0XY6GPhpQ5RYaY%3D%2BAe085%3DyCwf%3D%3DVjVRvBKMt4T_Nmjp5Nw%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
Re: AdWords API Python - Internal Error or Parsing Error
Got it. We have not seen the error today. I'll follow-up if it comes back. Thanks! On Tue, Aug 23, 2016 at 4:21 PM Mark Saniscalchi < msanis88.adxbuyerapiadvi...@gmail.com> wrote: > Hello Tejas, > > The stacktrace you linked to actually seems indicative of a separate > issue, I suspect you're seeing this issue > <https://groups.google.com/forum/#!topic/adwords-api/BXnAVhYe538> > instead. I can tell because the UnicodeDecodeError you're receiving > indicates that you're likely receiving something that was gzipped, but your > report definition indicates that you set the format to CSV. > > That said, I can't verify whether the original issue is still in effect. > If you're still experiencing issues with new reports, can you send another > report definition / stacktrace? > > Regards, > Mark > > On Friday, August 19, 2016 at 10:12:39 PM UTC-4, Tejas Manohar wrote: > >> Hey Mark, >> >> Sorry for the delay here. Here's report definition + error in logs- >> https://gist.github.com/tejasmanohar/fd539957f8653a6c8375cd3b5a2cd7f5. >> How can I determine the locale of customers? Btw, this error happens on >> many reports for this customer, not just one, so I can provide more >> examples, and retries are solving the problem for now, but it slows >> everything down. >> >> Let me know what else I can provide to help. Thanks! >> >> On Fri, Jul 29, 2016 at 3:13 PM Tejas Manohar <te...@segment.com> wrote: >> > Hey Mark, >>> >>> Thanks! I will get all this information to you on Monday. >>> >>> On Fri, Jul 29, 2016 at 3:05 PM Mark Saniscalchi < >>> msanis88.adxb...@gmail.com> wrote: >>> >> Hello Tejas, >>>> >>>> I'm the owner of the Python Client Library, and am taking a look at >>>> this issue. It's difficult to say for certain whether this is a client or >>>> server-based issue because the snippet and stacktrace are incomplete, but >>>> I'm leaning towards this being a server issue or a mixture of both. >>>> The AdWordsReportBadRequestError is raised when a reportDownloadError is >>>> detected in the response--this is usually the result of bad input. >>>> >>>> The UnicodeDecodeError is a bit of a mystery at the moment, as I can't >>>> replicate it (also in Python 3) with a data source known to contain utf-8. >>>> The fact that it seems to be expecting ascii input is telling, and I'm >>>> wondering if something else in your program would be expecting ascii input? >>>> It might be the TextIOWrapper, which will default to the system encoding >>>> (which may be ascii in your case). >>>> >>>> In short, I can't specifically point out what went wrong here because I >>>> don't have the full picture. I need to at least see what the report >>>> definition contains in order to attempt to reproduce >>>> theAdWordsReportBadRequestError; it'd also be helpful if I knew what locale >>>> settings are. >>>> >>>> Regards, >>>> Mark >>>> >>>> On Tuesday, July 26, 2016 at 9:18:17 PM UTC-4, Tejas Manohar wrote: >>>> >>>>> Hey Shwetha, >>>>> >>>>> I've confirmed that this issue is resolved by retrying, but it happens >>>>> very consistently. Since it's resolved by retrying and I'm using >>>>> codecs#getreader which knows how to handle Python unicode in both v2 and >>>>> v3, I really believe this issue is due to malformed data sent back from >>>>> the >>>>> API as a result of an error. Let me know what more info I could provide to >>>>> help. Thanks! >>>>> >>>>> On Wed, Jul 20, 2016 at 1:56 PM 'Shwetha Vastrad (AdWords API Team)' >>>>> via AdWords API Forum <adwor...@googlegroups.com> wrote: >>>>> >>>> Hi Tejas, >>>>>> >>>>>> This issue is related to how Python handles data streams and not >>>>>> specific to AdWords API. I suggest that you post your query in the >>>>>> AdWords >>>>>> API Python library repository >>>>>> <https://github.com/googleads/googleads-python-lib> as they are >>>>>> better equipped to help you out. >>>>>> >>>>>> Regards, >>>>>> Shwetha, AdWords API Team. >>>>>> >>>>>> -- >>>>>> -- >>>>>> =~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~
Re: AdWords API Python - Internal Error or Parsing Error
Hey Mark, Sorry for the delay here. Here's report definition + error in logs- https://gist.github.com/tejasmanohar/fd539957f8653a6c8375cd3b5a2cd7f5. How can I determine the locale of customers? Btw, this error happens on many reports for this customer, not just one, so I can provide more examples, and retries are solving the problem for now, but it slows everything down. Let me know what else I can provide to help. Thanks! On Fri, Jul 29, 2016 at 3:13 PM Tejas Manohar <te...@segment.com> wrote: > Hey Mark, > > Thanks! I will get all this information to you on Monday. > > On Fri, Jul 29, 2016 at 3:05 PM Mark Saniscalchi < > msanis88.adxbuyerapiadvi...@gmail.com> wrote: > >> Hello Tejas, >> >> I'm the owner of the Python Client Library, and am taking a look at this >> issue. It's difficult to say for certain whether this is a client or >> server-based issue because the snippet and stacktrace are incomplete, but >> I'm leaning towards this being a server issue or a mixture of both. >> The AdWordsReportBadRequestError is raised when a reportDownloadError is >> detected in the response--this is usually the result of bad input. >> >> The UnicodeDecodeError is a bit of a mystery at the moment, as I can't >> replicate it (also in Python 3) with a data source known to contain utf-8. >> The fact that it seems to be expecting ascii input is telling, and I'm >> wondering if something else in your program would be expecting ascii input? >> It might be the TextIOWrapper, which will default to the system encoding >> (which may be ascii in your case). >> >> In short, I can't specifically point out what went wrong here because I >> don't have the full picture. I need to at least see what the report >> definition contains in order to attempt to reproduce >> theAdWordsReportBadRequestError; it'd also be helpful if I knew what locale >> settings are. >> >> Regards, >> Mark >> >> On Tuesday, July 26, 2016 at 9:18:17 PM UTC-4, Tejas Manohar wrote: >> >>> Hey Shwetha, >>> >>> I've confirmed that this issue is resolved by retrying, but it happens >>> very consistently. Since it's resolved by retrying and I'm using >>> codecs#getreader which knows how to handle Python unicode in both v2 and >>> v3, I really believe this issue is due to malformed data sent back from the >>> API as a result of an error. Let me know what more info I could provide to >>> help. Thanks! >>> >>> On Wed, Jul 20, 2016 at 1:56 PM 'Shwetha Vastrad (AdWords API Team)' via >>> AdWords API Forum <adwor...@googlegroups.com> wrote: >>> >> Hi Tejas, >>>> >>>> This issue is related to how Python handles data streams and not >>>> specific to AdWords API. I suggest that you post your query in the AdWords >>>> API Python library repository >>>> <https://github.com/googleads/googleads-python-lib> as they are better >>>> equipped to help you out. >>>> >>>> Regards, >>>> Shwetha, AdWords API Team. >>>> >>>> -- >>>> -- >>>> =~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~ >>>> 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 adwor...@googlegroups.com >>> >>> >>>> To unsubscribe from this group, send email to >>>> >>> adwords-api...@googlegroups.com >>> >>> >>>> 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 a topic in the >>>> Google Groups "AdWords API Forum" group. >>>> To unsubscribe from this topic, visit >>>> https://groups.google.com/d/topic/adwords-api/Jmbqifyr_Ro/unsubscribe. >>>> >>> To unsubscribe from this group and all its topics, send an email to >>>> adwords-api...@googlegroups.com. >>> >>> >>>> Visit this group at https://groups.google.com/group/adwords-api. >>>> To view this discussion on the web visit >>>> https://groups.google.com/d/msgid/adwords-api/780b5d92-b91a-41d5-9467-246325408472%40googlegroups.com &
Re: AdWords API Python - Internal Error or Parsing Error
Hey Mark, Thanks! I will get all this information to you on Monday. On Fri, Jul 29, 2016 at 3:05 PM Mark Saniscalchi < msanis88.adxbuyerapiadvi...@gmail.com> wrote: > Hello Tejas, > > I'm the owner of the Python Client Library, and am taking a look at this > issue. It's difficult to say for certain whether this is a client or > server-based issue because the snippet and stacktrace are incomplete, but > I'm leaning towards this being a server issue or a mixture of both. > The AdWordsReportBadRequestError is raised when a reportDownloadError is > detected in the response--this is usually the result of bad input. > > The UnicodeDecodeError is a bit of a mystery at the moment, as I can't > replicate it (also in Python 3) with a data source known to contain utf-8. > The fact that it seems to be expecting ascii input is telling, and I'm > wondering if something else in your program would be expecting ascii input? > It might be the TextIOWrapper, which will default to the system encoding > (which may be ascii in your case). > > In short, I can't specifically point out what went wrong here because I > don't have the full picture. I need to at least see what the report > definition contains in order to attempt to reproduce > theAdWordsReportBadRequestError; it'd also be helpful if I knew what locale > settings are. > > Regards, > Mark > > On Tuesday, July 26, 2016 at 9:18:17 PM UTC-4, Tejas Manohar wrote: > >> Hey Shwetha, >> >> I've confirmed that this issue is resolved by retrying, but it happens >> very consistently. Since it's resolved by retrying and I'm using >> codecs#getreader which knows how to handle Python unicode in both v2 and >> v3, I really believe this issue is due to malformed data sent back from the >> API as a result of an error. Let me know what more info I could provide to >> help. Thanks! >> >> On Wed, Jul 20, 2016 at 1:56 PM 'Shwetha Vastrad (AdWords API Team)' via >> AdWords API Forum <adwor...@googlegroups.com> wrote: >> > Hi Tejas, >>> >>> This issue is related to how Python handles data streams and not >>> specific to AdWords API. I suggest that you post your query in the AdWords >>> API Python library repository >>> <https://github.com/googleads/googleads-python-lib> as they are better >>> equipped to help you out. >>> >>> Regards, >>> Shwetha, AdWords API Team. >>> >>> -- >>> -- >>> =~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~ >>> 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 adwor...@googlegroups.com >> >> >>> To unsubscribe from this group, send email to >>> >> adwords-api...@googlegroups.com >> >> >>> 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 a topic in the >>> Google Groups "AdWords API Forum" group. >>> To unsubscribe from this topic, visit >>> https://groups.google.com/d/topic/adwords-api/Jmbqifyr_Ro/unsubscribe. >>> >> To unsubscribe from this group and all its topics, send an email to >>> adwords-api...@googlegroups.com. >> >> >>> Visit this group at https://groups.google.com/group/adwords-api. >>> To view this discussion on the web visit >>> https://groups.google.com/d/msgid/adwords-api/780b5d92-b91a-41d5-9467-246325408472%40googlegroups.com >>> <https://groups.google.com/d/msgid/adwords-api/780b5d92-b91a-41d5-9467-246325408472%40googlegroups.com?utm_medium=email_source=footer> >>> . >>> For more options, visit https://groups.google.com/d/optout. >>> >> -- >> Best regards, >> >> Tejas Manohar >> > -- > -- > =~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~ > 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 adwords-api@googlegroups.com > To unsubscribe from this group, send email to > adwords-api+unsubsc
Re: AdWords API Python - Internal Error or Parsing Error
Hey Shwetha, I've confirmed that this issue is resolved by retrying, but it happens very consistently. Since it's resolved by retrying and I'm using codecs#getreader which knows how to handle Python unicode in both v2 and v3, I really believe this issue is due to malformed data sent back from the API as a result of an error. Let me know what more info I could provide to help. Thanks! On Wed, Jul 20, 2016 at 1:56 PM 'Shwetha Vastrad (AdWords API Team)' via AdWords API Forum <adwords-api@googlegroups.com> wrote: > Hi Tejas, > > This issue is related to how Python handles data streams and not specific > to AdWords API. I suggest that you post your query in the AdWords API > Python library repository > <https://github.com/googleads/googleads-python-lib> as they are better > equipped to help you out. > > Regards, > Shwetha, AdWords API Team. > > -- > -- > =~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~ > 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 adwords-api@googlegroups.com > To unsubscribe from this group, send email to > adwords-api+unsubscr...@googlegroups.com > 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 a topic in the > Google Groups "AdWords API Forum" group. > To unsubscribe from this topic, visit > https://groups.google.com/d/topic/adwords-api/Jmbqifyr_Ro/unsubscribe. > To unsubscribe from this group and all its topics, send an email to > adwords-api+unsubscr...@googlegroups.com. > Visit this group at https://groups.google.com/group/adwords-api. > To view this discussion on the web visit > https://groups.google.com/d/msgid/adwords-api/780b5d92-b91a-41d5-9467-246325408472%40googlegroups.com > <https://groups.google.com/d/msgid/adwords-api/780b5d92-b91a-41d5-9467-246325408472%40googlegroups.com?utm_medium=email_source=footer> > . > For more options, visit https://groups.google.com/d/optout. > -- Best regards, Tejas Manohar -- -- =~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~ 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 adwords-api@googlegroups.com To unsubscribe from this group, send email to adwords-api+unsubscr...@googlegroups.com 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 adwords-api+unsubscr...@googlegroups.com. Visit this group at https://groups.google.com/group/adwords-api. To view this discussion on the web visit https://groups.google.com/d/msgid/adwords-api/CAJU0XY5bU1d66y8-5SDgMwALTDupnXAq7KKtePiikdLQwGxDnA%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
Re: AdWords API Python - Internal Error or Parsing Error
Hm, that doesn't parse the CSV though. On Mon, Jul 18, 2016 at 2:10 PM 'Shwetha Vastrad (AdWords API Team)' via AdWords API Forum <adwords-api@googlegroups.com> wrote: > Hi Tejas, > > Have you tried using the download_criteria_report_as_stream.py > <https://github.com/googleads/googleads-python-lib/blob/master/examples/adwords/v201605/reporting/download_criteria_report_as_stream.py> > example > to stream AdWords reports? Could you use the below code snippet to process > *stream_data*? > > > try: >while True: > chunk = stream_data.read(CHUNK_SIZE) > if not chunk: break > report_data.write(chunk.decode() if sys.version_info[0] > == 3 and getattr(report_data, 'mode', 'w') > == 'w' else chunk) >print report_data.getvalue() > finally: >report_data.close() >stream_data.close() > > If this doesn't work, please provide the complete report definition used > and any error message received along with your clientCustomerID. Please use > *Reply > privately to author* when responding. > > Regards, > Shwetha, AdWords API Team. > > -- > -- > =~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~ > 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 adwords-api@googlegroups.com > To unsubscribe from this group, send email to > adwords-api+unsubscr...@googlegroups.com > 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 a topic in the > Google Groups "AdWords API Forum" group. > To unsubscribe from this topic, visit > https://groups.google.com/d/topic/adwords-api/Jmbqifyr_Ro/unsubscribe. > To unsubscribe from this group and all its topics, send an email to > adwords-api+unsubscr...@googlegroups.com. > Visit this group at https://groups.google.com/group/adwords-api. > To view this discussion on the web visit > https://groups.google.com/d/msgid/adwords-api/7dd4adad-b8bd-4825-8639-5bef60ccd42c%40googlegroups.com > <https://groups.google.com/d/msgid/adwords-api/7dd4adad-b8bd-4825-8639-5bef60ccd42c%40googlegroups.com?utm_medium=email_source=footer> > . > For more options, visit https://groups.google.com/d/optout. > -- Best regards, Tejas Manohar -- -- =~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~ 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 adwords-api@googlegroups.com To unsubscribe from this group, send email to adwords-api+unsubscr...@googlegroups.com 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 adwords-api+unsubscr...@googlegroups.com. Visit this group at https://groups.google.com/group/adwords-api. To view this discussion on the web visit https://groups.google.com/d/msgid/adwords-api/CAJU0XY4CZmeSFtXWnm-q3yEJg_n7m9N6TUuNPR0Z-UHKsyWQ4A%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
Re: Retrieve account creation date
> Please note that if this value has been changed after campaign creation, this will no longer indicate the date on which the campaign was created. What value? Shouldn't StartDate be immutable? On Fri, Jun 24, 2016 at 1:30 PM 'Shwetha Vastrad (AdWords API Team)' via AdWords API Forum <adwords-api@googlegroups.com> wrote: > Hi Tejas, > > You could query for StartDate > <https://developers.google.com/adwords/api/docs/appendix/reports/campaign-performance-report#startdate> > in > the Campaign Performance Report > <https://developers.google.com/adwords/api/docs/appendix/reports/campaign-performance-report>. > When you add a campaign > <https://developers.google.com/adwords/api/docs/reference/v201605/CampaignService.Campaign#startdate>, > this field defaults to the current day in the parent account's local > timezone. Please note that if this value has been changed after campaign > creation, this will no longer indicate the date on which the campaign was > created. > > Regards, > Shwetha, AdWords API Team. > > -- > -- > =~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~ > 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 adwords-api@googlegroups.com > To unsubscribe from this group, send email to > adwords-api+unsubscr...@googlegroups.com > 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 a topic in the > Google Groups "AdWords API Forum" group. > To unsubscribe from this topic, visit > https://groups.google.com/d/topic/adwords-api/cynjFINbqao/unsubscribe. > To unsubscribe from this group and all its topics, send an email to > adwords-api+unsubscr...@googlegroups.com. > Visit this group at https://groups.google.com/group/adwords-api. > To view this discussion on the web visit > https://groups.google.com/d/msgid/adwords-api/a3d19dae-3608-4b41-90d7-cf34cbaa82dd%40googlegroups.com > <https://groups.google.com/d/msgid/adwords-api/a3d19dae-3608-4b41-90d7-cf34cbaa82dd%40googlegroups.com?utm_medium=email_source=footer> > . > For more options, visit https://groups.google.com/d/optout. > -- Best regards, Tejas Manohar -- -- =~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~ 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 adwords-api@googlegroups.com To unsubscribe from this group, send email to adwords-api+unsubscr...@googlegroups.com 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 adwords-api+unsubscr...@googlegroups.com. Visit this group at https://groups.google.com/group/adwords-api. To view this discussion on the web visit https://groups.google.com/d/msgid/adwords-api/CAJU0XY4PpKxGH-aLA-20BtbQjBEoDcFQvc%3D84fe87sRTGX%3DjGg%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
