Support Home > Campaign Management > Kochava for Agencies – SAN Campaign/Postback Setup

Kochava for Agencies – SAN Campaign/Postback Setup

The following document goes over how to create SAN campaigns and postbacks as an agency within the Kochava platform.


Campaign Creation

In order for Kochava to properly associate installs to their respective campaigns/segments/trackers in the Kochava dashboard, the Tracker ID must be appended to the campaign name within the associated SAN (e.g., Facebook, Google). To setup Twitter campaigns, refer to the steps outlined in the Create Kochava Twitter Campaign support document(attribution windows will not be available to agencies).

 

BEST PRACTICES: It is recommended that marketers create trackers for each SAN that agencies will be running with (do not assign an agency to this tracker). This tracker will act as a catch-all in the case that any agency you are working with neglected to place their Tracker ID in the SAN dashboard.

 

  1. Log in to Kochava.
  2. Select the desired Account and App.
  3. Select Links > Campaign Manager.
  4.  

 

  • Locate the desired Campaign, and Tracker. Expand to locate the Tracker ID.
  •  

     

  • Copy and add the Tracker ID to the campaign name within the SAN UI.
  • NOTE: If agencies have been given access to or created a tracker for a SAN network the above steps need to be taken in order for data to flow to the correct accounts.


    Postback Creation

    In order to send a real-time feed of installs and in-app events to an endpoint or to a Kochava-Certified partner, the marketer must setup a postback configuration. For more information about a Custom Postback or a Kochava-Certified Postback, refer to our support documentation. Below are explanations for setting up SAN postbacks when agencies are involved.

    1. Where to Create SAN Postbacks
      1. SAN Install & Event postbacks should ONLY be setup under the Advertiser’s Parent Account. Agencies cannot create SAN postbacks. SAN Media Partners are a different use case and will be covered in the Network Specific Call Outs section.
    2. Setting the Delivery Method in the parent account
      1. Network Only should NOT be used when tracking SAN Campaigns with an Agency.
      2. Use Network Only + Agency (only applicable for Facebook, Yahoo!, etc.) if the Parent Advertiser is running with a SAN network, but ONLY wants to send events linked to Installs attributed to that SAN network. This delivery method selection will ensure that events tied to that network for either Parent Advertiser or Agency trackers will be transmitted via postback.
      3. NOTE: Do not use this Delivery Method for non-SAN network partner postbacks.

      4. Use All if the Parent Advertiser wants to send every event to the SAN network, whether they were driven by that SAN network, any other network or were unattributed.

      NOTE: This Delivery Method must be used if you want to track Reengagement/Retargeting with a SAN Network. It should also be employed if you want to provide the SAN with all event data to use functions like Facebook’s Custom Audience creator or to populate Remarketing Lists with Google AdWords.

    3. For setups specific to each SAN, see detailed steps below.

    Apple Search Ads

    1. If one does not already exist, create a default Apple Search Ads tracker from the Advertiser’s Parent access. Do not assign this tracker to any agency. If an agency does not properly include the Kochava Tracker ID within the Apple Search Ads campaign names (see next step), this tracker will serve as a catch-all to ensure activity for those campaigns are still captured.
    2. The Agency must create or be assigned an Apple Search Ads tracker with their agency selected. The Agency must ensure that the numerical Kochava Tracker ID from this ‘Agency’ tracker is included within all Campaign Names in the Apple Search Ads Dashboard.
    3. No Install or Event Postbacks are required for Apple Search Ads.

    DoubleClick

    1. At this time, the data provided by DoubleClick’s SAN integration does not support Kochava for Agencies. All tracking using the DCM SAN integration and Floodlight Tags must be facilitated through the Parent Advertiser account. The agency will need to rely on the Parent Advertiser for access to Reporting.
    2. Be sure to provide the Parent Advertiser with any Floodlight Tags that need to be added to the client-side Postback Configuration.

    Facebook & Instagram

    1. If they do not already exist, create a default Facebook tracker AND a default Instagram tracker from the Advertiser’s Parent access. Do NOT assign these trackers to any agency. If an agency does not properly include the Kochava Tracker IDs within the campaign names in Facebook Ads Manager, these trackers will serve as a catch-all to ensure activity for those campaigns is still captured.
    2. The Agency must be assigned or create Facebook & Instagram trackers with their Agency selected. When running with Facebook, if you include Instagram as a property in your campaigns, be sure to insert both the Facebook & Instagram Tracker IDs within the campaign names in Facebook Ads Manager. You can separate the Tracker IDs with an underscore or hyphen. If you keep your Instagram efforts distinct from Facebook, then simply put the Facebook Tracker ID in the Facebook campaigns and the Instagram Tracker ID in the Instagram campaigns. This will facilitate mapping of Facebook vs. Instagram claims to the appropriate Agency trackers.
    3. If running Reengagement/Retargeting with Facebook & Instagram, please ensure:
      1. Facebook Event Postbacks in Parent Account are set to ‘Delivery Method’ of “All”.
      2. Individual Facebook & Instagram Reengagement trackers must be created on the Parent Account (without an Agency selected), which tag the specific event for conversion. If multiple events will be considered for reengagement conversion, a separate Tracker must be created for each distinct event.
      3. Per the prior point, the Agency must also create equivalent Reengagement Trackers for Facebook & Instagram within their profile. The Tracker IDs need to be included within these retargeting campaign names in Facebook Ads Manager.
    4. When employing a Facebook Media Partner (i.e., Nanigans, Sprinklr… etc.), please ensure:
      1. Agency must create or be assigned an FMP tracker for both Facebook & Instagram with their Agency selected.
      2. Within the Facebook campaign names, include both Tracker IDs with an underscore or hyphen to separate them. Also ensure that the proper FMP Naming Convention is followed, format is outlined here. This will facilitate mapping of claims to the appropriate FMP tracker for Facebook or Instagram.
      3. The Agency needs to setup the FMP Facebook & FMP Instagram Postbacks within their account. Recommended ‘Delivery Method’ selection is “Network Only”.
      4. If running Reengagement with an FMP, be sure to setup FMP Reengagement Trackers for Facebook & Instagram, which tag the individual events considered for conversion.

    NOTE: If Reenagement is being run with an FMP, but not natively with Facebook, then Facebook Reengagement trackers are still required. Facebook event postbacks with a ‘Delivery Method’ of All, are also still required. These entries facilitate the flow of event data to Facebook, by which Kochava can receive claims against that activity.


    Google Adwords

    NOTE: Only Google AdWords (Network ID: 5465) supports Kochava for Agencies. If you’re using the legacy ‘Google AdMob – Android’ or ‘Google AdMob – iOS’ networks, Agency is not supported. Contact your Kochava Client Success Manager for more details.

    NOTE: iOS Search via Google is not part of the Google AdWords SAN Integration. To track Google iOS Search, create trackers using the “Google Search iOS” network entry within the Agency profile. The click URL should then be added within AdWords as the ‘Tracking Template’ within URL Options. No Postbacks are required for Google iOS Search.

    1. If one does not already exist, create a default Google AdWords tracker from the Advertiser’s Parent access. Do NOT assign this tracker to any agency. If an agency does not properly include the Kochava Tracker ID within the AdWords campaign names (see next step), this tracker will serve as a catch-all to ensure activity for those campaigns is still captured.
    2. The Agency must create or be assigned a Google AdWords tracker with their agency selected. The Agency must ensure that the numerical Kochava Tracker ID from this ‘Agency’ tracker is included within all Campaign Names in the AdWords Dashboard.
    3. For Post-Install Events to be transmitted via Postback to Google AdWords, Reengagement trackers must be created on the Parent Account (without an Agency selected), which tag the specific event for conversion. If multiple events will be considered for reengagement conversion, a separate Tracker must be created for each distinct event.
    4. If running Remarketing with Google AdWords, please ensure:
      1. Google AdWords event postbacks in Parent Account are set to ‘Delivery Method’ of “All”.
      2. Individual Google AdWords Reengagement trackers must be created on the Parent Account (without an Agency selected), which tag the specific event for conversion. If multiple events will be considered for reengagement conversion, a separate Tracker must be created for each distinct event.
      3. Per the prior point, the Agency must also create equivalent Reengagement Trackers for Google AdWords within their profile. The Tracker IDs need to be included within the remarketing campaign names in Google AdWords’ dashboard.

      NOTE: If multiple events are to be considered for conversion against a single campaign, the Agency can create a single Google AdWords Reengagement Tracker and tag multiple events within the “Event Matching” field. Then simply one Tracker ID can be placed within the AdWords Campaign Name, while allowing for conversion against multiple events.


    Snapchat

    1. If one does not already exist, create a default Snapchat tracker from the Advertiser’s Parent access. Do NOT assign this tracker to any agency. If an agency does not properly include the Kochava Tracker ID within the Snapchat campaign names (see next step), this tracker will serve as a catch-all to ensure activity for those campaigns is still captured.
    2. The Agency must create or be assigned a Snapchat tracker with their agency selected. The Agency must ensure that the numerical Kochava Tracker ID from this ‘Agency’ tracker is included within all Campaign Names in the Snapchat Dashboard.
    3. For Post-Install Events to be transmitted via Postback to Snapchat, Reengagement trackers must be created on the Parent Account (without an Agency selected), which tag the specific event for conversion. If multiple events will be considered for reengagement conversion, a separate Tracker must be created for each distinct event.
    4. If running Reengagement with Snapchat, please ensure:
      1. Snapchat event postbacks in Parent Account are set to ‘Delivery Method’ of “All”.
      2. Individual Snapchat Reengagement trackers must be created on the Parent Account (without an Agency selected), which tag the specific event for conversion. If multiple events will be considered for reengagement conversion, a separate Tracker must be created for each distinct event.
      3. Per the prior point, the Agency must also create equivalent Reengagement Trackers for Snapchat within their profile. The Tracker IDs need to be included within the reengagement campaign names in Snapchat’s dashboard.

      NOTE: If multiple events are to be considered for conversion against a single campaign, the Agency can create a single Snapchat Reengagement Tracker and tag multiple events within the “Event Matching” field. Then simply one Tracker ID can be placed within the Snapchat Campaign Name, while allowing for conversion against multiple events.

    5. When employing a Snapchat Partner (i.e., Amobee, Bidalgo… etc.), please ensure:
      1. Agency must create or be assigned a Snapchat Partner tracker with their Agency selected. Within the Snapchat campaign names, include the tracker ID. This will facilitate mapping of claims to the appropriate Agency tracker for the Snapchat Partner.
      2. Agency must provide Parent Advertiser with Snapchat Partner Account ID for placement within the regular Snapchat Postbacks.
      3. The Agency needs to setup the Snapchat Partner Postbacks within their account. Recommended ‘Delivery Method’ selection is “Network Only”.
      4. If running Reengagement with a Snapchat Partner, be sure to setup Reengagement Trackers for the Snapchat Partner, which tag the individual events considered for conversion.

      NOTE: If Reenagement is being run with a Snapchat Partner, but not natively with Snapchat, then Snapchat Reengagement trackers are still required. Snapchat event postbacks with a ‘Delivery Method’ of All, are also still required. These entries facilitate the flow of event data to Snapchat, by which Kochava can receive claims against that activity.


    Twitter

    1. Both Parent Advertiser & Agency must follow steps to authenticate their Twitter account with Kochava which is outlined here.
    2. If one does not already exist, create a default Twitter tracker from the Advertiser’s Parent access. Do NOT assign this tracker to any agency. If an agency does not properly include the Kochava Tracker ID within the campaign names in Twitter’s Dashboard (see next step), this tracker will serve as a catch-all to ensure activity for those campaigns is still captured.
    3. The Agency must create its own Twitter tracker from their Agency login and select their authenticated account(s) within. The Agency must ensure that the numerical Kochava Tracker ID from this ‘Agency’ tracker is included within all Campaign Names in the Twitter Dashboard.
    4. NOTE: Parent Advertiser needs to inform Agency on the desired “Attribution Window” selections within the Tracker. Only the settings from Parent Account tracker will be sent to Twitter.

    5. Parent Advertiser must create the Twitter Postbacks from their Kochava login.
    6. For Post-Install Events to be transmitted via Postback to Twitter, Reengagement trackers must be created on the Parent Account (without an Agency selected), which tag the specific event for conversion. If multiple events will be considered for reengagement conversion, a separate Tracker must be created for each distinct event.
    7. If running Reengagement/Retargeting with Twitter, please ensure:
      1. Twitter Event Postbacks in Parent Account are set to ‘Delivery Method’ of “All”.
      2. Individual Twitter Reengagement trackers must be created on the Parent Account (without an Agency selected), which tag the specific event for conversion. If multiple events will be considered for reengagement conversion, a separate Tracker must be created for each distinct event.
      3. The Agency must also create equivalent Reengagement Trackers for Twitter within their profile. The Tracker IDs need to be included within these retargeting campaign names in Twitter’s Dashboard.
    8. When employing a Twitter Partner (i.e., Adparlor, Ampush… etc.), please ensure:
      1. Parent Advertiser & Agency must still create regular Twitter trackers as previously described.
      2. The Agency must also create a Twitter Partner tracker with their Agency selected.
      3. Within the Twitter campaign names, Agency must include the Twitter Partner Tracker ID along with the proper Twitter Partner Naming Convention documented here. This will facilitate mapping of claims to the appropriate Agency tracker for the Twitter Partner.
      4. The Agency must setup the Twitter Partner Postbacks within their account. Recommended ‘Delivery Method’ selection is “Network Only”.
      5. If running Reengagement with a Twitter Partner, be sure to setup Reengagement Trackers for the Twitter Partner, which tag the individual events considered for conversion.

      NOTE: If Reenagement is being run with an FMP, but not natively with Twitter, then regular Twitter Reengagement trackers are still required. Twitter event postbacks with a ‘Delivery Method’ of All, are also still required. These entries facilitate the flow of event data to Twitter, by which Kochava can receive claims against that activity.


    Yahoo!

    1. If one does not already exist, create a default Yahoo! tracker from the Advertiser’s Parent access. Do NOT assign this tracker to any agency. If an agency does not properly include the Kochava Tracker ID within the Yahoo! campaign names (see next step), this tracker will serve as a catch-all to ensure activity for those campaigns is still captured.
    2. The Agency must create or be assigned a Yahoo! tracker with their agency selected. The Agency must ensure that the numerical Kochava Tracker ID from this ‘Agency’ tracker is included within all Campaign Names in the Yahoo! Media Dashboard.
    3. When employing a Yahoo! Partner (i.e., Kenshoo, Sprinklr… etc.), please ensure:
      1. Agency must create or be assigned a Yahoo! Partner tracker with their Agency selected.
      2. Within the Yahoo! campaign names, include both the Tracker ID and the proper FMP Naming Convention (documented here). This will facilitate mapping of claims to the appropriate Yahoo! Partner Tracker for the Agency.
      3. The Agency needs to setup the Yahoo! Partner Postbacks within their account. Recommended ‘Delivery Method’ selection is “Network Only”.

       
       

    Last Modified: Dec 14, 2021 at 1:35 pm