Skip to main content
All CollectionsReporting
Ambassify reporting and Google Analytics
Ambassify reporting and Google Analytics
Laurens Bobbaers avatar
Written by Laurens Bobbaers
Updated over 4 months ago

You can measure the success of your advocacy program via a wide range of metrics and indicators. If an important part of your use case is sharing articles from your website (e.g. landing pages, vacancies, blog articles, news), then clicks on shared posts and traffic can be interesting for you to measure.

Measuring clicks in Ambassify's Sharing Report

The Sharing Report in Ambassify gives you an overview of all the clicks that happened on the posts shared by your advocates via Social Share campaigns. For example, when your advocates share a link to your website on LinkedIn, it appears on their connections' feeds. Each time when someone clicks on the post to open the article, this is counted and reflected in the Sharing Report. Shared posts that receive a lot of clicks indicate that the content is found interesting and relevant by your advocates' network on LinkedIn.

Possible discrepancy between clicks and traffic in Google Analytics

Another way to measure the impact of your advocacy program, is to measure the traffic that it generates to your website. This can be done via UTM tracking, which is a built-in feature in your Ambassify account and can be tailored to your needs.

Clicks measured in Ambassify are not exactly the same as sessions in Google Analytics (GA). So, when you would compare the numbers in Ambassify and GA, you will find that there are some discrepancies.

This has to do with exactly what Google Analytics considers or can consider a session and depends on several factors. This article explains in more detail the difference between clicks on Google Ads and sessions in Analytics. The mechanism is similar to the discrepancies that may exist between the clicks that are measured in Ambassify, and the traffic measured in Analytics.

In summary, a click does not always result in a session, either for a “legitimate” reason (e.g. the same user clicks multiple times within a short period of time), or because of a problem when trying to report a session to GA (either a GA configuration problem, or simply a user's browser settings/configuration interfering).

The meaning of the values for 'Session medium' in Google Analytics

If you're tracking the UTM parameter 'medium', you may find the three different values in your GA. We'll briefly explain the difference:

  • Landing page: this means a link is shared from a landing page (publicly accessible) set up via Ambassify

  • Webview: this refers to a link shared from a “webviewed” community; our native app currently uses a “webviewed” community

  • App: this means a link is shared from a community (closed, accessible only to users with a login) to make the distinction with a landing page

Did this answer your question?