1. Home
  2. Marketers
  3. Campaign Management
  4. Create a Line Ads Campaign
  1. Home
  2. Marketers
  3. Create a Line Ads Campaign

Create a Line Ads Campaign


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

Data Needed Before Beginning Process:

  • Line Mobile App ID
  • Line Advertiser ID

Create a Line Ads Acquisition Tracker

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

Feature Note: To add this menu item to your Favorites Menu, select the “+” sign that appears when you hover over the menu. The Features Menu provides quick access to your most frequently visited areas of the Kochava UI.

  1. Select the desired Campaign & Segment, or create new ones.
  2. Click + Add (Tracker)

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.

  1. Enter a unique Tracker Name.

NOTE: When a Tracker is created, Kochava automatically generates a name for the Tracker. We recommend that you replace the Tracker name at this point with a clear name of your choosing.

  1. Select the Tracker Type > Acquisition. (default setting)
  2. Select Media Partner:
    1. Line Ads – iOS
    2. Line Ads – Android
  3. Select an Agency Partner. (optional)

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.

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

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.

  1. Enter the Install Destination URL.
  2. Enter a Deep Link. (optional)

NOTE: For more information about deep links, refer to our Deep Linking support documentation.

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

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.

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.

  1. Click Save. (If no further trackers need to be created)
  2. Click Save & Add Another Tracker. (If additional trackers need to be created)
  3. Click Save & Create Postback. (To navigate directly to the Partner Configuration page).

Create a Line Ads Install Postback Configuration

  1. Select App Configurations > Partner Configuration.

Feature Note: To add this menu item to your Favorites Menu, select the “+” sign that appears when you hover over the menu. The Features Menu provides quick access to your most frequently visited areas of the Kochava UI.

  1. Click + Add a Partner.
  2. Select Network Partner > Line Ads – iOS/Android.
  3. Click Next.
  4. Verify Status: Active.
  5. Click Save.
  6. Expand Line Ads Partner Configuration.
  7. Click Install > (Edit).
  8. Enter the Mobile App ID.
  9. Enter Advertiser ID.
  10. Select the Delivery Delay.
  11. Select the number of Retry Attempts.
  12. Select the Delivery Method.
  13. Click Save.

Note: For more information on Data Sharing Controls, see this support documentation.


Create a Line Ads Reengagement Configuration

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

Create a Reengagement Tracker:

  1. Navigate to Engagement > Campaign Manager.
  2. Select the desired Campaign & Segment, or create new ones.
  3. Click + Add (Tracker).
  4. Enter a Tracker Name.
  5. Select Tracker Type > Reengagement.
  6. Select Media Partner:
    1. Line Ads Platform – iOS
    2. Line Ads Platform – Android
  7. Select an Agency Partner. (optional)
  8. Select the Destination URL Type.
  9. Enter the Install Destination URL.
  10. Enter a Deep Link. (optional)
  11. Add a Custom Parameter. (optional)
  12. Select the Line Event.
  13. Click Save (If no further trackers need to be created).
  14. Click Save & Add Another Tracker. (If additional events need to be created).
  15. Click Save & Create Postback. (To navigate directly to the Partner Configuration page).

Create a Line Ads Post-Install Event Postback

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 Configurations > Partner Configuration.

Feature Note: To add this menu item to your Favorites Menu, select the “+” sign that appears when you hover over the menu. The Features Menu provides quick access to your most frequently visited areas of the Kochava UI.

  1. Click + Add a Partner.
  2. Select Network Partner:
    1. Line Ads – iOS
    2. Line Ads – Android
  3. Click Next.
  4. Verify Status: Active.
  5. Click Save.
  6. Expand Line Ads Partner Configuration.
  7. Select + Add a Postback.
  8. Select the desired Event.
  9. Enter the Line Mobile App ID.
  10. Enter the Line Advertiser ID.
  11. Enter the Items path.
  12. Enter the Line Category IDs.

NOTE: Item and Category ID containers should contain the key to the items that you want to send as the Item or Category ID. For more information on the Item and Category ID containers, contact your Line Customer Service representative.

  1. Select the Event Type.
  2. Select the Delivery Delay.
  3. Select the number of Retry Attempts.
  4. Select the Delivery Method.

NOTE: If you want to include both users (users have LAP click/have not LAP click) to your LAP audience, please select All.

  1. Click Save.

Note: For more information on Data Sharing Controls, see this support documentation.


Line Event Detail

Open Event:
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 ip address. string
View Home Event:
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
user_agent Client user agent. string
ip_address Client ip address. string
View Category Event:
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
user_agent Client user agent. string
ip_address Client ip address. string
category_ids Category IDs. < string > array
View Item Event:
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 ip address. string
items View items. < Item > array
category_ids Category IDs. < string > array
Search Event:
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 ip address. string
keyword Search keyword. string
Add to Cart Event:
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 ip address. string
items Added items. < Item > array
category_ids Category IDs. < string > array
Purchase Event:
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 ip address. string
items Purchased items. < Item > array
category_ids Category IDs. < string > array
Level Achieved Event:
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 ip address. string
*level_id Achieved level ID. string
Tutorial Complete Event:
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 ip 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.
Custom Event:
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 ip address. string
name Custom event name. Maximum Length: 100 string
data Any string can be specified. Maximum Length: 100 string
Updated on April 22, 2026

Was this article helpful?