# Google Analytics 4 + Krokul CRM

Yes. Krokul CRM integrates with Google Analytics 4 and sends deal events through the GA4 Measurement Protocol. The Krokul form widget saves the GA4 client_id and session on each new deal, and when it is qualified, won or lost, Krokul posts the matching event to your GA4 property with its value. Site visits and closed sales then sit in the same reports. The events travel through the Krokul app in Zapier, Make, n8n or Albato, or through the Krokul API and webhooks.

**Status:** Via API and webhooks. **Automation platforms:** Zapier, Make, n8n, Albato.

## What your team gets

### The visitor ID travels with the request

GA4 keeps the visitor client_id in the _ga cookie on your site. The Krokul form widget reads it, together with the current session, and stores both on the new deal. Every later event about this deal reaches GA4 under the same client_id, so it joins the visit that started it.

### Deal stages become funnel events

GA4 lists recommended events for this kind of funnel, such as generate_lead when a request arrives and qualify_lead when it is qualified. Krokul maps its stages to these event names, and a GA4 funnel exploration shows the path from first visit to signed contract.

### A won deal becomes a key event with value

When a manager marks the deal as won, Krokul posts close_convert_lead (or purchase, if you prefer) to the Measurement Protocol with its value and currency. Mark that event name as a key event in GA4, and closed deals count next to online conversions in the same property.

### Lost deals reach GA4 as well

A lost deal goes to GA4 as close_unconvert_lead. Campaign reports in GA4 then show, for each channel that brings requests, how many of them do not turn into sales.

## What moves between Google Analytics 4 and Krokul

| Google Analytics 4 | Krokul | Direction | When |
|---|---|---|---|
| client_id and session from the _ga cookie | Deal fields for the GA4 visitor | Site → Krokul | Submission of the Krokul form widget |
| Event generate_lead | New deal from a site form | Krokul → GA4 | The deal is created |
| Event qualify_lead or a custom stage event | Stage change | Krokul → GA4 | The deal moves to a mapped stage |
| Event close_convert_lead or purchase, with value and currency | Won deal | Krokul → GA4 | The deal is marked won |
| Event close_unconvert_lead | Lost deal | Krokul → GA4 | The deal is marked lost |

## How to connect today

### Krokul app in Zapier, Make, n8n or Albato

1. Connect the Krokul app with an API key.
2. Use Krokul triggers such as Deal Won or Deal Stage Changed with an HTTP step to /mp/collect when you need extra logic, for example a value adjusted by margin.
3. The GA4 trigger New Conversion Event in Zapier can add a comment to a deal through the Krokul action Add Comment.

### Custom flow through the Krokul API and webhooks

1. In GA4, open Admin → Data collection and modification → Data streams, select the web stream, create a Measurement Protocol API secret and note the measurement ID.
2. Create a Krokul API key with read access to deals, and keep the GA4 client_id on each deal with card/api-update.
3. Subscribe a Krokul webhook to card.statusChanged, card.won and card.lost, and verify the x-crm-signature header with your secret.
4. Post the matching event to /mp/collect with the stored client_id, then check it in GA4 DebugView.

**Triggers:** New Conversion Event.

**Actions:** Create Conversion Event for a Property; Create Measurement; Run Report for a Property; Send Measurement Events for an Application; Find Conversion.

### For integrators

The Measurement Protocol adds server events to the data that the Google tag collects on the site, so the tag stays in place. Keep the API secret on the server. One request carries up to 25 events, timestamp_micros may go back up to 72 hours, and Google offers the region1.google-analytics.com host for EU collection. For custom flows, the signed Krokul webhooks card.won and card.statusChanged carry the deal fields, and the Krokul API reads or writes the stored client_id.

[API documentation](https://app.krokul.com/api/v1/docs)

## Questions and answers

### Does Krokul integrate with Google Analytics 4?

Yes. Krokul integrates with Google Analytics 4 through the Krokul app in Zapier, Make, n8n and Albato, and through its API and webhooks. Deal events reach GA4 through the Measurement Protocol.

### Why does Krokul store the client_id?

A web stream event sent through the Measurement Protocol needs the client_id to tie it to a visitor. Without it GA4 cannot attribute the deal to the campaign that brought the visit.

### Can a deal won after several weeks still join the original visit?

The event lands on the same client_id, so the visitor is the same. Google notes that server events join gtag data best within 48 hours of the visit, so for long sales cycles GA4 records the win as a new event of that visitor.

### Does Krokul import data from GA4?

No. GA4 stays the place for traffic reports. Krokul sends deal events in one direction, from Krokul to GA4.

## Limits

Reports, audiences and attribution models stay in Google Analytics 4. Krokul adds qualification, won deals and lost deals, the events that happen after the form.

## Related services

- [Google Ads](https://krokul.com/en/integrations/google-ads/index.md)
- [Looker Studio](https://krokul.com/en/integrations/looker-studio/index.md)
- [Power BI](https://krokul.com/en/integrations/power-bi/index.md)
- [Webflow](https://krokul.com/en/integrations/webflow/index.md)
- [Zapier](https://krokul.com/en/integrations/zapier/index.md)

[Analytics and BI](https://krokul.com/en/integrations/category/bi/index.md)

Google Analytics is a trademark of Google LLC. Krokul is not affiliated with Google.

Updated: 2026-10-12

---

App: https://app.krokul.com/ · API: https://app.krokul.com/api/v1/docs