Enabling app attribution measurement in Kochava for Quantcast campaigns 

This article will guide you through the steps and recommendations to enable attribution measurement for Quantcast campaigns and create tracker links.

1. Add Quantcast as a partner network in Kochava.

   1. In the Kochava dashboard, go to apps & assets > partner configuration. Click on Add a Configuration, search for Quantcast in the Media Partner field, and click Go.

2. Configure Postback Events
   Postback allows Kochava to send a real-time feed of install and app events to Quantcast. The Kochava-certified postback is the most secure and reliable way to establish a postback and should be used as the default method. For more information, refer to Create a Kochava-Certified Postback.

   • After you select Quantcast in the Media Partner field, you’ll be shown all the standard and custom events. Locate the Install event and click the three dots to edit it. 

• On the edit postback page, fill out the form with the following details:

  • App Name: Enter the name of the app. This name will appear in the Quantcast Platform when creating a campaign with an app promotion goal. 

  • Platform: Enter the platform name. 

  • Quantcast ID: Enter the p-code.  Ensure “p—" is a prefix when entering the P-code. You can ask your account team for your p-code and the API key. You can also locate your P-code in the Quantcast Platform by clicking on the main navigation menu and ‘Accounts’ in the Organization Manager section. Locate your account and copy the P-code value. Make sure “p—" is included as a prefix. 

  • iOS Bundle ID/ Android Package Name: Enter the app bundle ID or app ID. The Package name is easily located in the app's URL on the Google Play store. (id=com. packagename). The Bundle ID must be obtained from the app developer, the app manager, or the Apple Store. For more information, refer to our Locating the Apple Bundle ID support document.

  • Quantcast API Key: Copy and paste the following API key into the API key field: 41c3048472464e13b1ec45f49aeac10c

  • Delivery Delay: Select ‘real-time delivery’ from the dropdown. The Delivery Delay determines whether the postback is delivered in real time or if there is an intentional delay before delivery. It can be set from 30 seconds to up to 10 minutes.

  • Retry Attempts: Select ‘3 attempts’ from the dropdown. The Retry Attempts determine the number of times Kochava will attempt to redeliver an event postback upon posting failure. They can be set from Do Not Retry to up to 10 attempts.

  • Delivery Method: Select ‘All’ if you are a direct advertiser or ‘Network + Agency’ if you are an agency. The Delivery Method determines whether Quantcast will receive all events/installs or only those attributed to Quantcast. Selecting ‘All’ or ‘Network + Agency’ is required when creating campaigns with the app promotion campaign goal.  

Repeat step 2 for each app event you want to share with Quantcast.

3. Configure Partner Reconciliation Settings
   If you skip this section or if reconciliation settings are not specifically set, ‘None Selected’ will be displayed and the corresponding default setting listed below will be applied. Default (unedited) settings will use the SAN’s Reconciliation lookbacks, not the standard 30/7/1 day settings used for all Kochava trackers. For more information, refer to Partner Reconciliation Settings and Attribution Overview in Kochava.

• Kochava’s reconciliation or attribution system works in a waterfall format. In the attribution waterfall, impressions are not weighted as heavily as clicks. The attribution waterfall follows the below priority: 

  • Click Attribution 

    • Device-based attribution. This is a deterministic attribution method that uses devices to perform the attribution match 

    • Fingerprinting. This is a probabilistic attribution method that uses an IP address and a user agent to perform the attribution match 

    • IP (full and partial) fingerprinting. This is a probabilistic attribution method that uses an IP address  to perform the attribution match 

• After click matching has been attempted, all unattributed installs are subject to impression matching.

  • Impression Attribution 

    • Device-based attribution. This is a deterministic attribution method that uses devices to perform the attribution match 

    • Fingerprinting. This is a probabilistic attribution method that uses an IP address and a user agent to perform the attribution match 

    • IP (full and partial) fingerprinting. This is a probabilistic attribution method that uses an IP address  to perform the attribution match 

