Closed baer closed 2 years ago
Hi @baer thanks for opening this issue.
From the looks of your issue it seems you may actually be using the Google Ads API
and therefore do not need to create the custom reports. Would you be able to check your Connector connection details and let me know what API type your connector is using? If it says Google Ads, then you will just need to update the API configuration of the package by setting the api_source
variable to be google_ads
.
Thank you for the quick response! Fivetran now only offers a single Google Ads connector type called "Google Ads (Adwords)." See Below. I assumed that, being called "Google Ads (Adwords)" this corresponds to the Adwords API Configuration documentation.
If I'm understanding correctly, my connector does not require any additional reports to work with this package. Even though the name of the connector includes the word "Adwords," it corresponds with the Google Ads API Configuration
Sounds like this if just a README clarity issue after a Fivetran rename :). Easy fix. Thanks again!
@baer Correct!
Were you able to specify the google_ads_api
variable and see the package succeed? I also agree that the naming of the connector is a bit confusing. Especially since the product by Google is still called Adwords, but the API is now Google Ads 😕 .
I will check with our product team for naming consistency, but let me know if the changes help your package succeed on your end!
HI @baer I believe the above will have solved the issue you were experiencing. I will close this ticket, but please feel free to open a new one if you are still experiencing issues.
Is there an existing issue for this?
Describe the issue
The configuration for the Google AdWords connector in the README requires three custom report types:
FINAL_URL_REPORT
,CRITERIA_PERFORMANCE_REPORT
,CLICK_PERFORMANCE_REPORT
. There appear to be two issues:Potentially related, Fivetran recently deprecated the Google Ads API and converted all existing connectors to Google Adwords. Our account had a Google Ads connector that was converted that had a
click_performance
report. It looks like Fivetran automatically changed that report toclick_view
and renamed many of the attributes. This makes me think that the README may have outdated report and field names.Thank you for your support!
Relevant error log or model output
No response
Expected behavior
The configuration in the README should apply to the Fivetran connector.
dbt Project configurations
NA
Package versions
What database are you using dbt with?
snowflake
dbt Version
1.1
Additional Context
No response
Are you willing to open a PR to help address this issue?