The following document defines the process for creating a Google Adwords reengagment campaign.

---

Create a Reengagement Tracker

NOTE: For Google to receive post-install event information, a re-engagement tracker must be created for each event individually that you wish to pass to Google. If attribution does not need to be tracked, ensure that the proper options are configured in the postback configuration for Google Adwords.

NOTE: Free App Analytics does not award install credit to a campaign type that is not a UA campaign.

 

BEST PRACTICES: If you do not wish for post install events to be claimed by Google, be sure to exclude them from your bid strategy when configuring your conversion events in Google.

 

1. Log in to Free App Analytics.
2. Select the desired Account and App.
3. If not already created, create a new Google campaign. For more information about creating campaigns, refer to our Google Ads support documentation.

 

BEST PRACTICES: In order to help with campaign organization, it is recommended that a segment be created for reengagement.

 

4. Enter a unique Tracker Name.
5. Select the Tracker Type > Reengagement.
6. Select Media Partner > Google Adwords.
7. Select the Destination URL Type > Custom. (default setting)
8. Enter a Deep Link. (optional)
9. Enter any Custom Parameters. (optional)
10. Add desired reengagement Event.
11. Click Save if no additional trackers need to be created.
12. Click Save & Add Another Tracker if additional trackers need to be created.
13. Click Save & Create Postback. (To navigate directly to the Partner Configuration page).

 

A. Campaign and Segment selection/creation section.
B. Click “+” to add a reengagement event.

---

Create a Reengagement Postback

BEST PRACTICES: Google strongly suggests that marketers enable any and all post-install events which are being being tracked by Free App Analytics. Any event that is configured will send ‘All’ occurrences of the event to Google.

BEST PRACTICES: Google strongly suggests the instrumentation of post-install events to track sessions as well as ‘deeplink’ events.

BEST PRACTICES: If the Event Name field is left empty, the original event name received from the app will be used. After the Custom Event may be used for any post-install events that do not correspond to one of Google’s pre-defined App Event Types.

 

Post-install events sent to Google must be designated with the corresponding Google App Event Type using the drop down menu within the Partner Configuration UI. Google has eight event types to select:

• Custom
• Session Start
• In_App Purchase
• View Item List
• View Item
• View Search Results
• Add to Cart
• eCommerce Purchase

NOTE: The ‘Custom’ event may be used for any post-install events that do not correspond to one of Google’s pre-defined App Event Types.

1. Select Apps & Assets > Partner Configuration.

 



 


2. Click Add a Configuration.
3. Select Network Partner > Google Adwords.
4. Click Go.
5. Locate the desired Post-Install Event, Click Postback Tools (⋮) > Create.

 



 

6. Enter the Link ID.
7. Select the App Event Type
8. If using the Custom Event Type, Enter an Event Name. (optional)

NOTE: If using the ‘Custom’ event designation and the Event Name field is left blank, the Event as called out within the Kochava UI will be passed to Google by default. If an event name is entered, that customer defined name will be passed to Google instead.

9. Enter the Kenshoo Customer ID. (optional)
10. Enter the Septini Customer ID. (optional)
11. Enter the Sprinkler Customer ID. (optional)
12. Enter the Cyberagent Customer ID. (optional)
13. Enter the Cognant Customer ID. (optional)
14. Enter the Marin Software Customer ID. (optional)
15. Enter the AI Media Group Customer ID. (optional)
16. Enter the Bidalgo Customer ID. (optional)
17. Enter the Yahoo! Japan Customer ID. (optional)
18. Enter the Wisebirds Customer ID. (optional)
19. Enter the Adquant Customer ID. (optional)
20. Select the Delivery Delay.
21. Select the number of Retry Attempts.

NOTE: The default setting for Delivery Method is set to All and cannot be modified.

22. Click Save.

 

---

Deeplinks & Google Ads Web to App Connect

Google Ads requires click parameters to attribute third-party app conversions resulting from non-app campaign ad clicks. If auto-tagging and deeplinking are enabled in Google Ads, Google will append the GCLID (Google Click Identifier) to the landing page url. Once redirected into the app, the GCLID can be extracted by Kochava, and passed to Google Ads, allowing Kochava to attribute app conversions to a specific ad campaign click.

Additionally, Google has introduced a new cohort identifier called gBraid, which enables privacy safe measurement under ATT of iOS app conversions driven by Search, Shopping, Display, & Performance Max campaigns . The gBraid parameter is also appended to the landing page url, allowing Kochava to attribute activity to a device in a group of devices, without identifying that particular user.

• Implement and enable _Deeplink event. For more information refer to our support documentation.
• For details on enabling auto-tagging, refer to Google’s support documentation.
• For more information on gBraid, refer to Google’s overview and set up.

---

Google Universal App Campaign for Engagement Setup

Linking Google UAC to Google Play:

1. Log in to Google Ads Account.
2. Click Tools>Setup>Linked accounts.

 



 

3. Click Google Play>Details.
1. If Google Play Developer and Ads Account has not been linked, Click Link.
1. Enter the email address of the Google Play Developer administrator.
2. Click Send.

 



A. Enter the email address of the Google Play Developer administrator.

3. Once the Google Play Developer administrator has approved the request, the accounts will be linked.
2. If Google Play Developer and Ads Account have been linked, Click “+” to link additional accounts.
1. Enter the email address of the Google Play Developer administrator.
2. Click Send.

 



A. Enter the email address of the Google Play Developer administrator.

3. Once the Google Play Developer administrator has approved the request, the accounts will be linked.

---

Creating a Deeplink Event:

For Google to track UACe campaigns, Google requires the advertiser to have a _deeplink event that has the deeplink listener included in that call. Once this is done correctly, Kochava will parse out the GCLID from the _deeplink event metadata and pass it on to Google. The GCLID is a parameter that is appended to the end of a deeplink URI and helps Google optimize the UACe campaigns.

 

WARNING: Before a Google UACe campaign can be initiated, and Kochava can receive the Google Click ID (GCLID) developers will first need to instrument the standard _Deeplink event in the Kochava SDK or through Server-to-Server. When instrumented to specification, the _Deeplink event will include the GCLID in the URI field of the event payload. For details about deeplinking, refer to our Android – Using the SDK or iOS – Using the SDK documentation.

1. Select App Tools (⋮) > Partner Configuration.

 



 

2. Click Add a Configuration.
3. Select Network Partner > Google Adwords.
4. Click Go.
5. Locate the Deeplink Post-Install Event, Click Postback Tools (⋮) > Create.

    

   
    

6. Enter the Link ID.
7. Select App Event Type > Session Start
8. Enter the Event Name (optional)
9. Enter the Kenshoo Customer ID. (optional)
10. Enter the Septini Customer ID. (optional)
11. Enter the Sprinkler Customer ID. (optional)
12. Enter the Cyberagent Customer ID. (optional)
13. Enter the Cognant Customer ID. (optional)
14. Enter the Marin Software Customer ID. (optional)
15. Enter the AI Media Group Customer ID. (optional)
16. Enter the Bidalgo Customer ID. (optional)
17. Enter the Yahoo! Japan Customer ID. (optional)
18. Enter the Wisebirds Customer ID. (optional)
19. Enter the Adquant Customer ID. (optional)
20. Select the Delivery Delay.
21. Select the number of Retry Attempts.
22. Click Save.