Regpack can push user activity directly to your Google Analytics account. Whether you are creating ads through AdWords, or simply checking Google Analytics to understand your users and their activity better, adding your tracking code in Regpack will be very useful!
To input your Google Analytics ID in Regpack, simply add your Tracking Code under Settings --> Project Settings --> General Tab.
The following events are tracked through the pixel in Google:
- Sign-up - When a user registers, this will be tagged as engagement.
- Payment Issued - This will fire when a payment is issued, including the value of it. It will be tagged as "e-commerce".
- Form View - When a user views a form, tagged as "registration_Process"
- 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.
Where to view this data:
On the left-hand side, 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
Creating Conversion Events in Google Analytics
Learn more about creating conversion events in Google Analytics here.
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:
- Click on your Admin gear icon and go to the "Goal" section.
- Create a new goal.
- In the setup, create a custom goal and press "continue".
- In Goal Description, name the goal and set the goal type as "event". Press "continue".
- In Goal Detalis, set the category to be equal to Regpack.
- Depending on the action you want to trigger an event based off of, use the action equal to the correct event.
- Keep the Label field blank.
- Set the value to Greater than Zero.
- Turn off the toggle "Use the Event Value as the Goal Value for the conversion". You can set a monetary value here as well.
- Save.
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 in Settings --> Forms --> "Edit Form Properties" --> the link is in the "Form Info" section.
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 domains
Follow 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.
You can view the UTM source, medium, campaign, as well as the full URL for every user.