To see if the integration is working correctly, follow these steps:

  1. Open your website and submit the form on your website.
  2. Check the lead that was created in your CRM as a result.
  3. If the GA Connector fields are populated with data it means the integration is working fine (even if the field values are “(not set)“)

With HTTPS, tracking will be more accurate.

The thing is, when a user goes from an HTTPS website to an HTTP one, most browsers hide the referrer information from the HTTP site.

This doesn’t allow Google Analytics and GA Connector to track the source of such user (unless there are UTM parameters).

So if your website is still HTTP, and your user is coming from some HTTPS blog for example, GA Connector (and Google Analytics) will consider this user’s traffic source direct/none.

You can read more about this and other tracking details here.

No, GA Connector can only save a pre-defined list of parameters that are described here.

You can prevent GA Connector tracking your form by removing the GA Connector script from that page.

This happened because of the change in tracking that Google made in October 2018.
They have disabled tracking templates that GA Connector uses to add these UTM parameters (in order to enable parallel tracking).

Thankfully, Google Ads have another feature that allows adding UTM parameters. It’s called “Final URL Suffix”.
We are now using this feature to power another solution that allows us to tracks campaigns, ad groups and keywords.

In order to implement this solution, please you can disable the old version of the GA Connector script and then go through this instruction.

Fortunately, no.

Your lead can be created in a day, in a month or even in a year after the form submission. As long as the lead’s email address matches the form submission email address, GA Connector will add the tracking information to it.

For Salesforce Professional Edition, GA Connector only supports GA-to-CRM data flow.

To setup GA-to-Salesforce for Professional Edition, you need to use GA Connector 1.0. You can start with this instruction.

As long as your Google Remarketing Ads contain UTM parameters, GA Connector will track them.
As long as your Dynamic Search Ads contain UTM parameters, GA Connector will track them.

We always recommend using GA Connector 2.0, unless you run into tracking issues (a high % of leads is not tracked).

GA Connector 2.0 pros:

  • Much easier to integrate. 1.0 requires updating your website forms, adding new fields, mapping them etc. It’s a whole process.

GA Connector 2.0 cons:

  • Currently, 1.0 (if integrated correctly) is able to give a higher percentage of tracked leads.
  • 1.0 supports several fields that 2.0 currently does not.


Unfortunately, it doesn’t. GA Connector only populates Leads/Contacts with GA data when they are created.


P.S. GA Connector does update existing objects for Zoho CRM though.

Unfortunately, it’s not possible to hide custom fields in Zoho CRM.

According to Zoho CRM support team, it’s not possible because extension fields are system defined, and currently, system defined feature cannot be hidden.



Note: We have requested to Zoho support to review this, and they have forwarded the request to their development team. So there is a possibility that this will be fixed in the future.

The current version of GA Connector doesn’t actually use Google Analytics API to populate CRM fields with analytics data (source,  medium etc). Instead, GA Connector emulates Google Analytics tracking algorithm precisely.

We took this approach because it allows more flexibility and it works faster this way.

The product is still called GA Connector because it uses Google Analytics algorithm to track information and because it also sends CRM data to Google Analytics (for a limited number of CRMs only though).

For Zoho CRM, GA Connector updates GA data every 5 minutes (if you’re using GA Connector 2.0).

For Salesforce and other CRMs, GA Connector only updates GA data one time – when the Lead/Contact/etc is created.

In the future, we’re planning to add the feature that will allow updating GA data in Salesforce at least every day.

No, GA Connector supports both HTTP an HTTPS sites out of the box, no need to make any changes in case you’re switching.

GA Connector price doesn’t depend on the number of users, it the same for the whole organization.

Unfortunately, it can’t, even if you’re using a third-party tool for capturing organic keywords (e.g. Keyword Hero).

The only way to do it is to reinstall GA Connector Fields extension and choose the users you want to make it available to:

Unfortunately, after reinstalling the extension, the old data won’t be available anymore. Although, with GA Connector 2.0, a significant part of the GA data will be renewed.

After integrating GA Connector, you may notice this problem:

Even though the majority of GA Connector fields are populated, some of them are still empty:

  • Pages Visited
  • Time spent on website
  • Number of Website visits

This is a temporary problem that occurs if you’re using the latest version of GA Connector (2.0). When it is fixed, you’ll start seeing these data points automatically.

At the beginning of 2018, we’ve completely rebuilt GA Connector in order to simplify the integration process. And some of the fields haven’t made it to the newest version yet – that’s why you don’t see them.

You’re prompted for an account ID when you start GA Connector installation on one browser/device, and finish on another. E.g. if you send someone a link to complete the last steps.

To solve this issue, you can log into your account from the second device or browser first, and then you won’t be prompted with the account ID.

You can log in to your GA Connector account by navigating to and clicking “Login”:



Or if you want to log in from another device or browser, you can find this link in your “Welcome to GA Connector, %yourname%!” email:


GA Connector supports most web forms with a rare exception. Not just native Zoho CRM and Salesforce forms.

Unlike 1.0, GA Connector 2.0 also doesn’t require adding any hidden fields to your forms.


There are just two requirements for the forms:

  • The contents of the form are not located inside a cross-domain iframe (or if they are, the iframe allows for adding custom JS code inside)
  • They need to have an email field (which GA Connector uses for visitor identification).


Here are just some of the forms supported by GA Connector:

  • Salesforce Web-to-Lead forms
  • Zoho CRM Webforms
  • Contact Form 7 for WordPress
  • Gravity forms for WordPress
  • Formidable for WordPress
  • Ninja Forms for WordPress
  • Unbounce forms
  • Hubspot forms
  • Pardot (by adding GA Connector code both inside and outside of Pardot iframe)
  • Marketo
  • Caldera forms
  • Connexys forms
  • Custom forms (usually)

Matching happens when the user types their email address in your webform.
The tracking code automatically picks up that an email address was typed and sends it to the server alongside visitor source information.
Later, when a Lead is created in the CRM, this data is matched and added to the Lead record.

You can read more about how GA Connector works in this article:
How GA Connector 2.0 Works

Leave a Reply

Your email address will not be published. Required fields are marked *