Google ADS API V9 IpBlock Ban, banning /16 instead 0/24

[Gabriel Gregori]

Hi,

I have developed a system to ban ip addresses with sub networks, and I sending to google ads API V9 ipBlock criterion with ip addresses like 91.205.230.0/24 and the google ads were always considering the right subnet class, always became 91.205.230.* in google ads system, but somehow after some time when I checked the banned ip's most of the ip's addresses subnets are 0/16 instead 0/24, the problem is that this is too much, about 65.000 ip's addresses, co-workers are telling me too check this on system, but I think this happen on google side when google ads receive too much 0/24 ip block criterion and then convert all 0/24 from same network to a single 0/16 ipblock criterion, could you please check it and confirm to me?

Thanks in advance!

Gabriel Gregori.

[Gabriel Gregori]

Since I didn't received a answer yet I apology if my description wasn't good enough, I will try to make it simple.

If I create many Ip Block Criterion with subnetmask 0/24 from same network in a campaign will google ads system transform all those ip block criterium from that campaign in a single IpBlockCriterium with ip subnetmask 0/16?

Or even simply

will that
CampaignCriterions[
   IpBlock: 91.205.230.*,
   IpBlock: 91.205.10.*,

   IpBlock: 91.205.30.*,

   IpBlock: 91.205.70.*,

   IpBlock: 91.205.80.*,

   IpBlock: 91.205.90.*,

   IpBlock: 91.205.150.*,

   ...

]

be converted to

CampaignCriterions[
   IpBlock: 194.65.0.0/16
]

And please if you can't understand let me know, because this is very important, it is our business survival.

Gabriel Gregori.

[Google Ads API Forum Advisor]

Hi Gabriel,

Thank you for your patience. I'm Peter and please allow me now to assist you regarding your concerns.

I understand the urgency of your concern. As per our IpBlock documentation, it states that :

An IpBlock criterion used for IP exclusions. We allow: - IPv4 and IPv6 addresses - individual addresses (192.168.0.1) - masks for individual addresses (192.168.0.1/32) - masks for Class C networks (192.168.0.1/24)

That said, however, the general and specific behavior of how an IpBlock performs or is implemented in Google's networks is more of a Product level matter. I would then recommend that you reach out to the Google Ads Product support team, via this link, for further insight.

I hope this helps.

Best regards,

Peter Laurence Google Ads API Team

ref:_00D1U1174p._5004Q2aQbIm:ref

[Gabriel Gregori]

Hi,

Thanks! But unfortunantely it wasn't on google side the issue, it was a external system which had access to the google ads, and was banning masks 0/16 without my knowledge, since I had no vision I thought it was google side, but then forgive, and thanks again!

Best regards,

Gabriel Gregori.

[Google Ads API Forum Advisor]

Hi Gabriel,

Thank you for the updates.

We're glad that you were able to find the information related to the behavior you observed. If you have additional questions regarding the topic being discussed in this thread, feel free to send those over to our team and we would be happy to assist you further.

Best regards,

Heidi Google Ads API Team

ref:_00D1U1174p._5004Q2aQbIm:ref