Google Ads

The following document defines the process for creating a Google Ads (UAC, Display, YouTube, etc.) campaign for iOS and Android.

 

Data Needed Before Beginning Process:

  • Google Ads Account
  • Link ID

NOTE: If you plan to leverage the Google Ads integration please contact your Account Management team.

NOTE: If you plan to use Search iOS or App extensions, utilize a SmartLink or VPPN. For more information, contact your Client Success Management team.


Create a Link ID within Google Ads

The following procedure provides the steps for creating a Link ID within Google Ads. For further details, contact a Google account representative.

NOTE: Only one Link ID per app is required. Android and iOS versions of the same app require separate link IDs. The Link ID provides the connection for the install and all post-install events for the associated app.

NOTE: If conversions need to be tracked across multiple accounts for a single app, either use cross-account conversion tracking and create the Link ID in the manager (MCC) account, or create the Link ID and share it across accounts. Create the link in the account that will be the owner of the link. Only the owner of the link can grant access and share the link to other accounts.

NOTE: After creating a new Link ID you MUST Import Mapped Conversions in the Google UI. This process MUST be completed whether you are creating your first Link ID or updating with a new Link ID for an existing app.

  1. Log in to Google Ads.
  2. Click Tools & Settings > Linked accounts.
  3.  

    Linked Accounts

     

  4. Select Third-party app analytics > Details.
  5.  

    Third Party App Analytics

     

  6. Click Create Link ID for the initial link in the account, or click “+” to add an additional link.
  7. Select App analytics provider > Kochava.
  8. Select your mobile app’s platform:
    • Android
    • iOS
  9. Locate the desired app.
  10. Click Create Link ID.
  11.  

    Create Link ID

     

  12. Copy and Retain the Link ID.

 

BEST PRACTICES: Do not close the Google Ads UI. After the setup process has been completed within Free App Analytics, mapped conversion events must be imported using the Google Ads UI.


Install Setup Process

NOTE: Kochava does not award install credit to a campaign type that is not a UA campaign.

 

BEST PRACTICES: It is HIGHLY recommended that a Tracker ID be appended to the partner campaign name e.g., the campaign name within the Google Ads UI. The Tracker ID can be easily located within Kochava’s Campaign Manager, expand the section below for instructions on locating the ID.

  1. Once a tracker has been created, navigate to Campaign Manager.
  2. Locate and click on the desired Campaign.
  3. Located the desired Segment, and click on the expand arrow.
  4. Locate the desired Tracker, and click on the expand arrow.
  5. Locate and copy the Tracker ID.

 

Locating Tracker ID

 

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

 

Create an Install Tracker:

  1. Log in to Free App Analytics.
  2. Select the desired Account and App.
  3. Create a new Tracker. For more information about Creating Trackers, click here.
  4. Enter a unique Tracker Name.
  5. Select the Tracker Type > Acquisition.
  6. Select Media Partner > Google Ads.
  7. Select an Agency Partner. (optional)
  8. Check Share with Publisher. (optional)
  9. Select Default Tracker:
    1. On
    2. Off (default)
    3. NOTE: Selecting On will allow SAN network traffic to funnel to the default tracker when no tracker ID is present. If a default tracker is not set up and the tracker ID is not appended to the partner campaign name, that data will be bucketed in the most recently set up tracker for that network.

  10. Select the Destination URL Type > Custom. (default selection)
  11. Enter a Deep Link. (optional)
  12. Enter any Custom Parameters. (optional)
  13. NOTE: The final URL is not required for tracking a Google campaign through Kochava, and should not be used.

  14. Click Save if no additional trackers need to be created.
  15. Click Save & Add Another Tracker if additional trackers need to be created.
  16. Click Save & Create Postback. (To navigate directly to the Partner Configuration page).

 

Acquisition Tracker Settings

A. Campaign and Segment selection/creation section.

 

Create an Install Postback:

  1. Select Apps & Assets > Partner Configuration.
  2.  

    Partner Configuration

     

  3. Click Add a Configuration.
  4. Select Network Partner > Google Ads.
  5. Click Go.
  6. Locate Google Ads Partner Configuration and Click Partner Configuration Tools () > Postbacks.
  7. Locate the Install Postback and Click Postback Tools () > Create.
  8.  

    Postbacks

     

  9. Enter the Link ID. (generated/obtained in the Google UI)
  10. Select App Event Type > First Open. (default setting)
  11. NOTE: The customer IDs that Google generates contains dashes, however the Google Ads API does not accept the customer ID with dashes. Remove the dashes from the customer ID when entering it into the relevant field in Free App Analytics.

  12. Enter the Kenshoo Customer ID. (optional)
  13. Enter the Septini iOS Customer ID. (optional)
  14. Enter the Sprinklr Customer ID. (optional)
  15. Enter the Cyberagent Customer ID. (optional)
  16. Enter the Cognant Customer ID. (optional)
  17. Enter the Marin Software Customer ID. (optional)
  18. Enter the AI Media Group Customer ID. (optional)
  19. Enter the Bidalgo Customer ID. (optional)
  20. Enter the Yahoo! Japan Customer ID. (optional)
  21. Enter the Wisebirds Customer ID. (optional)
  22. Enter the Adquant Customer ID. (optional)
  23. Check Send GCLID Only. (optional)
  24. NOTE: When checked, Kochava will send the GCLID when there are no other device IDs available. If this is not checked, then Kochava will not send Google a claim request unless there is a device ID to include.

  25. Select a Delivery Delay.
  26. Select the number of Retry Attempts.
  27. Click Save.

     

    Postback Settings

     


