@kapa.ai google analytics ga4 connector has consolidated streams , does they have incremental append

Thinking completed Yes, consolidated streams in the GA4 connector support Incremental - Append (as well as Incremental - Append + Deduped). The connector supports all four sync modes: [Supported Sync Modes] • Full Refresh - Overwrite • Full Refresh - Append • Incremental - Append • Incremental - Append + Deduped Regarding how incremental sync works specifically with consolidated streams: • Each property within a consolidated stream maintains its own incremental cursor, so properties sync independently. [One Stream per Report] •

property_id

is part of the stream's primary key, keeping rows from different properties distinct in the destination. [One Stream per Report] One important caveat: If you add a new Property ID after enabling the "One Stream per Report" setting, the new property is added as a new partition and starts from the stream's current cursor rather than your configured Start Date — meaning historical data for the new property is not automatically backfilled. You would need to manually clear the affected streams to trigger a full backfill. [One Stream per Report] 👍 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 will there be a rate limit issue if i do consolidate reports

Thinking completed Based on the knowledge sources, consolidating reports (enabling One Stream per Report) does not increase your rate limit risk. The documentation explicitly states: > "Syncs make the same number of API requests either way, so this setting reduces catalog size and destination table count rather than sync duration." [One Stream per Report] So consolidating streams is purely a catalog/destination organization improvement — it doesn't change how many API calls are made to Google Analytics. That said, rate limiting is still a general concern for the GA4 connector regardless of this setting. A few things worth knowing: • The connector applies a tier-aware rate limit locally — 10 requests/second for Standard Properties and 50 requests/second for Analytics 360 Properties. [manifest.yaml] • You can select your subscription tier (

Standard Property

or

Analytics 360 Property

) in the connector settings to apply the correct rate limit policy. [manifest.yaml] • GA4 quota cannot be self-service increased via the GCP console — unlike most Google APIs, a quota increase requires external escalation. [AGENTS.md] In short, switching to consolidated streams won't make rate limiting better or worse. 👍 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 what happens if i dont enable the One Stream per Report, then what are the streams i get

Thinking completed When One Stream per Report is disabled (the default), the connector creates a separate stream for every combination of report and Property ID. Naming Convention The stream naming follows a backward-compatible convention: [AGENTS.md] • The first property ID uses the plain report name — e.g.,

devices

• Each additional property ID gets a

Property<id>

suffix — e.g.,

devicesProperty5729978930

Scale of Streams With the default mode: [One Stream per Report] > "With 57 built-in reports and 70 properties that is roughly *3,990 streams*" So the total stream count = number of reports × number of Property IDs. Example If you have 2 properties (

111

and

222

) and a custom report named

first_report

, you would get: [unit tests] •

first_report

— for property

111

•

first_reportProperty222

— for property

222

Downsides of This Default Mode • The catalog becomes slow to load • The stream list is hard to manage • Setup becomes error-prone at scale [One Stream per Report] This is precisely why the One Stream per Report setting exists — to collapse all per-property streams into a single consolidated stream per report. 👍 0 button 👎 0 button ℹ️ Tip: Mention @kapa.ai in the thread for follow-ups or DM the app for 1-to-1 help.