Markin + BigQuery
Signal and outcome reads without moving a row.
Most large B2C estates already land every event in BigQuery. Markin treats it as the source of truth for both the hypothesis and its verdict, so nothing has to be reconciled between two systems later.
Attribute write-backRead only
What Markin reads
- GA4 and product event exports
- Transaction and subscription tables
- Customer attributes and consent state
What Markin writes back
- Decision tables partitioned by date
- Holdout membership and experiment reads
How the connection works
| Pattern | What it means here |
|---|---|
| Attribute write-back | Markin writes the decision onto the customer profile; your existing journeys read it as an entry condition. Latency is the platform's sync interval. |
| Read only | Markin reads signal from this system. Nothing is written back and no schema is changed. |
BigQuery questions
- How does Markin connect to BigQuery?
- Attribute write-back, Read only. Markin writes the decision onto the customer profile; your existing journeys read it as an entry condition. Latency is the platform's sync interval.
- What does Markin read from BigQuery?
- GA4 and product event exports; Transaction and subscription tables; Customer attributes and consent state.
- What does Markin write back into BigQuery?
- Decision tables partitioned by date Holdout membership and experiment reads
- Do we have to move our data to Markin?
- No. Markin reads from your warehouse, product events and operational systems in place, on your compute, under the access rules your data team already set. Nothing is copied into a separate customer base and there is no vendor-side profile store to migrate off later.
- Does Markin replace our engagement platform or CDP?
- No, and it should not. Your engagement platform keeps the channel, the templates, the deliverability and the governance. Your CDP keeps identity and consent. Markin adds the layer neither has: deciding which action deserves to exist for each customer, and proving it against a holdout.
- What if the system we use is not listed?
- The four activation patterns cover almost everything: attribute write-back, triggered event, decision API and direct surface rendering. Any system that exposes an API, accepts a table, or can read a warehouse column can receive decisions. New connectors are built during deployment, typically in days.