Post-Install Event Setup Process

NOTE: For Google to receive post-install event information, a re-engagement tracker must be created for the events you wish to pass to Google.

 

BEST PRACTICES: Google strongly suggests that marketers enable any and all post-install events that are 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 Deep Link events.

BEST PRACTICES: If the Event Name field is left empty, the original event name received from the app will be used. The Custom Event may be then 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.  

    Partner Configuration

     

  3. Using the Live Search locate the Google Ads postback configuration.
  4. Select Google Ads > Partner Configuration Tools () > Postbacks.
  5.  

    Postbacks

     

  6. Locate the desired post-install event.
  7. Click Postback Tools () > Create.
  8.  

    Postback Tools Edit

     

  9. Enter the Link ID.
  10. Select the App Event Type.
  11. If using the Custom Event Type, Enter an Event Name.
  12. NOTE: The customer IDs that Google generates contains dashes, however the Google Ads API does not accept the customer ID with dashes. Remove the dashes from the customer ID when entering it into the relevant field in Free App Analytics.

  13. Enter the Kenshoo Customer ID. (optional)
  14. Enter the Septini iOS Customer ID. (optional)
  15. Enter the Sprinklr Customer ID. (optional)
  16. Enter the Cyberagent Customer ID. (optional)
  17. Enter the Cognant Customer ID. (optional)
  18. Enter the Marin Software Customer ID. (optional)
  19. Enter the AI Media Group Customer ID. (optional)
  20. Enter the Bidalgo Customer ID. (optional)
  21. Enter the Yahoo! Japan Customer ID. (optional)
  22. Enter the Wisebirds Customer ID. (optional)
  23. Enter the Adquant Customer ID. (optional)
  24. Check Send GCLID Only. (optional)
  25. NOTE: When checked, Kochava will send the GCLID when there are no other device IDs available. If this is not checked, then Kochava will not send Google a claim request unless there is a device ID to include.

  26. Select a Delivery Delay.
  27. Select the number of Retry Attempts.
  28. Select the Delivery Method.
  29. NOTE: The default setting for Delivery Method is set to All and cannot be modified.

  30. Click Save.
  31.  

    Post Install Postback Settings


SKAD Credentials

  1. Select Apps & Assets > Partner Configuration.
  2.  

 

  1. Using the Live Search locate the Google Ads postback configuration.
  2. Select Google Ads > Network Tools () > Credentials.
  3. Enter the Login Customer ID(s) (Manager Account) for SKAdNetwork.
  4. Enter the Customer ID(s) for SKAdNetwork.
  5. NOTE: If multiple IDs are used, they should be comma-separated.

    NOTE: The Client Customer ID, SKAD Customer ID and Login Customer ID are located in the Google Ads Manager UI. The IDs that should be used are associated with the user who initially “logged in with Google” in the Free App Analytics UI. For more information about locating the Google IDs, refer to Google’s Find your Google Ads customer ID support document.

  6. Click Save.
  7.  

    Credentials Settings

     

    NOTE: Kochava pulls the aggregated SKAdNetwork performance data every 24 hours and collects all the SKAdNetwork performance data associated with that Customer ID.

     

    Important Note:
    The Client Customer ID, SKAD Customer ID and Login Customer ID are located in the Google Ads Manager UI. The IDs that should be used are associated with the user who initially “logged in with Google” in the Free App Analytics UI. The Client Customer ID(s) are customer IDs we will request cost data for and the SKAD Customer ID(s) are customer IDs we will request skad data for. The Login Customer ID(s) are the customer IDs of the Google Ads Manager Account(s) that have direct access to the provided Client and SKAD Customer IDs, but the Login Customer ID may not be required, depending on your Google Ads setup. For more information about locating the Google IDs, refer to Google’s Find your Google Ads customer ID support document and their Login Customer ID documentation


Import Mapped Conversion Events

  1. Click Tools, billing, and setting > Measurement > Conversions.
  2.  

    Adwords Measurement Conversions

     

  3. Click the plus button.
  4.  

    Adwords Plus Button

     

  5. Click Conversion Type > App.
  6.  

    Adwords Conversion Type App

     

  7. Select Third-party app analytics.
  8. Click Continue.
  9. Check the box next to each event to be imported.
  10. Click Import and continue.
  11.  

    The conversion events will now be present in the Conversion actions table. Event details may be viewed by click on the name of the event.


References

Related Documentation Link a 3rd party App Analytics Platform with Ads

If you use a third-party app analytics provider to track and measure your mobile app conversions, you can import data from your third-party app analytics platform by linking it to your Ads account.

 

Track App Conversions with 3rd Party App Analytics

If you use a third-party app analytics provider to track and measure your mobile app conversions then, you can import app conversion data from your provider.

 
 

Last Modified: Jul 26, 2023 at 8:45 am