• In the Kochava dashboard, go to apps & assets > partner configuration. Locate Quantcast, lick the three dots, and select  ‘Reconciliation’ from the dropdown. 

  • The reconciliation settings are divided into two sections: Impression and Click. Within each section, you can select the lookback window per reconciliation type. On the partner configuration page, fill out the form with the following details:

    • Impression Reconciliation

      • Device Lockback: Select 24 hours from the dropdown. Device Lookback determines how far back from the time of install to consider engagements for attribution on a standard device match. By default, the Device Lookback window is set to 24 hours.

      • Fingerprint Lookback: Select 24 hours from the dropdown. The Fingerprint Lookback window is set to 24 hours by default. It determines how far back from the time of install to consider engagements for attribution on a fingerprint-based match.

      • IP Lockback: Select 24 hours from the dropdown. IP Lookback determines how far back from the time of install to consider engagements for attribution on an IP-based match. By default, the IP Lookback window is set to Disabled.

      • Partial IP Lookback: Select 24 hours from the dropdown. Partial IP Lookback determines how far back from the time of install to consider engagements for attribution on a Partial IP-based match. By default, the Partial IP lookback window is set to Disabled.

      • Device Attribution Behavior: Select Standard from the dropdown. This Setting determines whether fingerprint matching will be attempted if a Device ID is present on click. The Standard setting will not attempt fingerprinting if a Device ID is present on click, while the Inclusive setting will attempt fingerprinting on all clicks. By default, the Device Attribution Behavior is set to Standard.

    • Click Reconciliation

      • Device Lockback: Select 30 days from the dropdown. Device Lookback determines how far back from the time of install to consider engagements for attribution on a standard device match. By default, the Device Lookback window is set to 30 days.

      • Fingerprint Lockback: Select 7 days from the dropdown. Fingerprint Lookback determines how far back, from the time of install, to consider engagements for attribution on a Fingerprint based match. By default, the Fingerprint Lookback window is set to seven days

      • IP Lockback: Select 23 hours from the dropdown. IP and Partial IP Lookback determines how far back from the time of installation to consider engagements for attribution on an IP or Partial IP-based match. By default, the IP and Partial IP lookback window is disabled.

      • Partial IP Lookback: Select 23 hours from the dropdown

      • Device Attribution Behavior: Select Standard from the dropdown.

      • Fingerprint Attribution Tier: Select Standard from the dropdown. Fingerprint Attribution Tier determines the Fingerprint validation configuration. The Standard setting validates based on a combination of IP Address and User Agent. The Full IP Address setting validates based on IP Address regardless of User Agent. The Partial IP Address setting validates based on the first three stanzas of the IP Address. By default, Fingerprint Attribution is set to Standard.

Here is a helpful table to guide you in choosing the appropriate attribution type for your mobile campaigns based on your use cases. 

• In the Kochava dashboard, go to links > campaign manager. Click ‘Add a Tracker’ or locate the desired campaign, click the three dots, and select  ‘Add a Tracker’ from the dropdown. 

• When creating a new tracker, you can create a campaign or a segment. Click the provided link to create a campaign or segment

• Enter the following information 

  • Campaign Name: Enter a unique campaign name 

  • Default Destination URL: Enter the URL of the app store 

  • Segment Name: Enter a unique segment name 

  • Segment Description: (optional) Enter a description of the segment 

• Select the campaign or segment you just created. Enter the following information  

  • Tracker Name: Enter a unique tracker name

  • Tracker Type: Select ‘Acquisition’ from the dropdown

  • Media Partner: Select ‘Quantcast’ from the dropdown

  • Agency Partner: (optional) Select the agency from the dropdown

  • Share with Publisher: Check the box. This ensures Quantcast can view the tracking URLs

  • Destination URL Type: Select Custom, Google Referrer (Android Only), or Landing page.

  • Install Destination URL: Enter the install URL

  • Deep Link: (optional) Enter the deep link

  • Custom Parameters: (optional) To determine the reporting breakdown in Kochava, you can add keys and values for custom parameters. Common custom parameters include campaign, ad set, and creative. In the value field, you can manually enter a value or use a Quantcast creative macro to insert a dynamic value. A full list of Quantcast creative macros can be found here. When you create custom parameters, they will be added to the click and impression tracking URLs automatically.

• Click Save 

Once you click save, the impression and click tracking URLs will be automatically generated. Copy the URLs and send them to the account team at Quantcast or apply them in the Quantcast Platform. 

Note: We recommend applying links directly in the Quantcast DSP instead of wrapping them in tags. It allows easy troubleshooting, and applying links in the ad server can cause discrepancies.