When setting up a Google Analytics integration, you pull in a field from Google Analytics that indicates the customer. In our case, it's called "abbreviation". Screenshot: http://cl.ly/1X1J1Y1S2h08
You then indicate which Salesforce Account field corresponds to that Google Analytics field. In our case, it's called "Account Number". Screenshot: http://cl.ly/3g272c0O1T0f
Unfortunately, when Gainsight aggregates the raw data into the "Day Agg" table, it performs a [i]case-sensitive match between our "abbreviation" and "Account Number". Some Accounts, therefore, have ended up without any aggregated Google Analytics data. I didn't realize that behavior when we were setting it up (it's not noted in the documentation http://cl.ly/0x0F2u2q3E3H, and I did this setup live with our Project Manager, who either didn't know or think to mention it), and now I need to go back and make our Account Numbers precisely the correct cases, and then fix the aggregated data.
It's hard enough to get Salesforce and Google Analytics and Gainsight to all have identical customers listed in each one, without any missed or any duplicates, and this makes things even harder.
I'd prefer that the match would [i]not be case-sensitive, and wonder if it was simply an oversight in the product development.
Already have an account? Login
Login to the community
Enter your username or e-mail address. We'll send you an e-mail with instructions to reset your password.
I'm linking the email addressed stored in the Google Analytics data to the email in the Salesforce Contact, as shown here: http://cl.ly/331v3I1h1Q2I
I'm getting a case-sensitive match on the email field, too, which is even less likely to be valid than a case-sensitive match than on Account foreign keys, and of course there are so many email addresses that I can't correct the data manually, as I did for the Account foreign keys. Therefore, the Day Agg table is ending up with "Contact Not Found" in the "User Email" field.