Event-level behavioral data
The whole event, outside the limits of what the GA4 interface will show you.
Existing Practical Vision client? You do not need the Data Audit. Request BQSync access.
Kept raw
select e.event_date, e.event_name, a.account, a.plan
from `metacortex.pv_analytics.events` e
join `your_crm.accounts` a using (user_pseudo_id)The account and plan columns are not GA4's. They are your own tables, joined in the warehouse on a key you control.
Where it fits
BQSync is not a product-analytics interface. It maintains event-level behavioral data in your warehouse so product questions can be answered with your existing tools, alongside BI, instead of in isolated dashboard logic. You do not need to work in BigQuery yourself - the point is that the answers stop depending on what a reporting interface happens to expose.
What you receive
Six things land in your warehouse.
Each card shows the one underneath it, because a benefit you cannot point at is a claim.
The whole event, outside the limits of what the GA4 interface will show you.
Behavioral history that is not subject to sampling, cardinality limits, or thresholding.
The sequence of what people did, in the order they did it, across sessions.
Your own customer tables, joined to behavior on a key you control.
The events behind the analysis are reviewed before anything is built on them.
One shared set of tables rather than a separate product-only extract.
BQSync is not a product-analytics product, a journey builder, or a replacement for the tools product teams already use to look at behavior. It maintains the underlying events so those questions can be answered in your warehouse.
Questions this data can support
Ask your data team for these from the maintained tables.
None of them require product to open BigQuery.
How teams use it
These are the working patterns product teams settle into once behavioral data sits next to the rest of the business, rather than behind a reporting interface.
01
Track who reached a new feature, who used it more than once, and whether adoption concentrated in a handful of accounts. Because account and plan context can be joined in, adoption can be read per segment rather than as a single site-wide number.
02
Follow the sequence of actions leading into an important outcome, even when it spans several visits. Event-level history makes it possible to look at what preceded a conversion or a cancellation, instead of only counting the outcome.
03
Bring in-product behavior into the retention analysis your data team already runs, so that usage patterns, not just billing events, inform which accounts look healthy.
04
Ask your BI or data team to build the product metrics you care about on the same maintained tables. Product and BI stop reconciling two versions of the same number.
Keep going
Next · /bi-data
They usually own the decision. This is the page to send them.
For BI & DataAlso · /solution
The audit, the transformations and the monitoring behind the tables.
See how it worksSideways · /marketing
Acquisition context attached to the behavior you are already studying.
For marketing & growthAlready working with Practical Vision? You do not need the Data Audit. Request BQSync access.