Google Analytics (GA4) integration

Prerequisite: Before setting up the integration, make sure you contact the partner and open an account with them.

To activate or edit the integration:

1. To activate: In AppsFlyer, from the side menu, select Collaborate > Partner Marketplace. To edit: In AppsFlyer, from the side menu, select Collaborate > Active Integrations.
2. Search for Google Analytics (GA4) and select it.
3. Click Set up integration. You’re directed to the integration setup page.

The Google Analytics configuration only includes the Integration tab.

For a detailed description of the Partner Configuration Window Header, click here.

Configure the following settings:

1. In the Integration tab, select the app for the integration and turn Activate partner on.

   Note: The toggle must be on (activated) for as long as you work with the partner.

   For more details about partner activation, click here.

2. In Firebase App ID, enter the identifier of the Firebase app. To learn how to locate the Firebase App ID, see the Firebase documentation.
3. In API Secret, enter the API Secret used to authenticate postbacks to Google Analytics. An API Secret is generated through the Google Analytics user interface. To view, edit, or create a secret, follow the instructions in the Google documentation. When instructed to select a web data stream, choose an Android or iOS data stream instead.
4. Turn on Customer User ID to send the customer user ID (CUID) instead of the advertising ID (IDFA).

5. Under the Default postbacks section, for users from, select All media sources including organic.

    Note

   The install postback includes only the touchpoint details (media source, campaign name, and campaign ID).

AppsFlyer can send automatic postbacks to Amplitude following user installs, including both installs and re-engagements (including re-attributions). Re-engagements occur when a user who already has the app installed opens it after clicking a campaign link. Learn more about default postbacks.

In the Integration tab, map AppsFlyer in-app events to Google Analytics (GA4) events, sent via postbacks.

1. Turn on In-app event postbacks.

2. Click Add event to add an SDK event to the list. The following table describes the fields to complete:

   Parameter name	Description
   AppsFlyer event	The name of the event, as received from the AppsFlyer SDK integrated into your app. Tip: Don't see the event you are looking for? Make sure to activate the event on a device with a non-organic installation, and recheck. Type it in AppsFlyer event, then click Create custom. Read more about custom event mapping.
   mapped to partner event	The unique name or ID of each event, as defined on the partner's side. Possible mapping configurations are: Text field: Get the corresponding event ID from the partner. Drop-down box: Select the most suitable pre-defined AppsFlyer event. As is: Send the events as they are, without name mapping.
   for users from	Select the sending option for the event: All media sources including organic: Send postbacks for events attributed to any partner, as well as organic events.
   including	No data (default): Send only the event itself without any event values. Values and revenue: Send all the event parameters, including the revenue value (if exists in the event). Values without revenue: Send all the parameters excluding the revenue value.

3. [Optional] Click the Add condition icon () to set conditions for an event.
4. Click Save integration.
5. Send the event postback mapping

After you have set up the in-app event mapping, send your developer a table where each mapped event corresponds to a row with the following columns:

• AF event: Name of the AppsFlyer event.

• Mapped to Google event: Name of the event in Google Analytics.

   Important!

  Don’t use any of the Google reserved events as names for custom Google Analytics events.

• AF event parameters (MANDATORY): Predefined AppsFlyer event parameters that must be included in the event postback sent to Google Analytics.

   Important!

  It is mandatory to include all predefined AF event parameters within the event definition exactly as they are listed in the table; failure to do so will result in Google Analytics rejecting the postback.

The event mapping table

The following table includes all the Google Analytics events and their predefined AppsFlyer parameters. Send your developer a table containing just the events that you mapped.

 

Reserved Google event names

The following event names are reserved and cannot be used as custom event names:

• ad_activeview
• ad_click
• ad_exposure
• ad_query
• ad_reward
• adunit_exposure
• app_clear_data
• app_exception
• app_install
• app_remove
• app_store_refund
• app_update
• app_upgrade
• dynamic_link_app_open
• dynamic_link_app_update
• dynamic_link_first_open
• error
• firebase_campaign
• firebase_in_app_message_action
• firebase_in_app_message_dismiss
• firebase_in_app_message_impression
• first_open
• first_visit
• in_app_purchase
• notification_dismiss
• notification_foreground
• notification_open
• notification_receive
• notification_send
• os_update
• session_start
• user_engagement

The app_instance_id uniquely identifies a Firebase app installation, and the ga_session_id uniquely identifies a Firebase app session. Retrieve these values from the Firebase SDK, then send them to GA4 using the setAdditionalData API.

