Hello Ziv,
I’m James from the Google Ads scripts support team. Thank you for raising your concern to us.
Can you please provide first the following information below so that we can have a better understanding of the issue?
Regards,
|
||||||
|
||||||
|
||||||
Hi Ziv,
This is Yasmin, I'm a colleague of Teejay in the Google Ads Scripts team.
I understand that the deadline for migrating the scripts is nearing, however, it appears that we haven't heard from the team yet with respect to this issue. I'll make sure to request for a follow up in this regard and our team will update this thread the soonest we hear from them.
Thanks,
|
||||||
Hi Ziv,
I'm afraid we don't have updates for this yet. I'll make sure to request a follow up on the issue and let you know once we receive relevant information. Your patience during this investigation is highly appreciated.
Hi Ziv,
It appears that we do not have updates we can share at this time, however, rest assured that our team is investigating the issue and are getting to the bottom of it. I'll request for an update once more and express urgency. We'll let you know the soonest we hear back from them.
We do appreciate your patience during this time.

Hi Ziv,
I heard back from the team. Allow me to relay what they had gathered.
Video responsive ads have always required a call-to-action, description, and long headline since they were added to the library last year. It's never been possible to create a video responsive ad without those fields, and preview runs without them would have raised a "missing required argument" error. Without additional details, they can't really guess where you got the impression that you could create video responsive ads without these fields. Either way, you would need to update your script to include those fields in the video responsive ad builder. Per the error message, you should provide those fields when building video responsive ads. You can obtain the values for existing video responsive ads using the snippet below:
var report = AdsApp.report(
`SELECT ad_group_ad.ad.video_responsive_ad.call_to_actions, ad_group_ad.ad.video_responsive_ad.descriptions, ad_group_ad.ad.video_responsive_ad.long_headlines ` +
`from ad_group_ad ` +
`WHERE ad_group_ad.ad.type = "VIDEO_RESPONSIVE_AD" ` +
// Can filter on things like ad_group.id, ad_group.name, ad_group_ad.ad.id, etc.
`campaign.id = ${CAMPAIGN_ID}`);
var rows = report.rows();
while (rows.hasNext()) {
var row = rows.next();
var callToActions = row['ad_group_ad.ad.video_responsive_ad.call_to_actions'];
var descriptions = row['ad_group_ad.ad.video_responsive_ad.descriptions'];
var longHeadlines = row['ad_group_ad.ad.video_responsive_ad.long_headlines'];
Logger.log(`all callToActions: ${callToActions.join(', ')}`);
var firstCallToAction = callToActions[0];
}
With that being said, I really appreciate you providing your insights as to what may have caused this issue. Allow me to communicate your findings and check with our team in order to validate this and we'll update you once we hear back from them, but do let us know if what they've provided works for you.
Regards,
Hi,
Ciara here, from the Google Ads Scripts team as well. Allow me to answer your additional concerns.
I see now the docs has been updated - so the new adTypes should be in use, right? - Yes, kindly use the updated adTypes for your scripts on the new experience.
In the legacy system there is ' TRUEVIEW_IN_DISPLAY_VIDEO_AD' and in the new experience there is no match for this - is this type deprecated? - You can view the supported values here.
In addition, I received the following feedback from the team:
The getType() return values are slightly different because of the new scripts experience, but there is not a functional difference between TRUEVIEW_IN_STREAM_VIDEO_AD and VIDEO_TRUEVIEW_IN_STREAM_AD - they both refer to the same type of ad.
TRUEVIEW_IN_DISPLAY_VIDEO_AD corresponds with the "YouTube Video discovery ad" type, which last year was renamed to "in-feed video ad" type. Are you perhaps looking for newVideoAd().inFeedAdBuilder()?
Looking forward to your response.
Regards,
|
||||||