The Standard Access request urgent

[Paulo Silva]

Hello. We have our application stopped for sales as we do not have standard 
access as we have received many customers in the last few days. Could you 
please prioritize? My MCC is 573-769-7662

-- 
-- 
=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~
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 adwords-api@googlegroups.com
To unsubscribe from this group, send email to
adwords-api+unsubscr...@googlegroups.com
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 adwords-api+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/adwords-api/94ed7c42-3bcf-4a11-b6fa-53ce3a09c78fn%40googlegroups.com.

OPERATION_NOT_PERMITTED_FOR_CONTEXT

[Paulo Silva]

Hi
a try to sendo blocked ips to campaing with this request

* Preparing request to 
https://googleads.googleapis.com/v15/customers/5932574280/campaignCriteria:mutate
* Current time is 2024-03-25T14:40:47.850Z
* Enable automatic URL encoding
* Using default HTTP version
* Enable timeout of 3ms
* Enable SSL validation
* Enable cookie sending with jar of 12 cookies
* TLSv1.2 (IN), TLS header, Supplemental data (23):
* 17 bytes stray data read before trying h2 connection
* TLSv1.2 (OUT), TLS header, Supplemental data (23):
*   Trying 2800:3f0:4001:830::200a:443...
* Connected to googleads.googleapis.com (2800:3f0:4001:830::200a) port 443 
(#3)
* ALPN, offering h2
* ALPN, offering http/1.1
*  CAfile: /etc/ssl/cert.pem
* TLSv1.0 (OUT), TLS header, Certificate Status (22):
* TLSv1.3 (OUT), TLS handshake, Client hello (1):
* TLSv1.2 (IN), TLS header, Certificate Status (22):
* TLSv1.3 (IN), TLS handshake, Server hello (2):
* TLSv1.2 (IN), TLS header, Finished (20):
* TLSv1.2 (IN), TLS header, Supplemental data (23):
* TLSv1.3 (IN), TLS handshake, Encrypted Extensions (8):
* TLSv1.3 (IN), TLS handshake, Certificate (11):
* TLSv1.3 (IN), TLS handshake, CERT verify (15):
* TLSv1.3 (IN), TLS handshake, Finished (20):
* TLSv1.2 (OUT), TLS header, Finished (20):
* TLSv1.3 (OUT), TLS change cipher, Change cipher spec (1):
* TLSv1.2 (OUT), TLS header, Supplemental data (23):
* TLSv1.3 (OUT), TLS handshake, Finished (20):
* SSL connection using TLSv1.3 / TLS_AES_256_GCM_SHA384
* ALPN, server accepted to use h2
* Server certificate:
*  subject: CN=upload.video.google.com
*  start date: Feb 26 08:18:27 2024 GMT
*  expire date: May 20 08:18:26 2024 GMT
*  subjectAltName: host "googleads.googleapis.com" matched cert's 
"*.googleapis.com"
*  issuer: C=US; O=Google Trust Services LLC; CN=GTS CA 1C3
*  SSL certificate verify ok.
* Using HTTP2, server supports multiplexing
* Connection state changed (HTTP/2 confirmed)
* Copying HTTP/2 data in stream buffer to connection buffer after upgrade: 
len=0
* TLSv1.2 (OUT), TLS header, Supplemental data (23):
* TLSv1.2 (OUT), TLS header, Supplemental data (23):
* TLSv1.2 (OUT), TLS header, Supplemental data (23):
* Using Stream ID: 1 (easy handle 0x1040096f200)
* TLSv1.2 (OUT), TLS header, Supplemental data (23):

> POST /v15/customers/5932574280/campaignCriteria:mutate HTTP/2
> Host: googleads.googleapis.com
> user-agent: insomnia/8.6.1
> content-type: application/json
> developer-token: litD5RA_CgW3FMlCnb7mTw
> authorization: Bearer 
ya29.a0Ad52N39bZic5lbbyLEYJyn863a7-FPHZXvRRzzUNoM_NP8udRX7SVvdoChe1UXUMZ3qoayI_F4a1xpWuDNBvIP9eWmiryAelRYyTNssIHXKjHmmk4FbJnEwGZd0H28oeU3tPygaNQhVEfjIR-KHHoInmqOx7QvgryXWt6AaCgYKAQ8SAQ8SFQHGX2Mih65SeZLyq9IPU9eUf0GjxQ0173
> accept: */*
> content-length: 170

* TLSv1.2 (OUT), TLS header, Supplemental data (23):

| 
{"customer_id":"5932574280","operations":[{"create":{"campaign":"customers/5932574280/campaigns/20717377421","negative":true,"ip_block":{"ip_address":"86.163.43.213"}}}]}

* We are completely uploaded and fine
* TLSv1.2 (IN), TLS header, Supplemental data (23):
* TLSv1.3 (IN), TLS handshake, Newsession Ticket (4):
* TLSv1.3 (IN), TLS handshake, Newsession Ticket (4):
* old SSL session ID is stale, removing
* TLSv1.2 (IN), TLS header, Supplemental data (23):
* TLSv1.2 (OUT), TLS header, Supplemental data (23):
* TLSv1.2 (IN), TLS header, Supplemental data (23):
* TLSv1.2 (IN), TLS header, Supplemental data (23):

< HTTP/2 400 
< request-id: InVoUjxhE7_vjMQaL09Pxw
< vary: X-Origin
< vary: Referer
< vary: Origin,Accept-Encoding
< content-type: application/json; charset=UTF-8
< date: Mon, 25 Mar 2024 14:40:48 GMT
< server: ESF
< cache-control: private
< x-xss-protection: 0
< x-frame-options: SAMEORIGIN
< x-content-type-options: nosniff
< alt-svc: h3=":443"; ma=2592000,h3-29=":443"; ma=2592000
< accept-ranges: none


* TLSv1.2 (IN), TLS header, Supplemental data (23):
* Received 998 B chunk
* TLSv1.2 (IN), TLS header, Supplemental data (23):
* Connection #3 to host googleads.googleapis.com left intact

But a receive this response

{
"error": {
"code": 400,
"message": "Request contains an invalid argument.",
"status": "INVALID_ARGUMENT",
"details": [
{
"@type": 
"type.googleapis.com/google.ads.googleads.v15.errors.GoogleAdsFailure",
"errors": [
{
"errorCode": {
"contextError": "OPERATION_NOT_PERMITTED_FOR_CONTEXT"
},
"message": "The operation is not allowed for the given context.",
"trigger": {
"stringValue": "EXPRESS(EXPRESS_SMART)"
},
"location": {
"fieldPathElements": [
{
"fieldName": "operations",
"index": 0
},
{
"fieldName": "create"
},
{
"fieldName": "ip_block"
}
]
}
}
],
"requestId": "InVoUjxhE7_vjMQaL09Pxw"
}
]
}
}

can i help me?

-- 
-- 
=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~
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,

OPERATION_NOT_PERMITTED_FOR_CONTEXT

[Paulo Silva]

hi

i try to send block ip for campaing

* Preparing request to 
https://googleads.googleapis.com/v15/customers/5932574280/campaignCriteria:mutate
* Current time is 2024-03-25T14:40:47.850Z
* Enable automatic URL encoding
* Using default HTTP version
* Enable timeout of 3ms
* Enable SSL validation
* Enable cookie sending with jar of 12 cookies
* TLSv1.2 (IN), TLS header, Supplemental data (23):
* 17 bytes stray data read before trying h2 connection
* TLSv1.2 (OUT), TLS header, Supplemental data (23):
*   Trying 2800:3f0:4001:830::200a:443...
* Connected to googleads.googleapis.com (2800:3f0:4001:830::200a) port 443 
(#3)
* ALPN, offering h2
* ALPN, offering http/1.1
*  CAfile: /etc/ssl/cert.pem
* TLSv1.0 (OUT), TLS header, Certificate Status (22):
* TLSv1.3 (OUT), TLS handshake, Client hello (1):
* TLSv1.2 (IN), TLS header, Certificate Status (22):
* TLSv1.3 (IN), TLS handshake, Server hello (2):
* TLSv1.2 (IN), TLS header, Finished (20):
* TLSv1.2 (IN), TLS header, Supplemental data (23):
* TLSv1.3 (IN), TLS handshake, Encrypted Extensions (8):
* TLSv1.3 (IN), TLS handshake, Certificate (11):
* TLSv1.3 (IN), TLS handshake, CERT verify (15):
* TLSv1.3 (IN), TLS handshake, Finished (20):
* TLSv1.2 (OUT), TLS header, Finished (20):
* TLSv1.3 (OUT), TLS change cipher, Change cipher spec (1):
* TLSv1.2 (OUT), TLS header, Supplemental data (23):
* TLSv1.3 (OUT), TLS handshake, Finished (20):
* SSL connection using TLSv1.3 / TLS_AES_256_GCM_SHA384
* ALPN, server accepted to use h2
* Server certificate:
*  subject: CN=upload.video.google.com
*  start date: Feb 26 08:18:27 2024 GMT
*  expire date: May 20 08:18:26 2024 GMT
*  subjectAltName: host "googleads.googleapis.com" matched cert's 
"*.googleapis.com"
*  issuer: C=US; O=Google Trust Services LLC; CN=GTS CA 1C3
*  SSL certificate verify ok.
* Using HTTP2, server supports multiplexing
* Connection state changed (HTTP/2 confirmed)
* Copying HTTP/2 data in stream buffer to connection buffer after upgrade: 
len=0
* TLSv1.2 (OUT), TLS header, Supplemental data (23):
* TLSv1.2 (OUT), TLS header, Supplemental data (23):
* TLSv1.2 (OUT), TLS header, Supplemental data (23):
* Using Stream ID: 1 (easy handle 0x1040096f200)
* TLSv1.2 (OUT), TLS header, Supplemental data (23):

> POST /v15/customers/5932574280/campaignCriteria:mutate HTTP/2
> Host: googleads.googleapis.com
> user-agent: insomnia/8.6.1
> content-type: application/json
> accept: */*
> content-length: 170

* TLSv1.2 (OUT), TLS header, Supplemental data (23):

| 
{"customer_id":"5932574280","operations":[{"create":{"campaign":"customers/5932574280/campaigns/20717377421","negative":true,"ip_block":{"ip_address":"86.163.43.213"}}}]}

* We are completely uploaded and fine
* TLSv1.2 (IN), TLS header, Supplemental data (23):
* TLSv1.3 (IN), TLS handshake, Newsession Ticket (4):
* TLSv1.3 (IN), TLS handshake, Newsession Ticket (4):
* old SSL session ID is stale, removing
* TLSv1.2 (IN), TLS header, Supplemental data (23):
* TLSv1.2 (OUT), TLS header, Supplemental data (23):
* TLSv1.2 (IN), TLS header, Supplemental data (23):
* TLSv1.2 (IN), TLS header, Supplemental data (23):

< HTTP/2 400 
< request-id: InVoUjxhE7_vjMQaL09Pxw
< vary: X-Origin
< vary: Referer
< vary: Origin,Accept-Encoding
< content-type: application/json; charset=UTF-8
< date: Mon, 25 Mar 2024 14:40:48 GMT
< server: ESF
< cache-control: private
< x-xss-protection: 0
< x-frame-options: SAMEORIGIN
< x-content-type-options: nosniff
< alt-svc: h3=":443"; ma=2592000,h3-29=":443"; ma=2592000
< accept-ranges: none


* TLSv1.2 (IN), TLS header, Supplemental data (23):
* Received 998 B chunk
* TLSv1.2 (IN), TLS header, Supplemental data (23):
* Connection #3 to host googleads.googleapis.com left intact

but i receive this response

{
"error": {
"code": 400,
"message": "Request contains an invalid argument.",
"status": "INVALID_ARGUMENT",
"details": [
{
"@type": 
"type.googleapis.com/google.ads.googleads.v15.errors.GoogleAdsFailure",
"errors": [
{
"errorCode": {
"contextError": "OPERATION_NOT_PERMITTED_FOR_CONTEXT"
},
"message": "The operation is not allowed for the given context.",
"trigger": {
"stringValue": "EXPRESS(EXPRESS_SMART)"
},
"location": {
"fieldPathElements": [
{
"fieldName": "operations",
"index": 0
},
{
"fieldName": "create"
},
{
"fieldName": "ip_block"
}
]
}
}
],
"requestId": "InVoUjxhE7_vjMQaL09Pxw"
}
]
}
}

can i help me?

-- 
-- 
=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~
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 adwords-api@googlegroups.com
To unsubscribe from this group, send email to
adwords-api+unsubscr...@googlegroups.com
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 Ad

Accounts suspended issues

[Paulo Silva]

Hello, everyone!

Our product is designed to facilitate sales tracking on Google Ads for 
products from platforms like Clickbank, Buygoods, among others.

Our product is aimed at affiliates who use Google Ads as a platform for 
product advertising.

In practice, our users install our custom-generated code snippet on their 
landing pages, and through this snippet, we collect important information 
about the buyers and visitors of the ad.

Thus, we can generate detailed reports to enable the optimization of 
campaigns.

It happens that some of our users have reported having their accounts 
suspended after using our product.

I would like to know if there is any connection between the suspended 
accounts and our snippet.

Below, I insert the snippet code:

let filtripixel_trackingId = 0;
let filtripixel_pixelId = '';
let filtripixel_interactionEnabled = false;
let filtripixel_lastScrollPosition = 0;
let filtripixel_lastReportedScrollPercentage = 0;
let filtripixel_verify_installation = false;

function filtripixel_preventInteraction(event) {
if (!filtripixel_interactionEnabled) {
event.preventDefault();
event.stopPropagation();
}
}

function filtripixel_getTrackingId(params) {
const body = {
events: [
{
type: 'visit',
...params,
},
],
pixelId: filtripixel_pixelId,
};
const options = {
method: 'POST',
headers: {
'Content-Type': 'application/json',
},
body: JSON.stringify(body),
};

fetch('https://filtripixel.io', options)
.then((response) => response.json())
.then((response) => {
filtripixel_trackingId = response.trackingId;
filtripixel_setTrackingIdOnAllLinks(response.trackingId);
})
.catch((err) => {
filtripixel_interactionEnabled = true;
document.removeEventListener('click', filtripixel_preventInteraction, true);
});
}

function filtripixel_sendEvents(params, eventType) {
const body = {
trackingId: filtripixel_trackingId,
pixelId: filtripixel_pixelId,
events: [
{
type: eventType,
...params,
},
],
};
const options = {
method: 'POST',
headers: {
'Content-Type': 'application/json',
},
body: JSON.stringify(body),
};

fetch('https://filtripixel.io', options).catch((err) => {
filtripixel_interactionEnabled = true;
document.removeEventListener('click', filtripixel_preventInteraction, true);
});
}

function filtripixel_getParamsFromQueryString() {
const currentUrl = new URL(window.location.href);
const params = new URLSearchParams(currentUrl.search);
const visitParameters = {};

params.forEach((value, key) => {
visitParameters[key] = value;
if (key === 'filtripixel-installation-verify') {
if (value === filtripixel_pixelId) {
alert('Filtripixel instalado com sucesso');
}
}
});
filtripixel_getTrackingId(visitParameters);
}

function filtripixel_setTrackingIdOnAllLinks(trackingId) {
const links = document.querySelectorAll('a');
links.forEach((link) => {
if (link.href) {
try {
const linkUrl = new URL(link.href);
const params = ['tid', 'subid', 'sid1', 'sck', 'src'];
params.forEach((param) => {
linkUrl.searchParams.set(param, trackingId);
});
link.href = linkUrl.href;
filtripixel_interactionEnabled = true;
document.removeEventListener('click', filtripixel_preventInteraction, true);
const readyDiv = document.createElement('div');
readyDiv.id = 'filtripixel_is_ready';
readyDiv.style.display = 'none';
document.body.appendChild(readyDiv);
} catch (error) {
console.error(error);
}
}
});
}

function filtripixel_calculateScrollPercentage() {
const scrolled = window.scrollY;
const viewportHeight = window.innerHeight;
const fullHeight = document.documentElement.scrollHeight;
const scrolledPercentage = Math.min(((scrolled + viewportHeight) / 
fullHeight) * 100, 100);
return scrolledPercentage;
}

function filtripixel_handleScrollEvent() {
const currentScrollPosition = window.scrollY;
const currentScrollPercentage = filtripixel_calculateScrollPercentage();

const scrollDirection =
currentScrollPosition > filtripixel_lastScrollPosition ? 'scroll-down' : 
'scroll-up';

const reportingThreshold = 10;
if (
Math.abs(currentScrollPercentage - filtripixel_lastReportedScrollPercentage) 
>=
reportingThreshold
) {
filtripixel_sendEvents({ percentage: Math.round(currentScrollPercentage) }, 
scrollDirection);

filtripixel_lastReportedScrollPercentage = currentScrollPercentage;
}

filtripixel_lastScrollPosition = currentScrollPosition;
}

function filtripixel() {
filtripixel_getParamsFromQueryString();
document.addEventListener('click', function (event) {
let target = event.target;

while (target && target !== document.body && target.nodeName !== 'A') {
target = target.parentNode;
}

if (target && target.nodeName === 'A') {
const params = Array.from(target.attributes).reduce((acc, attr) => {
acc[attr.name] = attr.value;
return acc;
}, {});
filtripixel_sendEvents(params, 'click');
}
});
window.addEventListener('scroll', filtripixel_handleScrollEvent);
}

document.addEventListener('DOMContentLoaded', function () {
document.addEventListener('click', filtripixel_preventInteraction, true);
const scriptTags = document.getElementsByTagName('script');

Need Advice: No Response on Standard Access Application.

[Paulo Silva]

Hello Team, this is a 10 email about subject

Thank you for your email, we have submitted several applications, the last 
one around 2 weeks ago and we are still waiting to hear back.

MCC ID: 573-769-7662

We are blocked from servicing our existing customers and onboarding new 
customers due to this delay.
Is there any chance you can provide an update on the status of this?

Thank you in advance and best regards,

Paulo 

-- 
-- 
=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~
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 adwords-api@googlegroups.com
To unsubscribe from this group, send email to
adwords-api+unsubscr...@googlegroups.com
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 adwords-api+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/adwords-api/869073f0-6e52-4d2c-9c9b-3575aebdefb1n%40googlegroups.com.

NO_CONVERSION_ACTION_FOUND

[Paulo Silva]

Hi

i send to search API the request below

* Preparing request to 
https://googleads.googleapis.com/v15/customers/6328939997/googleAds:search
* Current time is 2024-06-10T23:36:30.508Z
* Enable automatic URL encoding
* Using default HTTP version
* Enable timeout of 3ms
* Enable SSL validation
* Enable cookie sending with jar of 15 cookies
* Too old connection (228 seconds), disconnect it
* Connection 257 seems to be dead!
* Closing connection 257
* TLSv1.2 (OUT), TLS header, Supplemental data (23):
* TLSv1.3 (OUT), TLS alert, close notify (256):
* Hostname in DNS cache was stale, zapped
*   Trying 2800:3f0:4001:818::200a:443...
* Connected to googleads.googleapis.com (2800:3f0:4001:818::200a) port 443 
(#258)
* ALPN, offering h2
* ALPN, offering http/1.1
*  CAfile: /etc/ssl/cert.pem
* TLSv1.0 (OUT), TLS header, Certificate Status (22):
* TLSv1.3 (OUT), TLS handshake, Client hello (1):
* TLSv1.2 (IN), TLS header, Certificate Status (22):
* TLSv1.3 (IN), TLS handshake, Server hello (2):
* TLSv1.2 (IN), TLS header, Finished (20):
* TLSv1.2 (IN), TLS header, Supplemental data (23):
* TLSv1.3 (IN), TLS handshake, Encrypted Extensions (8):
* TLSv1.3 (IN), TLS handshake, Certificate (11):
* TLSv1.3 (IN), TLS handshake, CERT verify (15):
* TLSv1.3 (IN), TLS handshake, Finished (20):
* TLSv1.2 (OUT), TLS header, Finished (20):
* TLSv1.3 (OUT), TLS change cipher, Change cipher spec (1):
* TLSv1.2 (OUT), TLS header, Supplemental data (23):
* TLSv1.3 (OUT), TLS handshake, Finished (20):
* SSL connection using TLSv1.3 / TLS_AES_256_GCM_SHA384
* ALPN, server accepted to use h2
* Server certificate:
*  subject: CN=upload.video.google.com
*  start date: May 21 06:28:35 2024 GMT
*  expire date: Aug 13 06:28:34 2024 GMT
*  subjectAltName: host "googleads.googleapis.com" matched cert's 
"*.googleapis.com"
*  issuer: C=US; O=Google Trust Services LLC; CN=GTS CA 1C3
*  SSL certificate verify ok.
* Using HTTP2, server supports multiplexing
* Connection state changed (HTTP/2 confirmed)
* Copying HTTP/2 data in stream buffer to connection buffer after upgrade: 
len=0
* TLSv1.2 (OUT), TLS header, Supplemental data (23):
* TLSv1.2 (OUT), TLS header, Supplemental data (23):
* TLSv1.2 (OUT), TLS header, Supplemental data (23):
* Using Stream ID: 1 (easy handle 0x114008c0800)
* TLSv1.2 (OUT), TLS header, Supplemental data (23):

> POST /v15/customers/6328939997/googleAds:search HTTP/2
> Host: googleads.googleapis.com
> user-agent: insomnia/9.2.0
> content-type: application/json
> developer-token: 
> authorization: Bearer ---
> accept: */*
> content-length: 322

* TLSv1.2 (OUT), TLS header, Supplemental data (23):

| {
| "query":" SELECT conversion_action.id,conversion_action.name, 
conversion_action.type, conversion_action.category, 
conversion_action.status, 
conversion_action.type,conversion_action.counting_type, 
conversion_action.owner_customer  FROM conversion_action"
| }

* We are completely uploaded and fine
* TLSv1.2 (IN), TLS header, Supplemental data (23):
* TLSv1.3 (IN), TLS handshake, Newsession Ticket (4):
* TLSv1.3 (IN), TLS handshake, Newsession Ticket (4):
* old SSL session ID is stale, removing
* TLSv1.2 (IN), TLS header, Supplemental data (23):
* TLSv1.2 (OUT), TLS header, Supplemental data (23):
* TLSv1.2 (IN), TLS header, Supplemental data (23):
* TLSv1.2 (IN), TLS header, Supplemental data (23):

< HTTP/2 200 
< request-id: s2pDv8bufN2TIR_7XFOgZw
< content-type: application/json; charset=UTF-8
< vary: X-Origin
< vary: Referer
< vary: Origin,Accept-Encoding
< date: Mon, 10 Jun 2024 23:36:31 GMT
< server: ESF
< cache-control: private
< x-xss-protection: 0
< x-frame-options: SAMEORIGIN
< x-content-type-options: nosniff
< alt-svc: h3=":443"; ma=2592000,h3-29=":443"; ma=2592000
< accept-ranges: none


* TLSv1.2 (IN), TLS header, Supplemental data (23):
* Received 644 B chunk
* TLSv1.2 (IN), TLS header, Supplemental data (23):
* Connection #258 to host googleads.googleapis.com left intact

and receive this result

{
"results": [
{
"conversionAction": {
"resourceName": "customers/6328939997/conversionActions/6819728058",
"status": "ENABLED",
"type": "UPLOAD_CLICKS",
"category": "PURCHASE",
"countingType": "MANY_PER_CLICK",
"id": "*6819728058*",
"name": "GlucoFreedom",
"ownerCustomer": "customers/*6328939997*"
}
}
],
"fieldMask": 
"conversionAction.id,conversionAction.name,conversionAction.type,conversionAction.category,conversionAction.status,conversionAction.type,conversionAction.countingType,conversionAction.ownerCustomer",
"queryResourceConsumption": "909"
}

note the resource name that is returned

*customers/6328939997/conversionActions/6819728058*

when i try to send to upload click api (request below)
* Preparing request to 
https://googleads.googleapis.com/v15/customers/6328939997:uploadClickConversions
* Current time is 2024-06-10T23:21:46.120Z
* Enable automatic URL encoding
* Using default HTTP version
* Enable timeout of 3ms
* Enable

Re: the standard access request urgent

[Paulo Silva]

We are really frustrated. We have already filled out this form twice, and 
honestly, it's hard not to feel disheartened. We've noticed that others on 
this forum receive immediate support by simply providing their MCC, while 
we are being told to fill out the form again, for the third time.

I don't want to believe that there is any kind of prejudice involved, but 
it's hard not to notice that those who seem to receive quicker assistance 
are Americans and Europeans. As Latinos, we are not asking for special 
treatment, just equality. It is painful to feel like we are being treated 
differently. Please help us resolve this situation with the same 
consideration and speed that is offered to others.

On Wednesday, March 6, 2024 at 8:41:35 AM UTC-3 Google Ads API Forum 
Advisor wrote:

> Hi,
>
> Thank you for reaching out to the Google Ads API support team.
>
> By reviewing your query, I understand that your concern is regarding the 
> Google Ads API developer token.
>
> To apply for a standard access level developer token, I would recommend 
> you to fill out the standard access application form 
> . 
> You may check this documentation on standard access 
> 
>  
> for more information. Once you fill the standard access application form, 
> the compliance team will send you an email regarding your application.
>   
> This message is in relation to case "ref:!00D1U01174p.!5004Q02rziWj:ref"
>
> Thanks,
>   
> [image: Google Logo] Google Ads API Team 
>
>
>

-- 
-- 
=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~
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 adwords-api@googlegroups.com
To unsubscribe from this group, send email to
adwords-api+unsubscr...@googlegroups.com
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 adwords-api+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/adwords-api/720f136b-f254-474c-afe7-57c294e11e22n%40googlegroups.com.

Re: the standard access request urgent

[Paulo Silva]

some news?

On Monday, June 17, 2024 at 5:50:45 PM UTC-3 Google Ads API Forum Advisor 
wrote:

> Hi,
>
> From the earlier conversations, it appears that the compliance team has 
> proceeded with your access request in the ticket 3-589036293. Could you 
> please confirm if this concern is related to the mentioned ticket.
>   
>
>
> *This message is in relation to case "ref:!00D1U01174p.!5004Q02rziWj:ref" 
> (ADR-00226179) Thanks,*
>
>   
> [image: Google Logo] *Google Ads API Team* 
> *Register 
>  for 
> the upcoming workshop: Performance Max and the Google Ads API!*
>  
>
>
>

-- 
-- 
=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~
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 adwords-api@googlegroups.com
To unsubscribe from this group, send email to
adwords-api+unsubscr...@googlegroups.com
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 adwords-api+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/adwords-api/c6dd4bab-0688-4630-af19-6aa428c0bf84n%40googlegroups.com.

Urgent! conversions are not showing up for users in the Google Ads dashboard

[Paulo Silva]

Some users on my platform are not seeing the conversions sent since 
yesterday. Normally they view conversions in 4 hours but since yesterday at 
18:00 (UTC -3), the Google API responds that it has successfully received 
the conversion but they are not displayed. Can anyone tell me about it?

-- 
-- 
=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~
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 adwords-api@googlegroups.com
To unsubscribe from this group, send email to
adwords-api+unsubscr...@googlegroups.com
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 adwords-api+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/adwords-api/6805c01c-8dbc-4fb9-8a0f-fe33d0f09c78n%40googlegroups.com.

api token

[Paulo Silva]

It's been over a month since I submitted my request to have a basic API and 
no one has given us any position. Can someone help me?

-- 
-- 
=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~
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 adwords-api@googlegroups.com
To unsubscribe from this group, send email to
adwords-api+unsubscr...@googlegroups.com
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 adwords-api+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/adwords-api/d43ec119-4825-4ac4-b7df-562e343bb77fn%40googlegroups.com.

Ads API Basic Access

[Paulo Silva]

Hello team,
We have applied *Ads API Basic access*,  I have not received response from 
support, could u help us find the status of our apply?
MCC: 573-769-7662

Thanks!!!

-- 
-- 
=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~
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 adwords-api@googlegroups.com
To unsubscribe from this group, send email to
adwords-api+unsubscr...@googlegroups.com
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 adwords-api+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/adwords-api/a9aae9e8-eaa4-47ed-93f4-97e513fc0832n%40googlegroups.com.

gclid and keyword

[Paulo Silva]

Hi,

If I build an ad like meusite.com?keyword={keyword}, Google will replace 
the key {keyword} when redirecting to my website with the word used to 
reach that ad, correct?

If this is right, is it possible to make a query via api (select ... from 
click_view perhaps?) to obtain this same information?

If so, can anyone provide me with an example?

-- 
-- 
=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~
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 adwords-api@googlegroups.com
To unsubscribe from this group, send email to
adwords-api+unsubscr...@googlegroups.com
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 adwords-api+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/adwords-api/5b550a48-f225-4f18-b0d4-9367130055f7n%40googlegroups.com.

status of jobid for uploadclicks

[Paulo Silva]

it's possible consulting the status of job for uploadclicks?
if yes, someone send me a example?

-- 
-- 
=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~
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 adwords-api@googlegroups.com
To unsubscribe from this group, send email to
adwords-api+unsubscr...@googlegroups.com
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 adwords-api+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/adwords-api/964e322e-785f-47b5-9824-bb110130c8bfn%40googlegroups.com.

Re: status of jobid for uploadclicks

[Paulo Silva]

I have a very strange situation... one of my clients made 3 uploads through 
our automation but he can only view one of them on his dashboard.

I now looked at the query you gave me (thanks for the query) and all the 
jobs are marked as success.

Could you help me investigate?

On Friday, February 16, 2024 at 10:00:42 AM UTC-3 Google Ads API Forum 
Advisor wrote:

> Hi,
>
> Thank you for reaching out to the Google Ads API support team.
>
> By reviewing your concern, I understand that you need information 
> regarding the status of the job for upload clicks.
>
> You can use the Google Ads API to retrieve offline data diagnostics 
> , which contain 
> information about the overall health of your conversion upload and 
> adjustment processes. To retrieve the latest offline data diagnostics for 
> your account, send the following query 
> for offline_conversion_upload_client_summary resources using the 
> GoogleAdsService 
> .
>  
> I would suggest you to refer to this guide Monitor offline data 
> diagnostics 
> 
>  for 
> more information.
>
> You can use the below query: 
>
>- Query: "SELECT customer.id, 
>offline_conversion_upload_client_summary.alerts, 
>offline_conversion_upload_client_summary.client, 
>offline_conversion_upload_client_summary.daily_summaries, 
>offline_conversion_upload_client_summary.job_summaries, 
>offline_conversion_upload_client_summary.last_upload_date_time, 
>offline_conversion_upload_client_summary.resource_name, 
>offline_conversion_upload_client_summary.status, 
>offline_conversion_upload_client_summary.success_rate, 
>offline_conversion_upload_client_summary.successful_event_count, 
>offline_conversion_upload_client_summary.total_event_count FROM 
>offline_conversion_upload_client_summary" 
>
>
> You can try making a request using the Method: customers.googleAds.search 
> 
> .
>
> Also, you can use Query Builder 
> 
>  to 
> create your query and Query Validator 
>  to 
> validate your query.
>
> I would recommend you to check this help center article Conversion 
> Tracking: Troubleshooting conversion tracking status 
>  for 
> more information.
>   
> This message is in relation to case "ref:!00D1U01174p.!5004Q02rzBFp:ref"
>
> Thanks,
>   
> [image: Google Logo] Google Ads API Team 
>
>
>  
>
>

-- 
-- 
=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~
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 adwords-api@googlegroups.com
To unsubscribe from this group, send email to
adwords-api+unsubscr...@googlegroups.com
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 adwords-api+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/adwords-api/36f32eef-7a64-4077-9f4f-3da827d3bdb6n%40googlegroups.com.

Re: status of jobid for uploadclicks

[Paulo Silva]

It has been more than 24 hours and no information is displayed. The only 
difference between the events that are not being displayed is that instead 
of sending gclid I sent gbraid. Does this affect the result?

On Friday, February 16, 2024 at 7:57:47 PM UTC-3 Google Ads API Forum 
Advisor wrote:

> Hi,
>
> Thank you for getting back to us.
>
> Kindly note that uploaded conversions can take up to 24 hours for 
> conversions to show up in Google Ads, depending on the attribution model 
> you are using. Please refer to this article About data freshness 
>  for more 
> information.
>
>
>   
> This message is in relation to case "ref:!00D1U01174p.!5004Q02rzBFp:ref"
>
> Thanks,
>   
> [image: Google Logo] Google Ads API Team 
>
>
>

-- 
-- 
=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~
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 adwords-api@googlegroups.com
To unsubscribe from this group, send email to
adwords-api+unsubscr...@googlegroups.com
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 adwords-api+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/adwords-api/b29a3c39-f264-4f4e-8dfb-2b6d1dfed1a5n%40googlegroups.com.

Re: status of jobid for uploadclicks

[Paulo Silva]

It has been more than 96 hours and the data does not appear on my client's 
dashboard. Is there nothing you can do to investigate?

On Monday, February 19, 2024 at 12:54:18 AM UTC-3 Google Ads API Forum 
Advisor wrote:

> Hello,
>
>
> Thank you for getting back to us.
>
> I would like to inform you that sometimes the data upload will get 
> delayed. You may refer to this link 
> 
>  
> regarding how it works. No, sending gbraid instead of the gclid won't cause 
> any issue.
>
> Hope this helps. For any other assistance you may get back to us.
>
>   
> This message is in relation to case "ref:!00D1U01174p.!5004Q02rzBFp:ref"
>
> Thanks,
>   
> [image: Google Logo] Google Ads API Team 
>
>
>

-- 
-- 
=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~
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 adwords-api@googlegroups.com
To unsubscribe from this group, send email to
adwords-api+unsubscr...@googlegroups.com
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 adwords-api+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/adwords-api/f43ee5a4-9461-4866-9cd9-f1ee7f8d4593n%40googlegroups.com.

AdWords API Re: .Net API - impossible mission

[Paulo Silva]

The exception has only "Fault occurred while processing."




2009/5/18 silvapaulo...@gmail.com 

> Hi,
>
> I am trying to use the new v200902 API with the sandbox, it seems to
> be impossible. I've tried to execute the samples from:
>
> http://code.google.com/p/adwords-api-dotnet-samples/downloads/list
>
> awapi2009_csharp_samples.zip
>
> and
>
> http://code.google.com/p/google-api-adwords-dotnet/
>
> awapi_dotnet_lib_3.0.0.tar.gz
>
> Those examples are not working, I don't know what I am doing wrong.
>
> Someone knows how to test the new sandbox? What are the steps?
>
> thanks !

--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups 
"AdWords API Forum" group.
To post to this group, send email to adwords-api@googlegroups.com
To unsubscribe from this group, send email to 
adwords-api+unsubscr...@googlegroups.com
For more options, visit this group at 
http://groups.google.com/group/adwords-api?hl=en
-~--~~~~--~~--~--~---

AdWords API Re: .Net API - impossible mission

[Paulo Silva]

Hi,

Ok, So... please can you take a look in the log attached?



thank you in advance.


2009/5/19 AdWords API Advisor 

>
> Hello Paulo,
>
>  Unfortunately, the SOAP faults currently returned by the v200902 API
> leave much to be desired. What would be most helpful is if you could
> turn on logging of your SOAP requests and let us see what you're SOAP
> request XML looks like (with your auth token and client email X-ed
> out).
>
> Cheers,
> -Jeff Posnick, AdWords API Team
>
>
> On May 18, 8:08 pm, "silvapaulo...@gmail.com"
>   wrote:
> > Hi,
> >
> > I am trying to use the new v200902 API with the sandbox, it seems to
> > be impossible. I've tried to execute the samples from:
> >
> > http://code.google.com/p/adwords-api-dotnet-samples/downloads/list
> >
> > awapi2009_csharp_samples.zip
> >
> > and
> >
> > http://code.google.com/p/google-api-adwords-dotnet/
> >
> > awapi_dotnet_lib_3.0.0.tar.gz
> >
> > Those examples are not working, I don't know what I am doing wrong.
> >
> > Someone knows how to test the new sandbox? What are the steps?
> >
> > thanks !
> >
>

--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups 
"AdWords API Forum" group.
To post to this group, send email to adwords-api@googlegroups.com
To unsubscribe from this group, send email to 
adwords-api+unsubscr...@googlegroups.com
For more options, visit this group at 
http://groups.google.com/group/adwords-api?hl=en
-~--~~~~--~~--~--~---



com.google.api.adwords.v200902.CampaignService.CampaignService.log
Description: Binary data

AdWords API Re: .Net API - impossible mission

[Paulo Silva]

Maybe the soap errors messages could have more meaning.


thanks

2009/5/19 Paulo Silva 

> Hi,
>
> Ok, So... please can you take a look in the log attached?
>
>
>
> thank you in advance.
>
>
> 2009/5/19 AdWords API Advisor 
>
>
>> Hello Paulo,
>>
>>  Unfortunately, the SOAP faults currently returned by the v200902 API
>> leave much to be desired. What would be most helpful is if you could
>> turn on logging of your SOAP requests and let us see what you're SOAP
>> request XML looks like (with your auth token and client email X-ed
>> out).
>>
>> Cheers,
>> -Jeff Posnick, AdWords API Team
>>
>>
>> On May 18, 8:08 pm, "silvapaulo...@gmail.com"
>>   wrote:
>> > Hi,
>> >
>> > I am trying to use the new v200902 API with the sandbox, it seems to
>> > be impossible. I've tried to execute the samples from:
>> >
>> > http://code.google.com/p/adwords-api-dotnet-samples/downloads/list
>> >
>> > awapi2009_csharp_samples.zip
>> >
>> > and
>> >
>> > http://code.google.com/p/google-api-adwords-dotnet/
>> >
>> > awapi_dotnet_lib_3.0.0.tar.gz
>> >
>> > Those examples are not working, I don't know what I am doing wrong.
>> >
>> > Someone knows how to test the new sandbox? What are the steps?
>> >
>> > thanks !
>> >>
>>
>

--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups 
"AdWords API Forum" group.
To post to this group, send email to adwords-api@googlegroups.com
To unsubscribe from this group, send email to 
adwords-api+unsubscr...@googlegroups.com
For more options, visit this group at 
http://groups.google.com/group/adwords-api?hl=en
-~--~~~~--~~--~--~---

AdWords API Re: .Net API - impossible mission

[Paulo Silva]

I am debugging your code and I realized that you are creating the v13
headers:


private SoapHeader MakeHeader(string headerName, string value) {

string typeName = "com.google.api.adwords.v13." + headerName;

Even I called the v2009 service is it correct ?



2009/5/19 Paulo Silva 

> Maybe the soap errors messages could have more meaning.
>
>
> thanks
>
> 2009/5/19 Paulo Silva 
>
>  Hi,
>>
>> Ok, So... please can you take a look in the log attached?
>>
>>
>>
>> thank you in advance.
>>
>>
>> 2009/5/19 AdWords API Advisor 
>>
>>
>>> Hello Paulo,
>>>
>>>  Unfortunately, the SOAP faults currently returned by the v200902 API
>>> leave much to be desired. What would be most helpful is if you could
>>> turn on logging of your SOAP requests and let us see what you're SOAP
>>> request XML looks like (with your auth token and client email X-ed
>>> out).
>>>
>>> Cheers,
>>> -Jeff Posnick, AdWords API Team
>>>
>>>
>>> On May 18, 8:08 pm, "silvapaulo...@gmail.com"
>>>   wrote:
>>> > Hi,
>>> >
>>> > I am trying to use the new v200902 API with the sandbox, it seems to
>>> > be impossible. I've tried to execute the samples from:
>>> >
>>> > http://code.google.com/p/adwords-api-dotnet-samples/downloads/list
>>> >
>>> > awapi2009_csharp_samples.zip
>>> >
>>> > and
>>> >
>>> > http://code.google.com/p/google-api-adwords-dotnet/
>>> >
>>> > awapi_dotnet_lib_3.0.0.tar.gz
>>> >
>>> > Those examples are not working, I don't know what I am doing wrong.
>>> >
>>> > Someone knows how to test the new sandbox? What are the steps?
>>> >
>>> > thanks !
>>> >>>
>>>
>>
>

--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups 
"AdWords API Forum" group.
To post to this group, send email to adwords-api@googlegroups.com
To unsubscribe from this group, send email to 
adwords-api+unsubscr...@googlegroups.com
For more options, visit this group at 
http://groups.google.com/group/adwords-api?hl=en
-~--~~~~--~~--~--~---

AdWords API Re: .Net API - impossible mission

[Paulo Silva]

But here it is written as optional:

http://code.google.com/apis/adwords/docs/developer/adwords_api_sandbox.html#top
I put the cliemEmail and still not working

I am debugging your code and I realized that you are creating the v13
soap headers, even I called the v2009 service:

 private SoapHeader MakeHeader(string headerName, string value) {
string typeName = "com.google.api.adwords.v13." + headerName;

is it correct ?



2009/5/19 AdWords API Advisor 

>
> Hello,
>
>  The issue is that you're not specifying anything for the clientEmail
> header. The header has the same sort of value as the v13 Sandbox
> supports, i.e. "client_1+u...@domain.com ",
> where "u...@domain.com" is
> your Google Account email address.
>
>  The errors definitely should be more descriptive, and this will
> hopefully happen before we reach the full Production release.
>
> Cheers,
> -Jeff Posnick, AdWords API Team
>
>
> On May 19, 4:34 pm, Paulo Silva  wrote:
> > I am debugging your code and I realized that you are creating the v13
> > headers:
> >
> > private SoapHeader MakeHeader(string headerName, string value) {
> >
> > string typeName = "com.google.api.adwords.v13." + headerName;
> >
> > Even I called the v2009 service is it correct ?
> >
> > 2009/5/19 Paulo Silva 
> >
> > > Maybe the soap errors messages could have more meaning.
> >
> > > thanks
> >
> > > 2009/5/19 Paulo Silva 
> >
> > >  Hi,
> >
> > >> Ok, So... please can you take a look in the log attached?
> >
> > >> thank you in advance.
> >
> > >> 2009/5/19 AdWords API Advisor 
>  >
> > >>> Hello Paulo,
> >
> > >>>  Unfortunately, the SOAP faults currently returned by the v200902 API
> > >>> leave much to be desired. What would be most helpful is if you could
> > >>> turn on logging of your SOAP requests and let us see what you're SOAP
> > >>> request XML looks like (with your auth token and client email X-ed
> > >>> out).
> >
> > >>> Cheers,
> > >>> -Jeff Posnick, AdWords API Team
> >
> > >>> On May 18, 8:08 pm, "silvapaulo...@gmail.com"
> > >>>   wrote:
> > >>> > Hi,
> >
> > >>> > I am trying to use the new v200902 API with the sandbox, it seems
> to
> > >>> > be impossible. I've tried to execute the samples from:
> >
> > >>> >http://code.google.com/p/adwords-api-dotnet-samples/downloads/list
> >
> > >>> > awapi2009_csharp_samples.zip
> >
> > >>> > and
> >
> > >>> >http://code.google.com/p/google-api-adwords-dotnet/
> >
> > >>> > awapi_dotnet_lib_3.0.0.tar.gz
> >
> > >>> > Those examples are not working, I don't know what I am doing wrong.
> >
> > >>> > Someone knows how to test the new sandbox? What are the steps?
> >
> > >>> > thanks !
> >
> >
> >
>

--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups 
"AdWords API Forum" group.
To post to this group, send email to adwords-api@googlegroups.com
To unsubscribe from this group, send email to 
adwords-api+unsubscr...@googlegroups.com
For more options, visit this group at 
http://groups.google.com/group/adwords-api?hl=en
-~--~~~~--~~--~--~---

429 Resource has been exhausted | Too many requests. Retry in 30 seconds

[Paulo Silva]

Hi,

I have been using the Google Ads HistoricalMetrics API quite successfully 
for the last few months. However, ever since this morning, I notice an 
increased error rate with the following message:

An error occurred: 429 Resource has been exhausted (e.g. check quota). 
[type_url: "
type.googleapis.com/google.ads.googleads.v17.errors.GoogleAdsFailure"

I am pretty sure I am following the needed limits. Is there an issue with 
the rate limiter perhaps? I notice that there's no defined outage in the 
dasboard, but can someone confirm if I am the only one with this issue?

https://ads.google.com/status/publisher

-- 
-- 
=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~
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 adwords-api@googlegroups.com
To unsubscribe from this group, send email to
adwords-api+unsubscr...@googlegroups.com
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 adwords-api+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/adwords-api/27ae64fc-02f0-4a6b-a70f-c57168848cfbn%40googlegroups.com.

timeout: listAccessibleCustomers

[Paulo Silva]

i try to access the method 
https://googleads.googleapis.com/v19/customers:listAccessibleCustomers

*But i receive the timeout response*

* Preparing request to 
https://googleads.googleapis.com/v19/customers:listAccessibleCustomers
* Current time is 2025-07-02T17:58:27.073Z
* Enable automatic URL encoding
* Using default HTTP version
* Enable timeout of 3ms
* Enable SSL validation
* Enable cookie sending with jar of 49 cookies
* Found bundle for host: 0x11406892800 [can multiplex]
* Re-using existing connection #276 with host googleads.googleapis.com
* Connected to googleads.googleapis.com (2800:3f0:4001:80a::200a) port 443 
(#276)
* h2h3 [:method: GET]
* h2h3 [:path: /v19/customers:listAccessibleCustomers]
* h2h3 [:scheme: https]
* h2h3 [:authority: googleads.googleapis.com]
* h2h3 [developer-token: removed for security reasons]
* h2h3 [authorization: Bearer removed for security reasons]
* h2h3 [accept: */*]
* Using Stream ID: 3 (easy handle 0x11400a21e00)
* TLSv1.2 (OUT), TLS header, Supplemental data (23):

> GET /v19/customers:listAccessibleCustomers HTTP/2
> Host: googleads.googleapis.com
> developer-token: litD5RA_CgW3FMlCnb7mTw
> authorization: Bearer 
ya29.a0AS3H6Ny_ulVuegQQ5rhfZ1A7QnzAElPIQ0LJvjukVRzwxIFhdUYg20JOJtFe_4wn5P4v7vB71gsq39UDcvKShpTodveuJ94C5-QoeJBRVJu6ZCfvuBiZnwIVQQcKrKYLEuDChO0-WZuf0fAXCq8fNHh43YYmU5wxpgKA4TItIuQaCgYKAbkSARMSFQHGX2MiogP3Dqd_0IlDj9m6OzqROQ0178
> accept: */*

* Operation timed out after 30005 milliseconds with 0 bytes received
* TLSv1.2 (OUT), TLS header, Supplemental data (23):
* Connection #276 to host googleads.googleapis.com left intact

-- 
-- 
=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~
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 adwords-api@googlegroups.com
To unsubscribe from this group, send email to
adwords-api+unsubscr...@googlegroups.com
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 adwords-api+unsubscr...@googlegroups.com.
To view this discussion visit 
https://groups.google.com/d/msgid/adwords-api/e5af771f-d1ed-4553-9ec5-b2904ccf79d7n%40googlegroups.com.