Home » Help Center » Google Analytics & Facebook Pixel Tracking | Event and ECommerce Data | GTag

Google Analytics & Facebook Pixel Tracking | Event and ECommerce Data | GTag

You and I both know that the best results are born out of analyzing and optimizing. Regpack is already helping you do this for registration, but we wanted to take it a step further.

To that end, we’ve made some updates to the information that Regpack passes to Google Analytics in an effort to help support your organization’s marketing. Google Analytics is “the” place organization’s go to get data and insight on their website, including where conversions are coming from, traffic volume, how much time visitors spend on their site, and more.

GTAG has been implemented into the Regpack system, which will seamlessly push data into Google Analytics, including 4 registration events from your system. All you have to do is link your Google Analytics account in Regpack (in one quick step!) and Regpack will do the rest!

Note: You must use the tagging options in Google Analytics to work with this functionality correctly!

Connecting Google Analytics and Facebook in your Regpack Account

Getting this set up is easy!

Simply login to your Regpack account and go to Settings > Project Settings. Under the “General” tab, simply input your Google Analytics ID number. Here is a helpful article on setting up Google Analytics if you haven’t already.

The image below shows you where to find the Google Analytics field in Project Settings.

 Computer program

Just underneath you’ll find the Facebook Pixel field.

 Product design

The following events are tracked through the pixel in Google:

  1. Sign-up: When a user registers, this will be tagged as engagement.
  2. Payment Issued: This will fire when a payment is issued, including the value of it. It will be tagged as “e-commerce”.
  3. Form View: When a user views a form, tagged as “registration_Process”
  4. Form Complete: When a user completes a form, also tagged as “registration_process”

Note that these actions are only recorded on the front-end of your system, not the back end activities.

The following events are tracked through the pixel in Facebook:

  1. Page View: When a user views a form, tagged as “registration_Process”
  2. View Content: This is a visit to a web page.
  3. Purchase: this fires at the same time “Payment Issued” fires for Google, noted above. This fires on every payment issued, and does not fire on payments made in the back-end.
  4. Submit Application: This is the same as the “sign-up” event in Google, and it’s fired when a user is created.
  5. Complete Registration: When a registration form is completed.

To get started setting up a conversion event using these events in Google Analytics, read this article as a guide. For seasoned Google Analytics users, you simply want to select “Event” as your goal type when setting up a new Goal. Standard events for the Facebook pixel can be viewed here.

Where to view this data:

In Google Analytics, can view this data under the Behavior Tab. On the left-hand side, simply click Behavior > Events, Event Category = Regpack.

You can also generate reports based on these events. The article mentioned above has a breakdown of this, but here’s an overview:

  • Goal Values in Acquisition Reports
  • Multi-Channel Funnels / Attribution Reporting
  • Page Value Reporting

Form URL’s in Regpack

We have also updated the backend to show the specific URL of all forms, so you can select any form as a conversion event in Google Analytics.

This can be found at the bottom of the form edit dialog. Simply click Settings > Forms > Hover, Click “Edit Form Properties”, then scroll down to the “Form Info” section, as shown below.

Head to settings, forms. Hover over the form you want the URL of, and click “Edit Form Properties”:

 Product design

Then scroll to the bottom and you will have the form URL listed under “Form Info”. Place www.regpacks.com before the rest of the URL shown here:

 Message transfer agent  Product design


Creating Conversion Events in Google Analytics

Learn more about creating conversion events in Google Analytics here. The video below is also a great guide to get started!



Creating Goals with Registration Events

If you’d like to connect a specific goal with a GA event, or if you want to trigger a goal based on these events, do the following:

  1. Click on your Admin gear icon and go to the “Goal” section.
  2. Create a new goal.
  3. In the setup, create a custom goal and press “continue”.
  4. In Goal Description, name the goal and set the goal type as “event”. Press “continue”.
  5. In Goal Detalis, set the category to be equal to Regpack.
  6. Depending on the action you want to trigger an event based off of, use the action equal to the correct event.
  7. Keep the Label field blank.
  8. Set the value to Greater than Zero.
  9. Turn off the toggle “Use the Event Value as the Goal Value for the conversion”. You can set a monetary value here as well.
  10. Save!

Cross Domain Tracking

You can set up cross-domain tracking by modifying the tracking code. Learn more about this here. Note that in the article linked in the previous sentence, you need to do steps 1 and 2 only. Step 3 has already been implemented on our side and once steps 1 and 2 are implemented, it will work seamlessly.

To set up cross-domain tracking for multiple top-level domains, you need to modify the Analytics tracking code on each domain. You should have a basic knowledge of HTML and JavaScript or work with a developer to set up cross domain tracking. The examples in this article use the Universal Analytics tracking code snippet (analytics.js).

Set up a property in your Analytics account. For cross-domain tracking, set up one property in your Analytics account. Use the same tracking code snippet and tracking ID from that property for all of your domains. You need to edit the tracking-code snippet for cross-domain tracking to work. If you haven’t already included the snippet on all your webpages, you might want copy and paste it into a text editor before continuing with the instructions here. This way, you only have to make the changes once before including the modified snippet on all your webpages.

Edit the tracking code for the primary domain. Find the create line in the snippet. For a website called example-1.com, it looks like this: ga(‘create’, ‘UA-XXXXXXX-Y’, ‘example-1.com’);

Make the following changes to the snippet (the changes you need to make are in bold red text): ga(‘create’, ‘UA-XXXXXXX-Y’, ‘auto’, {‘allowLinker’: true}); ga(‘require’, ‘linker’); ga(‘linker:autoLink’, [‘example-2.com’]);

Remember to replace the example tracking ID (UA-XXXXXX-Y) with your own tracking ID, and replace the example secondary domain (example-2.com) with your own secondary domain name.

The tracking-code snippet must contain these changes every place it appears on your primary domain. For three or more domainsFollow the example above, but add the other domains to the autoLink plugin. Even the additional comma here is important:ga(‘linker:autoLink’, [‘example-2.com’, ‘example-3.com’] );See an example of the complete code snippetThe tracking code snippet on your primary domain should look like this: <script>(function(i,s,o,g,r,a,m){i[‘GoogleAnalyticsObject’]=r;i[r]=i[r]||function(){ (i[r].q=i[r].q||[]).push(arguments)},i[r].l=1*new Date();a=s.createElement(o), m=s.getElementsByTagName(o)[0];a.async=1;a.src=g;m.parentNode.insertBefore(a,m) })(window,document,’script’,’//www.google-analytics.com/analytics.js’,’ga’);ga(‘create’, ‘UA-XXXXXXX-Y’, ‘auto’, {‘allowLinker’: true});ga(‘require’, ‘linker’);ga(‘linker:autoLink’, [‘example-2.com’] );ga(‘send’, ‘pageview’);</script>


Utm Tracking in Regpack System Fields

Regpack also tracks the URL that users began their registration journey, and can even pull out the UTM parameters in that URL if they exist.

In order to view and report on this information, you’ll need to create a report in Regpack and add those system fields to the report. You can set the report as “Info View” if you’d like to view this information in the user panel, or simply filter for the users you’d like this information on (like everyone who ordered a specific product) and then run the report.

UTM - Image

As you can see above, you can view the UTM source, medium, campaign, as well as the full URL for every user.