Thanks, I almost got everything working.
I plan to retrieve the old feed-based extensions using a where clause, 
something like

SELECT <fields>
FROM campaign_extension_setting
WHERE campaign_extension_setting.extension_type = 'SITELINK'
  AND campaign.id NOT IN (1, 2, 3, 4)

And the IDs 1,2,3 and 4 showed up at a previous call to retrieve 
asset-based extensions and their associations to campaigns.
That should be the way to ensure we leave out migrated extensions, right?

The question I have - I also need to obtain sitelinks associated with 
groups, and some accounts have thousands of groups.
Is there any limitation on defining a set in AWQL?
And do AWQL queries have a limit in size? I know other APIs that enforce a 
limit of 10 MB per request.

So the question is now about general limitations on AWQL queries.

On Thursday, February 3, 2022 at 2:56:05 PM UTC+1 adsapi wrote:

> Hi Zweite,
>
> In Asset-based Extensions Migration guide 
> <https://developers.google.com/google-ads/api/docs/extensions/assets/migrating-extensions>
>  
> it states that if both Asset-based and Feed-based extensions of a 
> particular type are attached to the same customer, campaign, or ad group, 
> the Asset-based extensions will be served. This only applies for entities 
> at the same level. So for example, linking an asset to an ad group will 
> prevent all feeds serving on that ad group, but other ad groups in the same 
> campaign may continue serving feeds. Once you migrate a sitelink at ad 
> group level in that ad group you will have to migrate all sitelink 
> extensions in that ad group for all sitelink extensions to serve in that ad 
> group. But auto migration will migrate all of the extensions so all will 
> serve.
>
> As soon as an extension is migrated the asset based one will start serving 
> and the extension setting one will stop serving.
>
> Regarding reporting,  asset_field_type_view 
> <https://developers.google.com/google-ads/api/fields/v9/asset_field_type_view>
>  will 
> cover on any level the asset extension is connected.
>
> Regards,
>
> [image: Google Logo] 
> Aryeh Baker 
> Google Ads API Team 
>   
>
> ref:_00D1U1174p._5004Q2VQ9mn: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 
"Google Ads API and AdWords 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/39fb5004-bb75-4444-8673-fe065dd2c107n%40googlegroups.com.
  • Re... Zweitze
    • ... 'Google Ads API Forum Advisor' via Google Ads API and AdWords API Forum
      • ... Zweitze
      • ... kheny banguis
        • ... 'Google Ads API Forum Advisor' via Google Ads API and AdWords API Forum
          • ... Ngon Nguyen
          • ... Zweitze
            • ... 'Google Ads API Forum Advisor' via Google Ads API and AdWords API Forum
              • ... Zweitze
                • ... 'Google Ads API Forum Advisor' via Google Ads API and AdWords API Forum

Reply via email to