I started a new question with these new problems here <https://groups.google.com/forum/?utm_medium=email&utm_source=footer#!topic/adwords-api/joBzQcn9_t8> .
El viernes, 28 de agosto de 2015, 12:21:27 (UTC-3), sebastia...@despegar.com escribió: > > I also have a problem when creating "App Engagement Text Ads". > Apparently the "Call to Action" field is loaded correctly but when shown > in the preview it is not refresh accordingly. I attach an image this post > so you can understand the problem. In the image, where it says "INSTALL" it > should say what the "Call to Action" field says, but this is not what I get. > > El viernes, 28 de agosto de 2015, 8:36:21 (UTC-3), > sebastia...@despegar.com escribió: >> >> Hello again, >> I am having a problem after I upload "App Engagement Image Ads" and "App >> Engagement Text Ads", >> From th AdWords UI I can see they are created but the preview can no >> longer be shown when I click "View full size display ad." I attach an image >> to this post with the error message I am getting. >> This used to work a couple of days ago after I uploaded Ads with the same >> program. Is it possible that I am not uploading well-formed ad's and this >> is the reason the UI cannot generate a preview for them? >> Strangely enough, when I click the ad to modify it, I can click "save" >> and after I do that the UI becomes able to show the preview. Can somebody >> explain this to me? >> >> El viernes, 21 de agosto de 2015, 8:09:33 (UTC-3), >> sebastia...@despegar.com escribió: >>> >>> Hi Josh, >>> >>> OK, I see we are finally talking about the same use case. >>> >>> I tried using *originAdId* and now it seems to work (although when I >>> had the error I posted before I was doing the exact same thing and got an " >>> InternalApiError.UNEXPECTED_INTERNAL_API_ERROR"; maybe it was another >>> problem from our side). >>> >>> >>> When setting the *Image*, you *should* be able to simply pass an *Image* >>> object >>>> with its mediaId >>>> <https://developers.google.com/adwords/api/docs/reference/v201506/AdGroupAdService.Image#mediaId> >>>> set >>>> to an existing image in order to reuse that image. Unfortunately, this >>>> doesn't work right now. I have raised this issue and we're looking into it. >>>> >>> >>> I'm glad that you have a new issue for this. I think it's the most >>> intuitive way to reuse media, and also this will be consistent with the API >>> reference. >>> >>> Thanks for your guidance on how to use the API properly, >>> seb. >>> >>> El jueves, 20 de agosto de 2015, 15:46:55 (UTC-3), Josh Radcliff >>> (AdWords API Team) escribió: >>>> >>>> Hi, >>>> >>>> I finally get it. :) The key points are: >>>> >>>> 1. For the Image app engagement ad (455) >>>> >>>> <https://developers.google.com/adwords/api/docs/appendix/templateads#image_cto_ad> >>>> and Image app install ad (432) >>>> >>>> <https://developers.google.com/adwords/api/docs/appendix/templateads#image_ctd_ad>, >>>> >>>> you *must* set the *Image* for the ad via the TemplateAd.adAsImage >>>> >>>> <https://developers.google.com/adwords/api/docs/reference/v201506/AdGroupAdService.TemplateAd#adAsImage> >>>> attribute, >>>> as you were doing in your code. >>>> 2. When setting the *Image*, you *should* be able to simply pass an >>>> *Image* object with its mediaId >>>> >>>> <https://developers.google.com/adwords/api/docs/reference/v201506/AdGroupAdService.Image#mediaId> >>>> set >>>> to an existing image in order to reuse that image. Unfortunately, this >>>> doesn't work right now. I have raised this issue and we're looking into >>>> it. >>>> 3. Although using *mediaId* doesn't work, I have good news! You >>>> *can* set originAdId >>>> >>>> <https://developers.google.com/adwords/api/docs/reference/v201506/AdGroupAdService.TemplateAd#originAdId> >>>> to >>>> an existing ad that uses the same template, and AdWords will copy all >>>> of >>>> the template elements *and* the *Image* from the origin ad to your >>>> new ad. >>>> >>>> #3 means that for your use case of creating 500 ads, you can create one >>>> ad by setting the *Image.data* and using that for the *adAsImage* field. >>>> To create the other 499 ads, you can specify the first ad's ID for >>>> *originAdId*, and skip the rest. This will work even if you are >>>> creating ads in a different ad group from the first ad. >>>> >>>> Note that when creating the *TemplateAd*s using *originAdId*, you >>>> should do the following: >>>> >>>> - set *url, displayUrl, templateId, name*, and *originAdId* >>>> - do *not *set templateElements >>>> >>>> <https://developers.google.com/adwords/api/docs/reference/v201506/AdGroupAdService.TemplateAd#templateElements>, >>>> >>>> *dimensions, *or *adAsImage* >>>> >>>> I think that covers everything, but let me know if you still have >>>> questions. Thanks for bearing with me while I was trying to understand >>>> your >>>> use case. :) >>>> >>>> Cheers, >>>> Josh, AdWords API Team >>>> >>>> On Thursday, August 20, 2015 at 9:15:38 AM UTC-4, seb wrote: >>>>> >>>>> >>>>> >>>>> El jueves, 20 de agosto de 2015, 8:45:50 (UTC-3), >>>>> sebastia...@despegar.com escribió: >>>>>> >>>>>> Hi Josh, >>>>>> >>>>>> I noticed in your code that you are setting the adAsImage >>>>>>> <https://developers.google.com/adwords/api/docs/reference/v201506/AdGroupAdService.TemplateAd#adAsImage> >>>>>>> field, >>>>>>> and that's the only place where you use an *Image* object. However, >>>>>>> I'm pretty sure that the *adAsImage* field is being ignored since >>>>>>> that field is meant to provide you a preview of the ad in image form, >>>>>>> and >>>>>>> that preview for template ID 455 is simply based on the other fields in >>>>>>> the >>>>>>> ad that identify your app. >>>>>>> Does the image you provided actually appear on the ad in the AdWords >>>>>>> user interface? >>>>>>> >>>>>> >>>>>> No it doesn't, but the UI doesn't show the image when I create one >>>>>> manually either. If I download the report for two "Image app engagement >>>>>> ad's", one created manually via the AdWords UI and one created >>>>>> automatically with the program I sent you the structure is the same. >>>>>> These >>>>>> arguments seem to favor, in my view, that the adAsIamge is not being >>>>>> ignored. >>>>>> >>>>> >>>>> UPDATE: >>>>> Yes, it does show the image in the AdWords UI. Initially when I said >>>>> no was because I was using Firefox, but in Chrome it does show the image >>>>> in >>>>> both cases (manually created Ad, and created with the program I sent you). >>>>> >>>>> -- -- =~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~ 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 http://groups.google.com/group/adwords-api. To view this discussion on the web visit https://groups.google.com/d/msgid/adwords-api/d8dca93e-979f-4b8d-8cae-d09c64d30ba8%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
