Connect with us


Google Ads API Version 11.1 Now Out



Google Ads API Version 10 Is Out

Google has released version 11.1 of the Google Ads API. Version 11 of the Google Ads API was released in June, so this is a minor update to version 11.

Here is everything that was updated in version 11.1:


  • Added AssetGroup.ad_strength to represent the overall quality of the asset group.
    When advertisers mutate asset groups or assets associated with the asset groups, this field is recalculated. Until the recalculation is finished, the value is PENDING.


  • Added FlexibleRuleUserListInfo and RuleBasedUserListInfo.flexible_rule_user_list.
  • Added more values to the LeadFormFieldUserInputType enum (used as predefined questions for lead form extensions).
  • Added the following fields to UserAttribute: lifecycle_stage, first_purchase_date_time, event_attribute


  • Added Campaign.bidding_strategy_system_status to show the system status of the bidding strategy, such as whether it is learning, limited, or misconfigured.


  • Added support for the following metrics in the campaign report: all_conversions_from_click_to_call, all_conversions_from_directions, all_conversions_from_menu, all_conversions_from_order, all_conversions_from_other_engagement, all_conversions_from_store_visit, all_conversions_from_store_website, Made metrics.phone_call compatible with segments.hour in the campaign report.


  • You can now create experiments using GoogleAdsService.Mutate(). Previously, it was possible only when using ExperimentService.


  • Added Targeting.audience_targeting, which allows for specifying affinity and in-market categories to generate a reach forecast using ReachPlanService.GenerateReachForecast.
  • Added support for YouTube Select:
  • Added support for returning YouTubeSelectLineUp as product metadata when calling ReachPlanService.ListPlannableProducts.
  • Added PlannedProduct.advanced_product_targeting, which allows for specifying YouTubeSelectSettings to generate a reach forecast using ReachPlanService.GenerateReachForecast.
  • Added AudienceInsightsService.GenerateAudienceCompositionInsights (available to allowlisted accounts only), used to find attributes strongly associated with a particular audience, similar to Insights Finder.


  • Added UpgradeLocalCampaignToPerformanceMaxRecommendation.
  • Added DisplayExpansionOptInRecommendation.

Forum discussion at Twitter.



Google Search Bard, It’s ChatGPT Feature, To Trusted Testers



Google Bard Butler Graphic

Well, we knew it was coming and here it is, Bard – Google’s answer to ChatGPT. Google is now having its trusted testers test out Bard and will soon roll it out more widely to users in Google Search and others products in the coming weeks, Google announced. It is not called Apprectice Bard but rather Bard.

I covered this when the news broke at Search Engine Land and as I pointed out, right now, Google does not have an answer for how to attribute or link to answers Bard generates – yet. But I do suspect Google will have some answer for it. I also mentioned that Google has been writing knowledge panels using AI and other methods since 2018 and said then it is not stealing. So it will be interesting to see what Google ends up doing here.

Bard is Google’s experimental conversational AI service, powered by LaMDA, where Google can answer questions that might not have one right answer. Google said they will roll this out more widely in the coming weeks but for now, only trusted testers (who is outsourced to a third-party company) will be able to play with it.

Google said, “Soon, you’ll see AI-powered features in Search that distill complex information and multiple perspectives into easy-to-digest formats, so you can quickly understand the big picture and learn more from the web: whether that’s seeking out additional perspectives, like blogs from people who play both piano and guitar, or going deeper on a related topic, like steps to get started as a beginner. These new AI features will begin rolling out on Google Search soon.”

Here is a screenshot they shared of how it might look in Google Search:

Google Bard in Google Search

This is how it might look like in Google Search (without the attribution part…).

This is the Bard direct interface, not in search:

Google Bard GIF

I am super excited to see how this evolves at Google, Bing and others.

It is not too far off from the leaks of the Bing ChatGPT interface.

Here is Sundar Pichai’s tweets:

Here is some of the SEO community reaction:

Also, make sure to check out the roundup at Techmeme.

Forum discussion at Twitter, WebmasterWorld.

Source link

Continue Reading


Most SEOs Think Yahoo Won’t Be Able To Compete In Search



Yahoo 404 Baseball Sign

As you know, Yahoo is planning a come back to search with a new way of thinking about Yahoo Search. What that means, we don’t know yet, but we do know Yahoo is thinking hard about how they can compete. Greg Sterling ran a Twitter poll asking if Yahoo has a shot at it, and most say, nope – Yahoo Search is dead on arrival.

The poll on Twitter asked, “Yahoo is planning to “relaunch” search. Is there a chance to revive it?” It received a nice number of responses, 631 responses. The results were not too optimistic.

  • 43.7% said nope, dead on arrival
  • 26.6% said depends on the UI/UX
  • 29.6% said yes, now is the time

Here is that poll:

Personally, I think Yahoo has a good shot at it, better than most other companies. But time will tell and I am very much looking forward to seeing what Yahoo Search comes out with.

Forum discussion at Twitter.

Source link

Continue Reading


Google Clarifies JSON-LD, Microdata & RDFa Are All Supported For Structured Data



Google Schema

Google has clarified in its search developer documents that JSON-LD, Microdata and RDFa are all fully supported forms for structured data and Google Search. Google wrote, “all three supported formats are equally fine for Google, as long as they are valid and implemented properly per the feature’s documentation.”

The old paragraph in the documentation read:

Google Search supports structured data in the following formats, unless documented otherwise:

click for full size

The new paragraph in the documentation now reads:

Google Search supports structured data in the following formats, unless documented otherwise. In general, we recommend using a format that’s easiest for you to implement and maintain (in most cases, that’s JSON-LD); all 3 formats are equally fine for Google, as long as the markup is valid and properly implemented per the feature’s documentation.

click for full size

This was updated because Google’s Ryan Levering spotted the embedded tweet below, that shows there is confusion on which Google may or may not prefer. Ryan said, “We might need to tweak the wording for Google’s main structured data page.”

He said that Google “primarily recommend JSON-LD because sites screw up Microdata a lot more than they do JSON-LD because it’s embedded. We don’t have some secret plans to remove support for Microdata. Particularly for schema that is either very annotation/text heavy or very simple (so you don’t need to do meta tag gymnastics), Microdata can make more sense.”

So Lizzi Sassman updated the docs to reflect this.

Forum discussion at Mastodon.

Source link

Continue Reading