This page discussed features of the Kongregate SDK which are still included, but no longer required for new games to integrate.

Legacy Analytics Options

• Keen options:
  • KONGREGATE_OPTION_KEEN_PROJECT_ID - Your Keen project ID
  • KONGREGATE_OPTION_KEEN_WRITE_KEY - Your Keen write key
• AdX options (iOS only):
  • KONGREGATE_OPTION_ADX_ID - Your AdX ID
  • KONGREGATE_OPTION_APPLE_ID - Apple ID for referral tracking. You may find the Apple ID in iTunes Connect under App Information
  • KONGREGATE_OPTION_ADX_QA_UNTIL - A date (MM-DD-YYYY) up to 14 days in the future. Ad-X Events will be logged to QA server until the specified date. They may be viewed here: http://testing.ad-x.co.uk/QA/BUNDLEID
• AdX options (Android only):
  • KONGREGATE_OPTION_ADX_ENABLED - Enables AdX for Anddroid. Disabled by default for backwards compatibility.

  • Ad-X AndroidManifest.xml entries (for standard Google Play Store release). Ad-X manifest entries should go under the <application>tag.

    <meta-data android:name="APP_NAME" android:value="your.pagkage.name"/>
    <meta-data android:name="ADX_CLIENT_ID" android:value=CLIENT_ID />
    <meta-data android:name="NOIMEI" android:value="ON" />
    

  • replace CLIENT_ID with the Kongregate Client ID. You may find this in the sample AndroidManifest.XML file. your.package.name is your package name. We disable NOIMEI to prevent requiring the READ_PHONE_STATE premission.
  • This entry is used for referral tracking. You may add additional forward.<name> meta-tags to forward the INSTALL_REFERRAL action to other receivers. The <name> may be anything as long as it’s unique within the receivers meta-tags.

  <receiver android:name="com.kongregate.android.api.receivers.InstallReceiver" android:exported="true">
      <intent-filter>
          <action android:name="com.android.vending.INSTALL_REFERRER" />
      </intent-filter>
      <meta-data android:name="foreward.AdXAppTracker" android:value="com.AdX.tag.AdXAppTracker"/>
  </receiver>
  

  • To enable QA Mode set the following in your manifest. Be sure to disable before release. When enabled ad-x events may be viewed here: http://testing.ad-x.co.uk/QA/APPNAME

  <meta-data android:name="USEQASERVER" android:value="ON" />
  

• Ad-x for Amazon builds should include the following entries:

  <meta-data android:name="OTHERSTORE" android:value="AMAZON" />
  <meta-data android:name="STOREAPPID" android:value="<store_app_id>" />
  

• AdX options (General):
  • KONGREGATE_OPTION_ADX_UPGRADE - Forces AdX to track this installation as an upgrade as opposed to a new install. This is only needed if your game was previously released without Ad-X. See the installation tracking section for more details.

---

Legacy IAP Tracking

SDK 1.0.7.x track purchase flow

You can track purchases via Keen and AdX by using the startPurchase and trackPurchase methods on the analytics API object. They accept a product ID, quantity, and map of fields for the Keen event.

The product ID needs to be a specially crafted string that matches the name of the item in iTunes Connect and Google Play (minus the bundle ID or package name). For example: t05_hard might be the product ID for a hard currency item in pricing tier 5. Note that the tXX prefix is required to be 3 characters (t followed by the 2 digit pricing tier), so the leading zero is critical in this case.

The event fields should match the fields from iap_attempts and iap_transactions in your event schema.

The startPurchase method should be called at the beginning of the purchase flow.

The trackPurchase method should be called after the purchase is completed, including signature/receipt verification.