Hello -
I'm working on figuring that out now. Since we know the Bulk Upload service
doesn't validate these links it's possible you can use that, but I'm going to
see if there's another way.
Best,
Ben Karl
Google Ads API Team
ref:_00D1U1174p._5004Q2iOP6Z:ref
--
--
Thanks for the reply.
So How can I remove them? It is not possible with API or UI.
On Mon, Apr 17, 2023 at 4:29 PM Google Ads API Forum Advisor
wrote:
> Hello -
>
> I was able to determine how these shared sets were attached to your
> campaign. Two of them were linked in 2021, before we had
Hello -
I was able to determine how these shared sets were attached to your campaign.
Two of them were linked in 2021, before we had this type of validation in the
API:
Shared Set #7354130802 -> Campaign #9414378602
Shared Set #7354130802 -> Campaign #940730
The other two were linked via
Hello -
Thank you for following up, and apologies for the delay. I've been coordinating
internally to get information on how this shared set was linked, but the team
is still trying to identify the root cause. I requested an expedited resolution
and hope to share more details with you as soon
Hello,
It is nearly 3 months.
Could you share the latest status of this issue please?
Thanks
On Tuesday, February 28, 2023 at 12:01:39 AM UTC+3 Google Ads API Forum
Advisor wrote:
> Hello -
>
> Unfortunately we're still working on this. I was able to confirm that this
> error is expected
We still have the problem.
Could you give any update on this topic please? It is nearly one month now.
Thanks
On Wednesday, February 15, 2023 at 6:34:13 PM UTC+3 Google Ads API Forum
Advisor wrote:
> Hello -
>
> Thank you for following up. Unfortunately I don't have any updates at the
>
Hello -
Thank you for following up. Unfortunately I don't have any updates at the
moment. I'm coordinating with the engineering team that focuses on this feature
on the investigation and I just prompted them for an update. I'll follow up
here as soon as I have more information.
Best,
Ben
Hi,
Is there any update here?
On Friday, February 10, 2023 at 10:50:46 AM UTC+3 sealytic...@gmail.com
wrote:
> Hello sorry to write again but it is already one week and I am asked about
> the case regularly.
>
> Can you share an update please?
>
> Thanks
>
> On Friday, February 3, 2023 at
Hello sorry to write again but it is already one week and I am asked about
the case regularly.
Can you share an update please?
Thanks
On Friday, February 3, 2023 at 9:12:54 PM UTC+3 Google Ads API Forum
Advisor wrote:
> Hello -
>
> Thanks for following up. The team is still investigating
Hello -
Thanks for following up. The team is still investigating this issue, so
unfortunately I don't have an update right now. I'll respond to this thread as
soon as there's information to share.
Best,
Ben Karl
Google Ads API Team
ref:_00D1U1174p._5004Q2iOP6Z:ref
--
--
Hello,
Is there any update on this topic?
Thanks
On Wednesday, February 1, 2023 at 9:56:47 PM UTC+3 adsapi wrote:
> Hi,
>
> Thank you for trying out the provided suggestions. Allow me to raise this
> issue to my rest of the team. We will reach out to you once we have any
> updates.
>
>
Hi,
Thank you for trying out the provided suggestions. Allow me to raise this issue
to my rest of the team. We will reach out to you once we have any updates.
Regards,
Yasar
Google Ads API Team
ref:_00D1U1174p._5004Q2iOP6Z:ref
--
--
=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~
Also find
Hi again,
I tried with curl request and get the same error.
I have sent the curl logs with private message.
Thanks
On Tuesday, January 31, 2023 at 7:08:25 PM UTC+3 adsapi wrote:
> Hi,
>
> In addition to above, could you provide the full logs for the API request
> where you have added
Hi,
In addition to above, could you provide the full logs for the API request where
you have added NEGATIVE_KEYWORD shared set type to your app campaign so that I
can discuss this with my rest of team.
Kindly provide the complete logs via reply privately to author option.
Regards,
Yasar
Hi,
I work with Heidi. Thanks for getting back to us.
For your question “If NEGATIVE_KEYWORD shared set type cannot be applied to
channel type MULTIPLE, how it was set first?”, I’ve tried to add
NEGATIVE_KEYWORD shared set type to my app campaign and it successfully added
without any API
Hello thanks for the reply.
If NEGATIVE_KEYWORD shared set type cannot be applied to channel type
MULTIPLE, how it was set first? I cannot understand the case. Shared set
type never changed.
So to remove this campaigns, should I change its type first?
If we don't want to remove shared sets,
Hi,
Thank you for the reply.
Upon checking on the campaignSharedSets resource names you want to remove, I
can see that it has the "advertisingChannelType": "MULTI_CHANNEL" with
sharedSet type": "NEGATIVE_KEYWORDS". That being said, kindly note that
NEGATIVE_KEYWORD shared set type cannot be
Hello,
I replied privately request and response logs.
Thanks
On Friday, January 27, 2023 at 7:06:13 PM UTC+3 adsapi wrote:
> Hi,
>
>
> Thanks for reaching out to the Google Ads API Team. I hope you are doing
> well today.
>
>
> With regard to your concern, It seems you have encountered an
Hi,
Thanks for reaching out to the Google Ads API Team. I hope you are doing well
today.
With regard to your concern, It seems you have encountered an
OPERATION_NOT_PERMITTED_FOR_CONTEXT. That error said, The operation is not
allowed for the given context. However, to further investigate
Hello,
Somehow, our sharedsets have been attached campaigns with channel type
MULTIPLE. Now we want to remove these campaigns from SharedSet but both API
and UI is giving error. I understood that channel type MULTIPLE is not
allowed with sharedsets but if this is the case how can we able to
20 matches
Mail list logo
