Lead Source Tracking (API-based) FAQ

This doesn’t impact GA Connector as GA Connector doesn’t use third-party cookies. GA Connector uses first-party cookies instead.

GA Connector can also be configured to not use cookies and use other web storage options.

Yes! GA Connector will work on both Salesforce Lightning Experience and Classic.

With CRM-to-GA integration, you’ll be able to use the advanced Google Analytics reports with revenue data (e.g. multi-channel attribution reports).

The purpose of CRM-to-GA integration is the same as GA-to-CRM: to show you the ROI of your marketing campaigns. But CRM-to-GA allows you to see the ROI data in Google Analytics reports that have certain features that CRM reports don’t provide (e.g. multi-channel attribution reports).

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)“)

​Although GA Connector doesn’t send offline conversions directly to Google Ads, it’s possible to use it for this purpose.

Just follow the steps below:

1. ​Import CRM data to Google Analytics with GA Connector.
2. Link your Google Ads and Analytics accounts:
   ​https://support.google.com/analytics/answer/1033961?hl=en
3. Import CRM-related conversion from Analytics to Google Ads.

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.

It is possible to import GA4 conversions and purchase events into Google Ads Conversion Tracking.

To import your GA4 conversions (such as purchase events) into Google Ads Conversion Tracking, the following conditions must apply:

• Your GA4 property and Google Ads accounts are linked.
• You’ve enabled auto-tagging in your Google Ads account.
• The GA4 event you want to import has received traffic from an ad at some point.

Steps to import conversions:

1. Sign in to your Google Ads account, and click the Tools and settings icon in the header. Note: If you just recently linked your Google Ads and GA4 accounts, wait 30 minutes before starting to import conversions.
2. Click Measurement > Conversions.
3. Click New conversion action
4. Click Import, select GA4 Properties, then click CONTINUE.
5. Select the conversion you want to import, then click IMPORT AND CONTINUE.
6. Click DONE.

Google Ads will start importing data from your GA4 property beginning on the day you click Import. Historical conversion data before this date will not be added.

Your GA4 conversion events will appear alongside your other conversion actions within Google Ads Conversion Tracking and reports within two days.

You can read more about this 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 within two weeks. 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 currently only supports GA-to-CRM data flow.

To setup GA-to-Salesforce for Professional Edition, start a 30 days free trial from our website and follow the instructions from the setup wizard.

We always recommend using API-based integration, unless you run into tracking issues (a high % of leads is not tracked).

API-based integration pros:

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

Cookie-based integration cons:

• Currently, cookie-based integration (if integrated correctly) is able to give a higher percentage of tracked leads.
• Cookie-based integration supports several fields that the API-based integration currently does not such as (All Traffic Sources, Pages Visited, Number of Website Visits, Time Spent on Website).

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.

Yes, you are able to disable the default events in the dashboard here. You can also change the frequency of the events in the preferences section here.

The current version of GA Connector doesn’t actually use Google Analytics API to populate CRM fields with analytics data (source,  medium etc). Instead, it uses a proprietary tracking approach inspired by how Google Analytics processes and attributes data.

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, Salesforce, Pipedrive, Salesflare, Close CRM GA Connector updates GA data every 5 minutes (if you’re using GA Connector API-based integration).

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

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 API-based integration, 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 Lead Source Tracking (API-based). When it is fixed, you’ll start seeing these data points automatically.

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.

Currently, GA Connector doesn’t send CRM data directly into GA4 Ecommerce transactions. Instead, it can push CRM data as events, custom dimensions, and custom metrics for use in GA4 reports.

As a result, GA Connector doesn’t fully support GA4 Ecommerce Reports at this time.

The free trial starts at the moment when you sign up from our website. It lasts 30 days.

You can also request a trial extension in case you didn’t have enough time to test the app properly.

You can log in to your account here using the email address you used during sign-up.

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

Unlike Cookie-based integration, API-based integration 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 API-based integration Works

Yes. Even with very long sales cycles (e.g., 12+ months), GA Connector can still capture, save, and attribute CRM data for closed deals accurately.

Many customers ask about conversions that occur more than 90 days after the last website visit because 90 days is a key threshold for Google Analytics and Google Ads.

Here are some important considerations:

1. Google Ads limitation: If your Google Analytics property is linked to Google Ads and you export Analytics conversions back to Google Ads, conversions beyond 90 days from the last click won’t be attributed properly in Google Ads.
2. Last-click attribution in GA: Google Analytics will attribute these conversions to (direct) / (none) in last-click reports, regardless of the user’s original source. However, first-click source/medium attribution remains correct, so you’ll still know what originally brought the user to your site. Intermediate traffic sources are also available in Multi-Channel Funnel reports.

