@kapa.ai does google ads connector have geo_target_constant stream

Based on the knowledge sources, the Google Ads connector does not have a

geo_target_constant

stream as a standalone stream in the current manifest. The

geo_target_constant

is mentioned in the

config_migrations.py

file as part of the

FULL_REFRESH_CUSTOM_TABLE

list: [config_migrations.py]

FULL_REFRESH_CUSTOM_TABLE = [
    "asset",
    "asset_group_listing_group_filter",
    "custom_audience",
    "geo_target_constant",
    "change_event",
    "change_status",
]

This list appears to be used for migration/configuration purposes, not as a directly exposed stream. Looking at the full list of streams defined in the connector's

manifest.yaml

,

geo_target_constant

is not listed as one of the available streams. [manifest.yaml streams] The connector does have geography-related streams such as: •

geographic_view

•

geographic_view_with_metrics

•

geo_performance

However, if you need

geo_target_constant

data, you may be able to access it via a Custom GAQL Query stream (

custom_ga_query_stream

), which is available as a dynamic stream in the connector. [manifest.yaml streams] 👍 0 button 👎 0 button ℹ️ Tip: Mention @kapa.ai in the thread for follow-ups or DM the app for 1-to-1 help.

@kapa.ai so the Custom GAQL Query streams will be only full refresh?

No, Custom GAQL Query streams can be either incremental or full refresh, depending on whether your query includes

segments.date

in the

SELECT

clause. A custom query is treated as incremental if: •

segments.date

is present in the

SELECT

clause, and •

segments.date

is not already in the

WHERE

clause (since you'd be manually controlling the date range) [test_empty_streams.py] For example: When incremental, the connector automatically appends a

WHERE segments.date BETWEEN '{start_date}' AND '{end_date}'

condition to your query and uses

segments.date

as the cursor field. [components.py] So for

geo_target_constant

, since it is a reference/lookup table that doesn't typically have date segmentation, you would likely end up with a full refresh query unless you explicitly include

segments.date

in your SELECT. 👍 0 button 👎 0 button ℹ️ Tip: Mention @kapa.ai in the thread for follow-ups or DM the app for 1-to-1 help., with interactive elements