Hello,
I've spent some time trying to look into this example, but I'm still stumped.
I'm going to reach out to some other members of my team to see if they've
encountered anything like this before. I'll let you know what I find out.
Regards,
Mike, Google Ads API Team
ref:_00D1U1174p._5001UaSxGg
Hello,
Sorry for delay with answer.
We know that we can build workaround with CampaignSharedSets but we were
interested in the cause of this issue.
As you could see on previous screenshots that there are ~7 duplicated
CampaignSharedSets (which means they all are applied to *Removed*
SharedSets)
Hello,
Thanks for the clarification. I didn't notice that screenshot when the case was
escalated to me, and that helps to clarify the problem quite a lot.
I'm not sure how that shared set got into the state it is, since it appears to
be from 2017 and our change history only goes back to January
Hi Danica,
In my private response to you there SharedSet/CampaignSharedSet ids on
screen shots.
[image: Screen Shot 2020-04-30 at 2.21.25 PM.png]
Also, if you have access you can look to it on UI -
https://ads.google.com/aw/keywords/negative?ocid=126702634&euid=74496858&__u=8985522442&uscid=3
Hi Tetiana,
Thank you for providing the detailed description. I am checking on this
internally within the team. Rest assured we will get back to you once we have
more insight on this behavior.
Regards,
Danica, Google Ads API Team
ref:_00D1U1174p._5001UaSxGg:ref
--
--
=~=~=~=~=~=~=~=~=~=~=~=~
Hi Danica,
Flow which has been described before is automatic and we do it through the
API.
To remove SharedSet we:
1. Fetch all campaigns which are applied to current SharedSet through
the CampaignSharedSetService. Query looks like this: *"SELECT
campaign_shared_set.status, shared_s
Hi Tetiana,
Yes, I received your email - thanks for providing those details! Can you please
clarify a few things for me? You mentioned the following:
When we update rule, we unapply campaigns from SharedSet, remove SharedSet and
create the new one with up to date rule.
Are you performing these
Hi Danica,
I replied you privately with detailed information about our issue.
Have you received my email?
BR,
Tetiana
On Thursday, April 30, 2020 at 9:27:27 PM UTC+3, adsapiforumadvisor wrote:
>
> Hi Tetiana,
>
> Thanks for reaching out to us! Yes, kindly share your CID as well as the
> detaile
Hi Tetiana,
Thanks for reaching out to us! Yes, kindly share your CID as well as the
detailed request and response logs from the API so that I can further look into
it along with any additional screenshots that reflect the issue you are facing.
Can you also clarify which accounts were able to r
