Support Home > Campaign Management > Create a Line Campaign

Create a Line Campaign

The following document defines the process for creating an Line campaign within Kochava.

 

Data Needed Before Beginning Process:

  • Line Client ID
  • Line Mobile App ID
  • Line Advertiser ID
  • Line Client Secret

Create a Line Campaign

  1. Log in to Kochava.
  2. Select the desired app.
  3. Select App Tools>Campaign Manager.
  4.  

     

  5. Click Add a Tracker or Select Segment Tools>Add a Tracker.
    1. Select the Campaign.
    2. Select the Segment.

    NOTE: In order to streamline the Campaign/Segment/Tracker creation process a feature has been added to allow the creation of campaigns and segments while creating a new tracker. For more information about creating a campaign or segment while adding a new tracker, refer to our Create an Install Campaign support document. support documentation.

     

     

  6. Enter a unique Tracker Name.
  7. Select the Tracker Type>Acquisition

    NOTE: By default the Tracker Type is set to Aquisition.

  8. Select Media Partner:
    1. Line 2.0 – iOS
    2. Line 2.0 – Android

    NOTE: The Share With Publisher setting allows the associated publisher to view the settings for this tracker. By unchecking this box, the associated publisher will not be able to view the settings for the tracker.

  9. Select a Agency Partner. (optional)
  10.  

    A. CHeck to allow Publisher to view settings for the tracker.

     

  11. Select the Destination URL Type:
    1. Custom
    2. Google Referrer (Android Only)
    3. Landing Page

    NOTE: For more information on creating and using Landing Pages, refer to our Landing Page Creation and Maintenance support documentation.

    NOTE: Google Referrer is set as the default destination type for Android apps. For the majority of Android install campaigns, Google Referrer is used for optimal conversion tracking. Google Referrer will only appear for Android based apps. If the Google Referrer Install URL needs to be updated, refer to our Update Google Referrer Install URL support documentation.

  12. Enter the Install Destination URL.
  13. Enter a Deeplink. (optional)
  14. NOTE: For more information about deep links, refer to our Deep Linking support documentation.

  15. Add a Custom Parameter. (optional)
  16. NOTE: At the Campaign Level, advertisers can utilize the Custom Parameter fields to track any custom aspect of their campaigns that they define. You can use cp_0 through cp_9 and they will be populated within their own columns in reporting. For assistance with Custom Parameters, contact your Client Success Managers.

    1. Click Add a Parameter.
    2. Enter the Custom Parameter.
    3. Add additional Custom Parameters. (optional)

    NOTE: When a custom parameter is created, it is inserted automatically into the Click URL.

    NOTE: In order to remove a custom parameter, Click the “X” associated with the specific parameter.

     

    A. Custom Parameter

  17. Enter Pricing Type and Target Pricing. (optional)
  18. NOTE: Depending on the selected destination URL type, default and optional settings will vary.

     

    A. Enter any Optional Settings

  19. Click Save. (If no further trackers need to be created)
  20. Click Save & Add Another Tracker. (If additional trackers need to be created)

Reengagement Configuration

The information within this section provides the steps necessary to establish a reengagment campaign. If a reengagment campaign does not need to be created, the information in this section may be disregarded.

NOTE: An install tracker must be created in order for postback information to be sent.

 

Create a Reengagement Segment:

  1. Locate the desired Campaign.
  2. Select Campaign Tools>Add a Segment.
  3. Enter a Segment Name.
  4. Enter a Segment Description. (optional)
  5. Click Submit.

 

Create a Reengagement Tracker:

  1. Click Add a Tracker or Select Segment Tools>Add a Tracker.
    1. Select the Campaign.
    2. Select the Segment.
  2. Enter a Tracker Name.
  3. Select Tracker Type>Reengagement.
  4. Select Media Partner:
    1. Line 2.0 – iOS
    2. Line 2.0 – Android
  5. Select an Agency Partner. (optional)
  6. Select the Destination URL Type:
    1. Custom
    2. Google Referrer (Android Only)
    3. Landing Page
  7. Enter the Install Destination URL.
  8. Enter a Deeplink. (optional)
  9. Add a Custom Parameter. (optional)
  10. Enter Pricing Type and Target Pricing. (optional)
  11. Select the Line Event.
  12. Click Save (If no further trackers need to be created).
  13. Click Save & Add Another Tracker If additional events need to be created).
  14.  


Postback Configuration

To comply with Line’s audience building tech, specific data points are required to be sent. If a reengagement campaign is going to be run without sending the specific data points, a custom postback configuration should be created.

 

