-
Notifications
You must be signed in to change notification settings - Fork 10
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
GADS_SSI error #166
Comments
Hi @jbrs360, sorry for the delay coming back to you. Can you provide the smallest set of columns that allow you to reproduce this error? I will investigate the issue and get back to you by the end of this week. |
Sure, no problem. I've attached the schema and a test row from the dummy
data.
The customer_id and conversion_action_id is however correct for the clients DK market
account.
[image: image.png]
[image: image.png]
…On Tue, 4 Jun 2024 at 15:23, Caio Tomazelli ***@***.***> wrote:
Hi @jbrs360 <https://github.com/jbrs360>, sorry for the delay coming back
to you.
Can you provide the smallest set of columns that allow you to reproduce
this error?
I will investigate the issue and get back to you by the end of this week.
—
Reply to this email directly, view it on GitHub
<#166 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/BACDVNZB2HQDD6ZTMFGT7RTZFW5W3AVCNFSM6AAAAABHX55KWOVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDCNBXGUZDQOBYGQ>
.
You are receiving this because you were mentioned.Message ID:
***@***.***>
|
Hi Jacob, I was able to reproduce. In my case, the error was related to SSI not being allowed in the target account:
Notice how Tightlock was exposing only the StatusCode ("invalid argument"). I sent PR #169 to better expose the error message. As SSI requires a manual register step to be allowed, make sure you followed these steps for the target account: https://support.google.com/google-ads/answer/9995886?sjid=9733441823520280530-SA#eligibility In case your account is already allow-listed, you can retry with the new version (once the PR mentioned above is merged) to see the specific error message you're getting in your case. Hope this helps! |
Thank you Caio for the swift answer!
Sounds odd. Before we started using Tightlock we tried to build a cloud
function with code from Google's developer docs
<https://developers.google.com/google-ads/api/docs/conversions/upload-store-sales-transactions#code_example>
and got it to work until we hit some API limits.
However, we got it to work successfully with the provided ids.
I've reached out to Grace again just for confirmation. Do you think the
error could be of something else?
…On Tue, 4 Jun 2024 at 18:44, Caio Tomazelli ***@***.***> wrote:
Hi Jacob, I was able to reproduce.
In my case, the error was related to SSI not being allowed in the target
account:
>, <_InactiveRpcError of RPC that terminated with:
status = StatusCode.INVALID_ARGUMENT
details = "Request contains an invalid argument."
debug_error_string = "UNKNOWN:Error received from peer ipv4:173.194.212.95:443 {grpc_message:"Request contains an invalid argument.", grpc_status:3, created_time:"2024-06-04T16:35:47.152425085+00:00"}"
>, errors {
error_code {
offline_user_data_job_error: NOT_ON_ALLOWLIST_FOR_STORE_SALES_DIRECT
}
Notice how Tightlock was exposing only the StatusCode ("invalid
argument"). I sent PR #169
<#169> to
better expose the error message.
As SSI requires a manual register step to be allowed, make sure you
followed these steps for the target account:
https://support.google.com/google-ads/answer/9995886?sjid=9733441823520280530-SA#eligibility
In case your account is already allow-listed, you can retry with the new
version (once the PR mentioned above is merged) to see the specific error
message you're getting in your case.
Hope this helps!
—
Reply to this email directly, view it on GitHub
<#166 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/BACDVN5VG6NVSBXU2BPWQZTZFXVHJAVCNFSM6AAAAABHX55KWOVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDCNBXHE3TMMJYGQ>
.
You are receiving this because you were mentioned.Message ID:
***@***.***>
|
Hey Jacob, If you already tested before, this might be something else. I just merged the changes, so the proper error should be exposed now. Please redeploy and test again and feel free to reopen the issue if you still can't figure it out with the improved error message. |
Hi Caio, I've started from scratch and created a new connection with a new data source and destination. I'm still getting the INVALID_ARGUMENT error when running the connection. I don't see any new or improved error message. |
Hi Jacob, Just confirming: Have you redeployed your Tightlock backend with the latest version (merged on June 5)? The change we made to the SSI connector (Line 120) should show you a more detailed version. So either your version is not updated or the API is not providing a detailed description of the problem. Unfortunately I'm not able to debug the problem directly with your account, so I'll wait for your confirmation before investigating further. |
Hey Jacob, Looks like the only thing that is missing now is at least one user identifier. Even though there is no single identifier that is required, you need to provide at least one of: email, telephone or address. |
Thanks for confirming, I'm trying to reproduce and see if I can investigate this in some other way, I'll keep you posted. In the meantime, if I were to implement a custom debug version to investigate this issue, would you be willing to deploy it? Since I'm struggling to get access to an account that is enabled to use SSI, I might rely on your testing to get this fixed, if you are interested in helping out. |
Yes, sure, we could make that happen.
…On Thu, 20 Jun 2024 at 20:08, Caio Tomazelli ***@***.***> wrote:
Thanks for confirming,
I'm trying to reproduce and see if I can investigate this in some other
way, I'll keep you posted.
In the meantime, if I were to implement a custom debug version to
investigate this issue, would you be willing to deploy it? Since I'm
struggling to get access to an account that is enabled to use SSI, I might
rely on your testing to get this fixed, if you are interested in helping
out.
—
Reply to this email directly, view it on GitHub
<#166 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/BACDVN4PMW4XAPVWQ2Z5LJDZIMLDNAVCNFSM6AAAAABHX55KWOVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDCOBRGI2TOMRYHE>
.
You are receiving this because you were mentioned.Message ID:
***@***.***>
|
Hi Jacob, I was able to get access to an SSI enabled account and I was able to send conversions through with this minimal example:
I found a bug in the way related to the optional That said, this parameter is only optional if you have not set it up in your Ads account. All that being said, can you provide additional information about the error you're getting, since I was not able to reproduce? If you can also provide redacted information about the setup of your destination (i.e. if you are providing all the required fields in the UI) that would be great. I'm still trying to find a good way to debug remotely...one option would be for you to temporarily invite me ([email protected]) to your Ads account, so that I can try sending a test hit and see if I can reproduce the problem. |
Hi Caio,
I unfortunately can't give you access without discussing this with our
client.
At the moment we don't receive any error message. Below you will see the
latest run together with the first row of the data we're sending. No custom
keys are sent with it. I've manually created the schema to match with the
requirements.
[image: image.png]
[image: image.png]
…On Fri, 21 Jun 2024 at 20:05, Caio Tomazelli ***@***.***> wrote:
Hi Jacob,
I was able to get access to an SSI enabled account and I was able to send
conversions through with this minimal example:
id,customer_id,conversion_action_id,conversion_date_time,conversion_micro_value,email
1,XXXXX,YYYYYY,2024-06-18 ***@***.***
2,XXXXX,YYYYYY,2024-06-18 ***@***.***
I found a bug in the way related to the optional custom_key parameter (PR
#175 <#175> ).
That said, this parameter is only optional if you have not set it up in
your Ads account.
All that being said, can you provide additional information about the
error you're getting, since I was not able to reproduce? If you can also
provide redacted information about the setup of your destination (i.e. if
you are providing all the required fields in the UI) that would be great.
I'm still trying to find a good way to debug remotely...one option would
be for you to temporarily invite me ***@***.***) to your
Ads account, so that I can try sending a test hit and see if I can
reproduce the problem.
—
Reply to this email directly, view it on GitHub
<#166 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/BACDVNZCM5ULGOXZ2SZIHI3ZIRTQLAVCNFSM6AAAAABHX55KWOVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDCOBTGIYDMNBVGA>
.
You are receiving this because you were mentioned.Message ID:
***@***.***>
|
Hey Jacob, I can't see the images when they come from email attachments. Can you post them directly in Github? Thanks! |
Hi Jacob, Can you send me the full error log you are getting? I'm trying to query the log database for "The required field was not present." with no luck, so it would be good to have more details. |
How do I get the full error log? The interface does not return any. |
If you can provide a screenshot of the error you're getting in the interface (the "The required field was not present." that you mentioned) that would already be useful. If you want to have the full log, you can:
I understand that these troubleshooting steps are complicated, but for now there is no other way to see them unfortunately. Simplifying this flow is currently in our roadmap though. |
Thanks for the update Jacob! This is definitely a bug. I'll keep this issue open as I investigate. Thanks again for your patience here and for the help while troubleshooting the issue. |
No problem Caio! It would be a nice feature to get a "Successful run"-message with a webhook to e.g. Slack, to follow the different connections and to react as fast as possible if something went wrong. |
Hi Caio, I got two questions:
|
Hi Jacob, sorry, missed your questions here. Answers below:
|
Thanks, Caio!
We've had it running for 7 days with uploads, no errors. But I cannot see
any conversions or value added. By the looks of it the data is not
ending up the right place all though I've double checked ids.
…On Tue, 30 Jul 2024 at 15:16, Caio Tomazelli ***@***.***> wrote:
Hi Jacob, sorry, missed your questions here.
Answers below:
1. I'll look into having that as an option, thanks for pointing that
out.
2. In this link
<https://developers.google.com/identity/protocols/oauth2#expiration>,
you can find common reasons for premature token expiration (normally,
refresh_token should only expire after 6 months of inactivity). The most
common cause of this problem is having your GCP OAuth project with
"Testing" publishing status, which causes the token to expire after 7 days.
If that's not the case, this could also be related to org specific policies
in your GCP project.
—
Reply to this email directly, view it on GitHub
<#166 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/BACDVN3DCZ5FMSVUEVYAJFLZO6G4RAVCNFSM6AAAAABHX55KWOVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDENJYGMZDQNZYHA>
.
You are receiving this because you were mentioned.Message ID:
***@***.***>
|
Hi Caio,
Just bumping this one in case you missed it. The uploaded data isn't
showing in the platform. Could you have a look?
…On Tue, 30 Jul 2024 at 15:35, Jacob Brix ***@***.***> wrote:
Thanks, Caio!
We've had it running for 7 days with uploads, no errors. But I cannot see
any conversions or value added. By the looks of it the data is not
ending up the right place all though I've double checked ids.
On Tue, 30 Jul 2024 at 15:16, Caio Tomazelli ***@***.***>
wrote:
> Hi Jacob, sorry, missed your questions here.
>
> Answers below:
>
> 1. I'll look into having that as an option, thanks for pointing that
> out.
> 2. In this link
> <https://developers.google.com/identity/protocols/oauth2#expiration>,
> you can find common reasons for premature token expiration (normally,
> refresh_token should only expire after 6 months of inactivity). The most
> common cause of this problem is having your GCP OAuth project with
> "Testing" publishing status, which causes the token to expire after 7 days.
> If that's not the case, this could also be related to org specific policies
> in your GCP project.
>
> —
> Reply to this email directly, view it on GitHub
> <#166 (comment)>,
> or unsubscribe
> <https://github.com/notifications/unsubscribe-auth/BACDVN3DCZ5FMSVUEVYAJFLZO6G4RAVCNFSM6AAAAABHX55KWOVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDENJYGMZDQNZYHA>
> .
> You are receiving this because you were mentioned.Message ID:
> ***@***.***>
>
|
Hey @jbrs360 sorry for the delay. Unfortunately there are many reasons why you're not seeing the data. Normally, when there are no errors, this is unrelated to Tightlock. I would advise following the steps in the comment above for checking the logs again and see what is the raw response from the API in the success cases and share here if you still can't find the reason. Cheers, |
I've configured a 1PD Scheduler through the interface using GADS SSI.
There is access to both platforms as I've used the same credentials/configurations in a Python project before trying with Tightlock.
To limit errors:
When running the 1PD Scheduler connection I get 1 error: "INVALID_ARGUMENT" Count: 1. I have no idea how to proceed. I've narrowed everything down where I can't change anything anymore and the error message doesn't help me.
![image](https://private-user-images.githubusercontent.com/134494903/330778112-574bb783-93e4-4ff3-b95b-3b173472f51f.png?jwt=eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJpc3MiOiJnaXRodWIuY29tIiwiYXVkIjoicmF3LmdpdGh1YnVzZXJjb250ZW50LmNvbSIsImtleSI6ImtleTUiLCJleHAiOjE3MjU5NDA1ODYsIm5iZiI6MTcyNTk0MDI4NiwicGF0aCI6Ii8xMzQ0OTQ5MDMvMzMwNzc4MTEyLTU3NGJiNzgzLTkzZTQtNGZmMy1iOTViLTNiMTczNDcyZjUxZi5wbmc_WC1BbXotQWxnb3JpdGhtPUFXUzQtSE1BQy1TSEEyNTYmWC1BbXotQ3JlZGVudGlhbD1BS0lBVkNPRFlMU0E1M1BRSzRaQSUyRjIwMjQwOTEwJTJGdXMtZWFzdC0xJTJGczMlMkZhd3M0X3JlcXVlc3QmWC1BbXotRGF0ZT0yMDI0MDkxMFQwMzUxMjZaJlgtQW16LUV4cGlyZXM9MzAwJlgtQW16LVNpZ25hdHVyZT1lNDcwODUwNWNmZGM4NDFkMjk4YmM1MTljNzRmOTRjNmY3ODMyMzI2OTlkMDUyYmIzYWM5ZTFhYmZlZTRiNTExJlgtQW16LVNpZ25lZEhlYWRlcnM9aG9zdCZhY3Rvcl9pZD0wJmtleV9pZD0wJnJlcG9faWQ9MCJ9.JPDE4tiA5OnomWX51diybp9ZTKYP9gN0OKBJxaeAXPI)
![image](https://private-user-images.githubusercontent.com/134494903/330778158-40256af9-290f-47c8-aa02-46fd53c3a171.png?jwt=eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJpc3MiOiJnaXRodWIuY29tIiwiYXVkIjoicmF3LmdpdGh1YnVzZXJjb250ZW50LmNvbSIsImtleSI6ImtleTUiLCJleHAiOjE3MjU5NDA1ODYsIm5iZiI6MTcyNTk0MDI4NiwicGF0aCI6Ii8xMzQ0OTQ5MDMvMzMwNzc4MTU4LTQwMjU2YWY5LTI5MGYtNDdjOC1hYTAyLTQ2ZmQ1M2MzYTE3MS5wbmc_WC1BbXotQWxnb3JpdGhtPUFXUzQtSE1BQy1TSEEyNTYmWC1BbXotQ3JlZGVudGlhbD1BS0lBVkNPRFlMU0E1M1BRSzRaQSUyRjIwMjQwOTEwJTJGdXMtZWFzdC0xJTJGczMlMkZhd3M0X3JlcXVlc3QmWC1BbXotRGF0ZT0yMDI0MDkxMFQwMzUxMjZaJlgtQW16LUV4cGlyZXM9MzAwJlgtQW16LVNpZ25hdHVyZT0wZjQwNTVlNjNiNjBhOGI0NzgyMDE3NDQ2NmQwYTM3Nzg0M2YzZmY2MDU4MTA5ZDk1MTlmYjcxZDYyYTE5MDI5JlgtQW16LVNpZ25lZEhlYWRlcnM9aG9zdCZhY3Rvcl9pZD0wJmtleV9pZD0wJnJlcG9faWQ9MCJ9.AtQ7P_N2DzIdk3-8ZD434V6Le8ZayNSxUk_-lmNkDKs)
The text was updated successfully, but these errors were encountered: