Google Analytics is a free web analytics service, developed by Google to help you analyze your website traffic. It collects your web page visitors statistics and offers you rather many tools and reports for analyzing your online traffic.
To get more familiar with this service you can follow the link to the Google Analytics support page.
The integration allows:
- getting the main information of the call from your visitor (such as the caller ID, call duration, destination ID and visitor ID);
- checking the goals of the calls right in your reports in Google Analytics;
- identifying the traffic channels which bring you the callers and analyze their effectiveness.
The integration features:
Ringostat sends the calls data to Google Analytics as the events. You can find them in your Google Analytics property in the Reports menu selecting the Behavior > Events section.
The event categories, which can be sent to your goals:
- PROPER — the target calls, which are defined (calculated) depending on the configurations of a target call length and a sale cycle settings;
- REPEATED — the calls were repeated after the first target one within the sale cycle;
- ANSWERED — non-target answered calls;
- FAILED — the calls were failed, when the call forwarding number was not connected correctly (there might be some mistake in number/sip-account authorization configurations);
- NO+ANSWER (NO ANSWER) — missed calls;
- BUSY — the calls were missed, when all locations in a call routing scheme were busy;
- VOICEMAIL — the calls which were redirected to the voicemail;
- NO-FORWARD — the calls, which were missed because the call forwarding scheme didn't work or a number, the call was made to, wasn’t set to the call routing scheme;
- CLIENT+NO+ANSWER — the calls from the visitors, who sent a request for the callback but didn’t answer the call.
- NO+EXTENSION — the calls from the caller, who didn’t enter an extension number and wasn’t redirected to a reserve call routing scheme (only for IVR schemes);
- WRONG+EXTENSION — the calls from the visitors, who input a wrong extension number after the last try and wasn’t redirected to a reserve call routing scheme (only for IVR schemes).
To be able to see the calls in your reports you should set the goals for them in your Google Analytics property configurations.
Google Analytics calculates the goals in some specific way: only one call per session can be defined as a goal. All the further calls during the same session won't be counted as the successful goals.
1. The visitor made 2 calls to your number and didn't get the answer. In this case, only the first call will be counted as the goal, because both of them were made during the same session.
2. The visitor had made the first call and it was answered. The call got the status "target". Then, in 5 minutes, he or she made the second call and it got the status "repeated". In case you are looking for these calls in all call categories goal, you will find only the first one as the successful goal. However, if you are checking the goals for the proper calls and the repeated/answered calls separately, each of call will be defined as the successful goal in an appropriate one.
According to this method of calculating the goals, you might find the differences between your project statistics and your goals statistics in Google Analytics. So, for now, you know the reason.
The calls are attaching to the visitor sessions if you use the session-based call tracking. So, the call is pinned by the unique visitor ID, which Google Analytics attaches to every visitor session.
In case of the basic call tracking, things work a bit differently. Here we do not have any attaching to the session, but only to the number. So, Google Analytics generates the direct traffic channel for such calls in its statistics.