BEST PRACTICES: The Meta key sent in the JSON object for the post install event needs to be added to the appropriate entry in the partner configuration.

 

  1. Select App Tools>Partner Configuration.
  2.  

     

  3. Click Add a Configuration.
  4. Select Network Partner:
    1. Line 2.0 – iOS
    2. Line 2.0 – Android
  5. Click Go.
  6.  

     

  7. Locate the desired post-install event.
  8. Click Postback Tools>Edit.
  9. Enter the Line Client ID.
  10. Enter the Line Mobile App ID.
  11. Enter the Line Advertiser ID.
  12. Enter the Line Client Secret.
  13. Enter the Items path.
  14. Enter the Line Category IDs.
  15. Select the Event Type.
  16. Select the Delivery Delay.
  17. Select the number of Retry Attempts.
  18. Select the Delivery Method.
  19. Click Save.
  20.  


Line Event Detail

Name Required Optional Description Schema
timestamp Timestamp when server received event (milliseconds). integer (int64)
mobile_app_id Mobile App ID. string
advertiser_id Advertiser ID. string
audience_id IDFA or Advertising ID. string
user_agent Client user agent. string
ip_address Client up address. string

Name Required Optional Description Schema
timestamp Timestamp when server received event (milliseconds). integer (int64)
mobile_app_id Mobile App ID. string
advertiser_id IDFA or Advertising ID. string
user_agent Client user agent. string
ip_address Client up address. string

Name Required Optional Description Schema
timestamp Timestamp when server received event (milliseconds). integer (int64)
mobile_app_id Mobile App ID. string
advertiser_id IDFA or Advertising ID. string
user_agent Client user agent. string
ip_address Client up address. string
category_ids Category IDs. < string > array

Name Required Optional Description Schema
timestamp Timestamp when server received event (milliseconds). integer (int64)
mobile_app_id Mobile App ID. string
advertiser_id IDFA or Advertising ID. string
audience_id IDFA or Advertising ID. string
user_agent Client user agent. string
ip_address Client up address. string
items View items. < Item > array
category_ids Category IDs. < string > array

Name Required Optional Description Schema
timestamp Timestamp when server received event (milliseconds). integer (int64)
mobile_app_id Mobile App ID. string
advertiser_id IDFA or Advertising ID. string
audience_id IDFA or Advertising ID. string
user_agent Client user agent. string
ip_address Client up address. string
keyword Search keyword. string

Name Required Optional Description Schema
timestamp Timestamp when server received event (milliseconds). integer (int64)
mobile_app_id Mobile App ID. string
advertiser_id IDFA or Advertising ID. string
audience_id IDFA or Advertising ID. string
user_agent Client user agent. string
ip_address Client up address. string
items Added items. < Item > array
category_ids Category IDs. < string > array

Name Required Optional Description Schema
timestamp Timestamp when server received event (milliseconds). integer (int64)
mobile_app_id Mobile App ID. string
advertiser_id IDFA or Advertising ID. string
audience_id IDFA or Advertising ID. string
user_agent Client user agent. string
ip_address Client up address. string
items Added items. < Item > array
category_ids Category IDs. < string > array

Name Required Optional Description Schema
timestamp Timestamp when server received event (milliseconds). integer (int64)
mobile_app_id Mobile App ID. string
advertiser_id IDFA or Advertising ID. string
audience_id IDFA or Advertising ID. string
user_agent Client user agent. string
ip_address Client up address. string
*level_id Achieved level ID. string

*level_id is automatically mapped to the “level_number” key from our standard events. To send the level_id, as required, “level_number” must be sent in the event data.

Name Required Optional Description Schema
timestamp Timestamp when server received event (milliseconds). integer (int64)
mobile_app_id Mobile App ID. string
advertiser_id IDFA or Advertising ID. string
audience_id IDFA or Advertising ID. string
user_agent Client user agent. string
ip_address Client up address. string
*level_id Achieved level ID. string

*level_id is automatically mapped to the “level_number” key from our standard events. To send the level_id, as required, “level_number” must be sent in the event data.

Name Required Optional Description Schema
timestamp Timestamp when server received event (milliseconds). integer (int64)
mobile_app_id Mobile App ID. string
advertiser_id IDFA or Advertising ID. string
audience_id IDFA or Advertising ID. string
user_agent Client user agent. string
ip_address Client up address. string
name Custom event name.
Maximum Length: 100
string
data Any string can be specified.
Maximum Length: 100
string

 
 

Last Modified: Aug 17, 2018 at 10:19 am