Live
Google Analytics 4
Web analytics
Server-side delivery of labeled events. Runs alongside the GA4 tags you already have; Capture Core flags a conflict before you turn delivery on.
Labeled events, delivered into Destinations you already run.
Capture Core sends named experience data server-side into the analytics tools your teams already trust. Google Analytics 4 is live. Adobe Analytics is next. Warehouses and CDPs follow on the same Destination path.
Definition
What is a Destination?
A Destination is where Capture Core delivers labeled events — the analytics, CDP, or warehouse your team already uses. You keep those tools. Capture Core captures interactions, names them, and routes them so charts and models finally see complete coverage.
Catalog
Which Destinations can Capture Core send events to?
Only Google Analytics 4 is live today. Everything else is labeled honestly as next or later so search and answer engines do not treat a roadmap as a catalog.
Next
Adobe Analytics
Web analytics
Next Destination after GA4. Built for teams on Adobe Experience Cloud who need labeled events without ripping out Analytics.
Later
Amplitude
Product analytics
Labeled events into the product analytics Destination your growth team already models in.
Later
Segment
CDP
Route named events into the CDP that already fans out to the rest of your stack.
Later
GTM server-side
Tag manager
Server-side Google Tag Manager as a Destination — ads and consent stay in GTM; product events arrive already named.
Warehouse
Into the warehouse you already run
Labeled events can land in BigQuery or Snowflake when those Destinations ship. Capture Core feeds the warehouse you already query — it is not a CDP or a second source of truth you have to migrate onto.
Later
BigQuery
Warehouse
Stream labeled events into the warehouse analytics and data teams already query.
Later
Snowflake
Warehouse
Same Destination path as BigQuery — named events in the warehouse you already run.
How Destination delivery works
Capture and name
Capture Core records interactions and assigns business-ready event names your teams can share.
Connect a Destination
In the dashboard, choose where labeled events should go. Credentials stay encrypted; the UI never shows secrets after save.
Deliver server-side
Events leave our cloud in batches. Keys never sit in the browser, and delivery can retry if a Destination is briefly down.
Keep native tags
Existing GA4 or tag-manager scripts stay in place. If we detect the same Destination already receiving native events, you decide before anything duplicates.
Destinations ship with Capture Core. Use Tag Guardian when you need proof journey events still fire after a deploy.
FAQ
What is a Destination in StrataIQ?
A Destination is where Capture Core delivers labeled events — the analytics, CDP, or warehouse your team already uses. Destinations are part of Capture Core, not a separate product you buy.
Which Destinations does Capture Core support today?
Google Analytics 4 is live today. Adobe Analytics is next. Amplitude, Segment, BigQuery, Snowflake, and GTM server-side are later Destinations on the same roadmap.
Do I need to remove GA4 or Google Tag Manager?
No. Capture Core runs alongside GA4 and GTM. Teams keep GTM for ads and consent. Destination delivery is optional and reversible; historical data stays where it is.
Can Capture Core send events to BigQuery or Snowflake?
Not yet. BigQuery and Snowflake are warehouse Destinations on the roadmap. When they ship, labeled events land in the warehouse you already run — Capture Core does not replace that warehouse.
How does server-side Destination delivery work?
After you connect a Destination in the dashboard, Capture Core sends labeled events from our servers in batches. Destination credentials stay encrypted at rest and never ship in the browser snippet.
Do I buy Destinations separately from Capture Core?
No. Destinations are how Capture Core delivers events. You choose which Destinations to connect; you do not purchase Destinations as their own product.
What if GA4 already receives the same events from my site?
Capture Core warns you before you turn on delivery to a Destination that already receives native events from the same site, so you can avoid duplicates instead of finding them in reports later.