Analytics FAQ

What program does sherpa° use to track analytics?

We currently use Google Data Studio to track analytics. We provide you with a link to your dashboard, which you can check for real-time updates. Sherpa° is presently working and reviewing Amplitude as our go-to analytics tracking platform.

When can I get my analytics dashboard?

Your partner success manager will provide you with a dashboard 2 to 3 weeks after you go live.

What is the best performing placement?

We recommend putting Sherpa° on your most viewed pages and using highlighted banners so it can attract the majority of users' attention. Our data shows that the most effective placements are the home page, COVID-19 information dedicated page, newsletters, booking confirmation, manage my booking, and emails (pre-travel and trip reminder). Many of our partners successfully gained traffic and revenue streams from other digital marketing channels, such as social media.

How often is the analytics information updated on the dashboard?

All the information and data in the dashboard will be auto-updated daily.

How do you keep track of visits?

We provide you with a data studio dashboard for all the analytics, including information on total number of users to each solution you are using, Top popular corridors searched, category devices that users use, users locations (based on their browsers), placements (where users are coming from), etc.
Depending on the solutions you use, we may have additional information regarding most engaged content (WebApp), funnel information (Trip), etc.

What is the average Engagement Rate at sherpa°?

The Average Engagement Rate highly depends on the industry you are operating in. However, we believe a good Engagement Rate should be higher than 40%, which means that more than 40% of users will interact with our products by hovering over the map, searching for a trip, or clicking on any functionality.

Do you collect any conversion data for eVisas?

We track the conversion rate displayed in the dashboard and update it daily. You can look back at the conversion rates for different periods by adjusting the time frame in the top-right corner.

What does it mean when I see unknown, (other), (not set) or (other)?

User Corridor Search chart - these will show up if a user performs a search that is not a country, for example, searching by region or airport code.
Placement performance chart - these will show up if the placement parameter is missing in the integration code.

What does it mean when I see (direct) in the traffic source chart?

Traffic that arrives when someone types in your website's URL in a browser, opens your website through a bookmark or when Google Analytics cannot recognize the traffic source

What region codes do you use?

Check out more information about our region code mapping here.

Capturing analytics data from Map and Trip Element

📘

By Request Only

The sdkEventRequirementsSearch is a Feature flag which can be turned on by request. Please contact your PSM if you would like to use it.

Prior to implementation, please ensure you are filtering for the sdkLoaded event by including the following code:

if(event.type === 'sdkLoaded'){
// sdk is ready, create and mount new elements
$sherpa.V2.createElement(....)
}

The 'sdkLoaded' event type is not the only one available for you to watch for. By watching for the event type of 'sdkEventRequirementsSearch', which is sent each time a user searches for a trip using either the Trip or Map Element, you can capture valuable analytics about the trip they searched.

By creating a function that listens for an event from the sherpa° SDK, you can capture this analytics data when the event type detected is 'sdkEventRequirementsSearch'.

// onSherpaEvent needs to be declared before the script is loaded
function onSherpaEvent(event){
  if(event.type === 'sdkEventRequirementsSearch'){
    // a trip has been searched
    // capture analytics data from the returned data object here
    // see below for an example of the returned data structre
    console.log(JSON.stringify(event.data));
  }
}

Below is an example of the data structure returned by the browser with the 'sdkEventRequirementsSearch' event.

{type: "sdkEventRequirementsSearch", data: Array[2], scope: "@joinsherpa/v2", elementId: "Y1NDI"…}
data: Array[2]
    0: Object
        data: Object
            attributes: Object
                travelNodes: Array[2]
                    0: Object
                        countryCode: "CAN"
                        departure: Object
                            date: "2022-06-13"
                            time: "00:00"
                            travelMode: "AIR"
                            __proto__: Object
                        type: "ORIGIN"
                        __proto__: Object
                    1: Object
                        arrival: Object
                            date: "2022-06-13"
                            time: "00:00"
                            travelMode: "AIR"
                            __proto__: Object
                        countryCode: "MEX"
                        type: "DESTINATION"
                        __proto__: Object
                traveller: Object
                    nationality: "CAN"
                        vaccinations: Array[1]
                            0: Object
                                status: "FULLY_VACCINATED"
                                type: "COVID_19"
                                __proto__: Object
                            __proto__: Object
                type: "DEPARTURE"
                __proto__: Object
            type: "ITINERARY"
            __proto__: Object
        __proto__: Object
    1: Object
        data: Object
            attributes: Object
                travelNodes: Array[2]
                    0: Object
                        countryCode: "MEX"
                        departure: Object
                            date: "2022-06-20"
                            time: "00:00"
                            travelMode: "AIR"
                            __proto__: Object
                        type: "ORIGIN"
                        __proto__: Object
                    1: Object
                        arrival: Object
                            date: "2022-06-20"
                            time: "00:00"
                            travelMode: "AIR"
                            __proto__: Object
                        countryCode: "CAN"
                        type: "DESTINATION"
                        __proto__: Object
                traveller: Object
                    nationality: "CAN"
                    vaccinations: Array[1]
                        0: Object
                            status: "FULLY_VACCINATED"
                            type: "COVID_19"
                            __proto__: Object
                    __proto__: Object
                type: "RETURN"
                __proto__: Object
            type: "ITINERARY"
            __proto__: Object
        __proto__: Object
elementId: "Y1NDI"
scope: "@joinsherpa/v2"
type: "sdkEventRequirementsSearch"

When a user searches for a trip, report the event with the following properties:

Property nameDescription
OriginOrigin entered by the user
ConnectionAny connections entered by the user
DestinationDestination entered by the user
isRoundTripA boolean flag displaying if a round trip has been selected.
Date RangeDate ranges entered by the user
PassportPassport entered by the user

Are there plans to add more Analytics events like 'sdkEventRequirementsSearch' ?

Currently, Sherpa° does not have any plans to make further events available. Partners are welcome to contact our Partner Success and partner Support teams so we can review specific use cases.