To overcome these limitations, GA Connector’s Visitor Source Tracking module records first, last, and all intermediary sources directly in your CRM, so you don’t have to rely solely on Google Analytics attribution rules.

Yes, GA Connector supports apps built on top of force.com, such as Connexys for example.

No, GA Connector works with both Google Analytics Standard edition and 360.

Technically, GA Connector doesn’t send any traffic source data to GA. It only sends information like revenue in combination with GA Client ID and GA Session ID, which serves as an identifier of the user.

Google Analytics already knows all users’ traffic sources (including the first click). With GA Connector, it also knows CRM data about some users (e.g. revenue stats).

GA Client ID serves as a key that combines traffic source and CRM data. It means that you can use CRM data will all attribution models available in Google Analytics.

You can read more about this here.

Yes, certainly. You can use CRM data will all attribution models available in Google Analytics.

No, there are no limitations.

During the free trial, you get a fully working version of GA Connector, just for a limited time.

Long sales cycles aren’t a problem. Even if the cookie has expired on the website, it’s already captured inside the CRM.

This means that even if the information about the sale is sent in two years after the conversion, GA Connector will still send the data to Analytics. And Analytics will still display this sale inside its reports.

GA Connector sends CRM information to GA4 primarily as events, custom dimensions, and custom metrics. These can be used across:

• Standard GA4 reports, including Acquisition (e.g., Source/Medium, Session Campaigns), Engagement (e.g., Pages and Screens), and Conversions.
• Exploration reports (custom ad-hoc analysis), where you can combine CRM data with any other available GA4 dimensions and metrics.

This means you can analyze CRM data in GA4 in much the same way you analyze other event-based data—allowing flexible filtering, segmentation, and comparison within your reporting workflows.

For sure. You will be able to use data imported from Salesforce with all attribution models offered by Google Analytics.

You can read more about this here: GA Connector and Multi-Channel Attribution Reports

GA Connector for Salesforce can send information about any Salesforce object into Salesforce. It can send almost any field and information about how many objects of a certain type were created.

Here are just some examples of data points that GA Connector can send from Salesforce to GA:

• Number of Opportunities created.
• Number of Opportunities that reached a certain stage (e.g. closed won).
• Number Leads that reached a certain status (e.g. Qualified or Converted).
• Opportunities Amount (or any other field that represents a number, e.g. revenue or profit).
• How many objects of any given type were created.
• Any text field from any object.

After these data points are sent to Google Analytics, you can combine them with other Google Analytics metrics and dimensions in reports, and even create calculated metrics based on them.

As a result, you will be able to measure things like:

• Revenue per channel.
• ROI of each channel.
• The number of qualified vs disqualified leads per channel.
• The number of customers of certain type per channel (e.g. how many wholesale vs retail customers a certain marketing campaign generated)
• And almost any other metric that can be calculated by combining Salesforce and Google Analytics data.

No. GA Connector does not alter your existing GA4 reports or tracking configuration.

If you choose to mark GA Connector events as conversions, the only difference you’ll see is additional conversion events listed in your Conversions report and available for analysis in other standard GA4 and Exploration reports.

Yes, GA Connector for Salesforce supports multiple Google Analytics accounts.

You need to save GA Measurement IDs to your Leads in addition to GA Client ID.

Having the Measurement ID in each Lead/Account/etc allows GA Connector can determine to which GA property to send the updates to.

This can be achieved by saving the Measurement ID of your GA property to Salesforce field GA_Measurement_ID during the form submission.

Example of implementation

For example, here is how you do it if you are using Web-to-Lead forms in Salesforce:

1. Add the GA Measurement ID field in your form
2. Make the field hidden, and insert your GA Measurement ID in the value attribute as shown below:
   <input  id="00N1r00000KN1Py" maxlength="255" name="00N1r00000KN1Py" size="20" type=”hidden” value=”G-CWTHC49Y9K” />
3. When the lead is created, GA Measurement ID will be added by default to your lead, and that will trigger an event on the right property.

Yes, in many cases GA Connector can send information about Salesforce Leads/Contacts/etc created by call tracking software.

However, GA Connector requires the call tracking software to send GA Client ID and GA Session ID to Salesforce in order for it to be able to send data to Google Analytics.

Not all call tracking apps match this requirements. Here are some examples that support this:

• CallTrackingMetrics
• Ringostat
• CallRail