Hi,
I cannot get a report for the correct dates. I am using the followign query:
SELECT
campaign.name,
customer.id,
ad_group.id,
ad_group.name,
ad_group.labels,
segments.date
FROM ad_group
WHERE segments.date = '2021-05-04'
AND ad_group.status = ENABLED
AND ad_group.name = 'roman test'"""
There
Hi!
I am getting an Internal error from Google Ads when trying to work with
keywords. Here is the response I am getting:
2021-04-21T20:14:28.869938+00:00 heroku[router]: at=info method=GET
path="/api/results/job/608084d6361c8d0004af25b2"
host=dashboard-add3.herokuapp.com
Hi Ernie!
The customer id is '716-826-1846'. This is a test account.
Here's what I'm doing, I bolded the relevant parts:
toMutate.push({
_resource: 'CampaignCriterion',
_operation: 'create',
ad_group: `customers/${customer.cid}/adGroups/${adGroupId}`,
campaign:
Hi there!
Currently, I am trying to disable certain devices on the ad group level by
using AdGroupBidModifier with the appropriate device type and setting
`bid_modifier` to 0. Instead, I want to do the same on the Campaing level.
However, it seems that CampaignBidModifier does not support
Hi,
I would like to request the ability to create campaign goals via the API.
Thank you!
Best regards,
Roman
--
--
=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~
Also find us on our blog:
https://googleadsdeveloper.blogspot.com/
=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~
You
Hi! I am using Google Ads API via Opteo that extends it by using grpc. I
started getting the error described in the err.json file. I believe it is
related to grpc. I believe that it is due to my request being rtoo large
but I was wondering if anyone could confirm that please?
Thank you!
Roman
The problem is gone now. All I had to do was turn off the ad-block. This
should really be mentioned somewhere that even to enable the API that the
ad-block should be disabled. Thanks, everyone!
On Tuesday, September 8, 2020 at 12:22:08 PM UTC-7 adsapiforumadvisor wrote:
> Hi Roman,
>
> Thank
I created a new project and a new billing account but the problem still
exists new Tracking number: c7177652421928959
On Monday, September 7, 2020 at 5:48:37 PM UTC-7 Roman Akhtariev wrote:
> The attached screenshot is what I see when trying to enable it
>
> Tracking number: c2431369
