GA Connector – CRM & GA integration

Beskrywing

Most marketing teams can’t answer a simple question: which campaigns, ads, and keywords actually turn into revenue? GA Connector answers it, right inside your CRM.

Why marketers use GA Connector

• See the true source of every deal. Every lead and closed deal in your CRM shows the campaign, keyword, and ad that created it.
• Tracking that survives ad blockers and browser privacy features. Third-party scripts get blocked; this plugin runs first-party, through your own domain and server, so it keeps working.
• Every traffic source covered. Google Ads, Facebook Ads and other paid channels, plus organic, social, referral, and email.
• Marketing ROI without the enterprise price tag. Report revenue by campaign, channel, and keyword. No full-blown attribution suite required.
• GDPR-ready. The plugin captures nothing about the visitor on your server as the page loads; with manual script injection, the tracker runs only after your consent banner or tag manager allows it.

Requires a GA Connector account. The plugin is free with no locked or trial-limited features; the GA Connector service it connects to is a paid subscription with a 30-day free trial. Full details in External services below.

What you’ll see in your CRM for each lead and deal

• First-click and last-click attribution: channel, source, campaign, keyword, ad content, and landing page.
• All UTM parameters (source, medium, campaign, term, content) and click IDs like gclid.
• Visitor details: location, device, browser, pages visited, and time on site.

How it works

• A visitor lands on your site, and the tracker records the page they landed on and where they came from, read in the visitor’s browser.
• The GA Connector tracker loads from your domain instead of a third-party one, so ad blockers and browser privacy features leave it alone.
• Page views and lead details are sent to your own site first, then relayed securely to GA Connector with your API key attached on the server, never in the browser.
• GA Connector matches that activity to the leads and sales in your CRM and reports on what’s driving revenue.

Key plugin features

• First-party, server-side tracking through your own domain.
• API key stays private on the server, never in your page source or visible network requests.
• GDPR-ready: nothing about the visitor is captured on your server as the page is built; with manual script injection, nothing runs until the visitor accepts consent.
• Works with your consent banner or Google Tag Manager via manual script injection.
• Works with any caching setup, including full-page caching.
• Multisite-ready; setup is pasting your API key.

Powered by the GA Connector service

• Records where each visitor came from: the campaign, source, keyword, referrer, device, and location.
• Follows a visitor across multiple visits, devices, and your different domains.
• Links that history to the leads, contacts, and closed deals in Salesforce, Zoho CRM, Pipedrive, or Close.
• Reports on which marketing sources actually generate revenue, broken down by campaign, channel, and keyword.

GA Connector is a full attribution and reporting product; this plugin is the first-party connection to it.

Supported CRMs

This plugin works with Salesforce, Zoho CRM, Pipedrive, and Close. Using a different CRM? Other versions of GA Connector cover additional CRMs. See gaconnector.com for the full list.

External services

This plugin acts as a first-party, server-side proxy to the GA Connector tracking service.

What the service provides

GA Connector records where your website visitors came from (UTM parameters, referrer, gclid, device, geolocation, etc.) and links that attribution to leads and closed deals in your CRM (Salesforce, Zoho CRM, Pipedrive, or Close). On your behalf, the service stores each visitor’s full attribution history, applies multi-touch attribution across visits and devices, stitches visitor identity across your domains, enriches your CRM records with that data, and generates the reporting dashboards that attribute revenue to sources and campaigns. GA Connector is a full analytics/attribution product, not a licensing, validation, or storefront mechanism.

Why the plugin requires it

All of the processing above (storage, attribution modeling, identity stitching, CRM enrichment, and reporting) happens in the GA Connector service; the plugin has no local equivalent of that functionality. The plugin’s role is to capture tracking signals first-party on your server and relay them. Without a GA Connector account and API key the plugin has nothing to relay to, so it is not functional on its own (beyond its settings screen).

What runs where

• In the plugin (local, GPL): the settings screen, the first-party REST endpoints on your domain, server-side delivery of the tracker script, script-injection control (automatic or manual), API-key storage, and the cross-domain internal-domains list.
• In the service: attribution storage and modeling, cross-device and cross-domain identity, CRM enrichment, and revenue reporting dashboards.

When your site connects to the service, and what is sent

Your site connects to the GA Connector API at track.gaconnector.com in the following cases:

• When you save your API key on the settings page (and each time that page is rendered), the plugin calls GET /api/v1/account with your site’s domain and your API key attached as a Bearer token. This verifies the key and confirms the domain is registered on your account. No visitor data is sent.
• On every front-end page render (in automatic mode), the browser loads the tracker script from your own domain at /wp-json/ga_connector/js; the plugin fetches the canonical tracker script server-side via GET /api/v1/js. Only your site’s origin is sent; no visitor data is sent.
• When the tracker script runs in the visitor’s browser (immediately in automatic mode, or only after the visitor consents when it is loaded via a consent banner/Google Tag Manager in manual mode), it POSTs events to your own domain at /wp-json/ga_connector/events/pageview and /wp-json/ga_connector/events/identify. The plugin forwards these server-side to POST /api/v1/events/... with your API key attached. Pageview events send: a visitor id minted in the browser, the page URL, the referrer, the user-agent, the visitor’s IP address (determined by your server from the request), and a timestamp. The page URL, referrer, and user agent are read in the visitor’s browser. Identify events are sent when a visitor enters an email address into a form field (the tracker detects this automatically) or when your site calls the tracker’s identify API; they send the visitor id plus the identifier name and value (the email address is SHA-256 hashed in the browser before it is sent). Your API key is never exposed to the browser.

Account, terms, and privacy

A GA Connector account and API key are required. GA Connector is a paid subscription service; a 30-day free trial (no credit card required) is available at gaconnector.com. Use of the service is subject to GA Connector’s Terms of Service and Privacy Policy. For details on data handling and GDPR, see the GDPR guide.

Consent

The plugin adds nothing about the visitor to your pages on the server as the page is built; the page URL, referrer, and user agent are read in the browser instead. It never mints a visitor id or sets a cookie at page-render time; the visitor id and the __gacvid cookie are minted by the tracker script in the browser once it runs, which in automatic mode is as soon as the page loads.

To gate that on consent, use manual script injection so the tracker loads only when your consent banner or Google Tag Manager fires it; then nothing about the visitor is stored or sent until they have accepted consent.