​Although GA Connector doesn’t send data directly to Adwords, 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 Adwords and Analytics accounts:
    https://support.google.com/analytics/answer/1033961?hl=en
  3. Import CRM-related goals from Analytics to Adwords.

The problem looks like this:

Why this happens

According to the Google Analytics documentation article What the value (not set) means:

If you see (not set) as a value for Landing Page, this is generally due to a session with no page or screen view level hits included.

Which is exactly what happens when you install GA Connector:

  1. GA Connector sends events from the CRM to Google Analytics.
  2. These events are grouped into sessions. You can read more about this here.
  3. These sessions don’t contain any page views (because there were none), which is why you see more (not set) page views.

It is possible to import Analytics goals and transactions into Google Ads Conversion Tracking.

To import your goals and Ecommerce transactions from Analytics into Google Ads Conversion Tracking, the following conditions must apply:

  • Your Analytics and Google Ads accounts are linked.
  • You’ve enabled auto-tagging in your Google Ads account. Note: If you are using the auto-tagging override setting in Analytics, you can still import goals and transactions into Google Ads for those clicks.
  • On a per-type basis, your Analytics goal or transaction has received active traffic from an ad at some point.

To import your goals:

  1. Sign in to your Google Ads account, and click the Tools, billing, and settings icon in the header. Note: If you just recently linked your Google Ads and Analytics accounts, wait 30 minutes before starting to import goals or transactions.
  2. Click Measurement > Conversions.
  3. Click Add.
  4. Click Import, select Google Analytics, then click CONTINUE.
  5. Select each goal or transaction you want to import, then click IMPORT AND CONTINUE.
  6. Click DONE.

Google Ads Conversion Tracking starts importing the data from your Analytics account starting from the day you clicked Import. Historical data from before this date is not added to conversion tracking. Your goals appear alongside your conversion data in your Conversions page and Google Ads reports within two days.

You can read more about this here.

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.

Yes. GA Connector allows you to only send information about certain objects.

For example, you can send Amount only for Opportunities that have a certain Record Type or Stage.

You may be concerned about the implications of installing our app on API limitations (because by default, every lead/contact/etc creation will trigger a request to GA).

In order to solve this, we’ve developed a batching feature which allows to send only send events to GA once a day.

You can enable this feature in GA Connector General Settings – Main – Batch Requests (more details here).

Unfortunately, you can’t delete GA Connector tabs, but you can hide them.

Right now, GA Connector only supports Salesforce Enterprise or higher.

If you’re seeing this message, you’re probably using Professional or Group edition.

Right now, GA Connector doesn’t push CRM data to Google Analytics Ecommerce transactions. It can only send data as goals and customer dimensions&metrics.

So unfortunately, GA Connector doesn’t support Ecommerce Reports right now.

The free trial starts at the moment when you generate a license key (it’s a part of the setup wizard). It lasts 30 days.

If you want the trial to last longer, you can finish all the steps from the setup wizard and only then generate the license key. You can also request a trial extension in case you didn’t have enough time to test the app properly.

Even if your sales cycle is very long (e.g. 12+ months), GA Connector can still save and attribute CRM data about the sale correctly.

 

Many customers ask us what happens if the conversion happened 90+ days after the last visit because 90 days is an important milestone for Google Analytics and Adwords.

And there are a couple caveats in such cases:

  1. If your Google Analytics is connected to your Adwords account, and you export your Analytics conversions to Analytics, Adwords won’t be able to attribute this conversion.
  2. Last click source/medium of such offline conversion would be (direct)/(none), no matter where the user came from (that’s just how Google Analytics last non-direct click algorithm works). First click source/medium would be correct though, so you’ll still know that source that originally brought user to your website. Plus, all intermediary traffic source will be available in the multi-channel GA reports.

 

You can use GA Connector Visitor Source Tracking module to save first, last and all intermediary source inside the CRM, so you don’t need to rely on Google Analytics for attribution.

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.

You can configure events from any Salesforce field or object (if you add the necessary settings).
So for example, it will send the event like this when and object with name={ObjectName} object is created:
Category: Salesforce {ObjectName}
Action: Create
Label: (not set)
When a text/date/picklist field with name={FieldName} is updated, GA Connector will send an event like this one:
Category: Salesforce {ObjectName}
Action: Update {FieldName}
Label: {FieldValue}
Or if it’s a number field:
Category: Salesforce {ObjectName}
Action: Update {FieldName}
Label: (not set)
Value: {FieldValue}
You can read more about this here:
Technically, GA Connector doesn’t send any traffic source data to GA.
It only sends information like revenue in combination with GA Client 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.

You can read more about this here:

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 Analytics mostly as goals and dimensions, which can be displayed in:

  • almost every standard report, including Source/medium, Landing pages, Campaigns etc, and even Multi-channel reports;
  • you can use CRM data sent by GA Connector in custom reports as well.

You will be able to use CRM data just the way you’re using other goals in Google Analytics.

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. Unless you configure goals for GA Connector events, you won’t see any changes (because all events are sent as non-interaction events). If do you configure goals for GA Connector events, the only change you’ll see is a couple more options inside the “Conversions” dropdown.

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

You need to save GA tracking IDs to your Leads in addition to GA client ID.

Having the tracking 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 Tracking ID of your GA property to Salesforce field zuevsoftware__Google_Analytics_Tracking_ID__c 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 Google Analytics Tracking ID field in your form
  2. Make the field hidden, and insert your Google Analytics tracking ID in the value attribute as shown below:
    type=”hidden” value=”UA-111111111-1″ />
  3. When the lead is created, Google Analytics tracking 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 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

 

Leave a Reply

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