R7K12 Integration with Google Analytics¶
Google Analytics (GA for short) is a free service provided by Google for creating detailed statistics on website visitors. The statistics are collected on Google's server; the user only places JS code on the pages of their website. The tracking code fires when a user opens a page in their web browser (provided that JavaScript execution is allowed in the browser). Users of the service can define goals and navigation sequences. A goal can be a sales completion page, views of certain pages, or file downloads. Using this tool, marketers can determine which advertising campaigns are successful and find new sources of target audiences. What do you need for this?
- A Google Analytics account that data needs to be sent to. When you connect the integration, the system will ask for authorization; you will need your login and code.
- Access to the R7K12 service. Sign-in through your Google account is required for security and for providing high-quality service.
Setting up the integration in R7K12¶
Sign in to the R7K12 end-to-end analytics system with a Google account that has access to R7K12. Select your project.
Go to the “Integrations” tab and, in the “Analytics systems” section, select “Google Analytics”.
You need to set up the transfer of event data from the R7K12 end-to-end analytics system to your Google Analytics account. Events are sent using the Measurement Protocol.
Google Measurement Protocol is a platform for sending data to Google Analytics from an external environment. Data reaches Google Analytics through scripts installed on your website. Everything else you can send to Google Analytics manually, using a set of rules for collecting and sending hits, which make up the Google Measurement Protocol platform.
The “inquiry” and “request” events are sent to Analytics instantly. “Sales” are sent every day at 23:30.
When we set up data sending from R7K12 to Google Analytics, the data goes to all views.
Setting up the transfer of events in two types (dynamic and static):
- inquiry;
- request;
- sale.
Static events are needed when the visit ID is unknown (for example, a call from a Yandex business card). See the example below.
To create a webhook (event) transfer, click the “Create” button. In the window that opens, select the “Dynamic” event type, the “Inquiry” event, and the “Instantly” sending time. In the “Traking ID” field, enter your Google Analytics tracking ID.
In the following fields under “Additional parameters”, you need to specify these settings, which differ for each type of inquiry:
- Event for inquiries:
Copy the values from table 1 and paste them into the corresponding fields, as shown in the screenshot below.
Table 1 - Names and values of additional inquiry parameters
| t | event |
| ec | R7K12 |
| cid | CLIENTID GOOGLE UNIVERSAL |
| ea | recourse |
Fields in which you need to select values from the list are shown in bold. For manual entry, select “Custom value” from the list; you will then be able to type text in the field.
These are four required parameters indicating that we are sending an event, its action and category, as well as the client ID. After filling in all the required fields, click the “Save” button.
To create a static event for inquiries (or other events), follow the same steps as for a dynamic one, but select the “Static” value in the “Type” field.
2. Event for target requests:
To create an event transfer for inquiries, select the “Dynamic” event type, the “Request” event, and the “Instantly” sending time. In the “Traking ID” field, enter your Google Analytics tracking ID.
The set of parameters for the “request” event remains almost the same as for “inquiries”, except that a different event action is set here — “target_lead”, which indicates that this is a request:
Table 2 - Names and values of additional request parameters
| cid | CLIENTID GOOGLE UNIVERSAL |
| t | event |
| ec | R7K12 |
| ea | target_lead |
3. Event for transactions: To set up the transfer of sales, in addition to the required parameters, where the event action (a sale) is specified, you also need to specify parameters that are important for analytics:
- campaign source;
- campaign medium;
- campaign content;
- keywords.
To create a transaction event transfer, select the “Sale” event type and the “23:30” sending time. In the “Traking ID” field, enter your Google Analytics tracking ID.
The set of parameters for the “sale” event:
Table 3 - Names and values of additional sale parameters
| cid | CLIENTID GOOGLE UNIVERSAL |
| t | event |
| ea | purchase |
| ec | R7K12 |
| pa | purchase |
| tr | REVENUE |
| ti | VISIT ID |
To set up transaction events, in addition to the required parameters, where the event action (a sale) is specified, you also need to specify parameters that are important for analytics:
- campaign source;
- campaign medium;
- campaign content;
- keywords.
The settings of static and dynamic events for the same event differ only in the event type selected in the settings window.
Setting up goals in Google Analytics¶
Go to the Google Analytics interface via this link, then to the “Admin” tab.
Select the required view (usually “All Web Site Data”). For that view, click the “Goals” button.
To create a goal, click the “+ NEW GOAL” button.
Next, select the “Custom” goal template and click “Continue”.
Enter the goal name, select the “Event” goal type, and click Continue.
In the “Category” and “Action” fields, enter the values for the events. Then click “Save”.
Breakdown of the events you want to send from R7K12 to Google Analytics:
- For “inquiry” events: category - R7K12, action - recourse.
- For “request” events: category - R7K12, action - target_lead.
- For “sale” events: category - R7K12, action - purchase.