Let your developer implement the code to:

1. Collect the app_instance_id and the  ga_session_id fields from Firebase.
2. Call setAdditionalData, before the first launch, to include the app instance ID and ga_session_id,  in installs, sessions, and in-app events.

FirebaseAnalytics.getInstance(this).appInstanceId.addOnCompleteListener { task ->
   if (task.isSuccessful) {
       AppsFlyerLib.getInstance().setAdditionalData("app_instance_id", task.result)
    }
}

FirebaseAnalytics.getInstance(this).getAppInstanceId().addOnCompleteListener(task -> {
       if (task.isSuccessful()) {
           AppsFlyerLib.getInstance().setAdditionalData("app_instance_id", task.getResult());
       }
  });

let appInstanceId = Analytics.appInstanceID()
    AppsFlyerLib.shared().customData = ["app_instance_id": appInstanceId]

(void) fetchAnalyticsInstanceId {
           NSString *instanceID = [FIRAnalytics appInstanceID];
           [[AppsFlyerLib shared] setAdditionalData:@{@"app_instance_id": instanceID}];
}

using Firebase.Analytics;
    public class AnalyticsManager : MonoBehaviour
    {
        private async void Start()
        {
           AppsFlyer.initSDK(devKey, appID, this);
           string appInstanceId = await FirebaseAnalytics.GetAnalyticsInstanceIdAsync();
           Dictionary <string, string> customData = new Dictionary<string, string>();
           customData.Add("app_instance_id", appInstanceId);
           AppsFlyer.setAdditionalData(appInstanceId);
           AppsFlyer.startSDK();
        }
}

The ga_session_id uniquely identifies a session of a Firebase app. This value must be retrieved from the Firebase SDK and sent to GA4 using the setAdditionalData API.

Let your developer implement the code to:

1. Collect the ga_session_id field from Firebase.
2. Call setAdditionalData before the first launch to include the session ID (and app_instance_id, if used).
3. Use the key ga_session_id when calling the API.

FirebaseAnalytics.getInstance(this).sessionId.addOnCompleteListener { task ->
    if (task.isSuccessful) {
        AppsFlyerLib.getInstance().setAdditionalData("ga_session_id", task.result)
    }
}

FirebaseAnalytics.getInstance(this).getSessionId().addOnCompleteListener(task -> {
    if (task.isSuccessful()) {
        AppsFlyerLib.getInstance().setAdditionalData("ga_session_id", task.getResult());
    }
});

if #available(iOS 14.0, *) {
    Analytics.sessionID { sessionID, error in
        if let sessionID = sessionID {
            AppsFlyerLib.shared().customData = ["ga_session_id": sessionID]
        }
    }
}

- (void)fetchAnalyticsSessionId {
    if (@available(iOS 14.0, *)) {
        [FIRAnalytics sessionIDWithCompletion:^(NSString * _Nullable sessionID, NSError * _Nullable error) {
            if (sessionID) {
                [[AppsFlyerLib shared] setAdditionalData:@{@"ga_session_id": sessionID}];
            }
        }];
    }
}

using Firebase.Analytics;
using System.Threading.Tasks;
using AppsFlyerSDK;
using UnityEngine;
using System.Collections.Generic;

public class AnalyticsManager : MonoBehaviour
{
    private async void Start()
    {
        AppsFlyer.initSDK("yourDevKey", "yourAppID", this);

        // Get session ID
        string sessionId = await FirebaseAnalytics.GetSessionIdAsync();

        Dictionary<string, string> customData = new Dictionary<string, string>();
        customData.Add("ga_session_id", sessionId);
        AppsFlyer.setAdditionalData(customData);

        AppsFlyer.startSDK();
    }
}

Make sure the events in the postbacks you send to GA4 are registered and read by Google Analytics. There are two methods advertisers can use to view their data:

• Using GA4 Explorations, you can explore the raw event data with all associated parameters. Prerequisite: Big Query export must be set up in your property)
• The Events report enables advertisers to view their postback events. The report can be found under one or more report collections.
  For example, the Events reports can be found in the Life cycle or the Games reporting collections under Engagement > Events. 
  For more information on the Events report see the Google documentation.

• The Traffic acquisition report helps you understand where your website and app visitors are coming from.

  Under the Life cycle collection go to Acquisition > Traffic Acquisition).

  For more information on the Traffic acquisition report, see the Google documentation.