Analytics

Adding Google Analytics and Google Ads Conversion tags to Cvent landing pages

Step 1

Cvent has provided a guide to add Google Analytics integration to its landing pages. Please pick up the guide here and follow the steps 1 to 3 on page 9. Please enable the linker plugin there too. See picture below:

image.png

Step 2

Now, that Google Tracking is in place, add the conversion tracking code for Google Ads.

Please add the two code snippets posted below to the “Admin>Account>Account>Code Snippets>”. Please follow this video for the details.


The re-marketing pixel for each Cvent form:

—————————————————————————————————————

<!– Global site tag (gtag.js) – Google Ads: 1002231020 –><script async src=”https://www.googletagmanager.com/gtag/js?id=AW-1002231020“></script><script>  window.dataLayer = window.dataLayer || [];  function gtag(){dataLayer.push(arguments);}  gtag(‘js’, new Date());
  gtag(‘config’, ‘AW-1002231020’);

</script>

—————————————————————————————————————  

The conversion pixel for each time a lead is submitted via Cvent:

<!– Event snippet for Cvent Form Conversion conversion page –> <script>  gtag(‘event’, ‘conversion’, {‘send_to’: ‘AW-1002231020/bYQ2CJDy25oBEOyp890D’});</script>

Step 3

  
Once done, and the code is assigned to the right places, as per the video link above, please enable cross-domain tracking from within Google Analytics. Excellent video provided by Benjamin at LovesData.com


Step 4

One more thing left to do is to add cvent.com to the Referral Domain Exclusion list in Google Analytics. To do that, please go to the Property( the middle portion of the Analytics account) as shown below

Please click on the yellow “Referral Exclusion List” and enter this text into the referral exclusion list.

That’s it! You are done and will be able to track Google Ads conversions as well as page views on the Cvent landing pages to your heart’s content.

The same process can be followed for Facebook and other traffic sources by just replacing the code in Step 2 with the equivalent for tracking the other traffic sources.

I do realize that this is a bit confusing so I can get on a call with the developer putting this in place if needed. To contact me, get me on Upwork or just write to me here.

Analytics, Google Tag Manager

UserID tracking in Google Tag Manager(GTM)

uid_gtm

Why do we need to do that?

Ostensibly Google says that you do this for tracking true users of your site. Since multiple devices generate a visitor cookie each, they get counted as different visitors. You can stitch sessions cross-device by creating a userid view.

However, if we want to track CAC and LTV by referral sources and we have only Google Analytics and an internal database around, we can piggyback on this method to measure them.

It is tricky and will require some testing before it runs in your environment. However, it works and I have managed to figure it out in Google Tag Manager and will lay it out for you dear analyst, step by step.


Step 1

Create the User-ID view in Google Analytics. Go to the Property and expand “.js tracking Info”. Then follow the prompts as seen in the picture below.

uid_gtm_02

After you have done the above, let’s create a dimension to store this data.

Step 2

In the same property column, below the PRODUCT LINKING tab, sits a place to create custom dimensions as shown in this picture below.

uid_gtm_03_02

 

Click on create dimension and add the custom dimension as shown below:

uid_gtm_04

Please note that you have to name it userID. This is because I am going to name the data layer variable later the same. They have to be so to capture your user information.

Step 3

Have your awesome developer pass the user-id value to the data layer variable called userID. The values that it should spit out if you click “view-source” on your site should look like this:

dataLayer = [{‘userID’: ‘yyyyyy’}];

dataLayer.push( {‘event’:’uidAvailable’, ‘uid’:’yyyyyy’} );

They can push this change live anytime and will be quite thankful for the Starbucks drink you will treat them to.

Make very sure that this userID being made cannot be Personally identifiable information(PII). So no names, email addresses, etc.

Step 4

Ok! Let’s push on now to the Google Tag Manager and the last part of this implementation.

Open up your tag manager and on the left hand side where it says, variables, click and add a user defined variable. We will call it userID.

uid_gtm_05

Now, on the left hand side open up the tags section. On all the tags that have anything to do with an event or page view, we will make slight edits. Let’s start with the Google Analytics tag (it should be set to universal Analytics otherwise this will not work).

step_4_2

We add two variable to be filled when the tag fires, one is the userId (please note that this is the exact name you need to set). The other is the custom dimension that we have created in Google Analytics so we can run reports based on our own user-ids, which I am sure, are aligned to email addresses.


Step 5

Now, let’s set our workspace on Google Tag Manager to Preview the changes that we have made. If this works, the Real-Time reports in Google Analytics will immediately start collecting data. Once it works, then go ahead and publish the new tags.

Now, you should be free to download the userID and referral source. You can download the LTV and userID from your own database and analyze in Excel or any other spreadsheet of your choice.

You would have noticed that I keep harping on the name and case of the variable “userID” and “userId”. I thought to name all variables the same and it didn’t work. However, hard-coding the variables works perfectly!

Do let me know if you have any issues with this and I can walk you through the implementation, if need be.