Support Home > Campaign Management > Create a Spotify SAN Campaign

Create a Spotify SAN Campaign

Feature Summary: The following document describes how to set up a campaign for Spotify – SAN. Kochava enhances your install and event data with the Spotify ad impression or click metadata directly from Spotify to allow for extremely accurate and complete data.

 

Data Needed Before Beginning Process:

  • Spotify Product ID
  • Spotify Event Name

Create a Link for a Spotify – SAN Install Campaign

     

  1. 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.

     

    Tracker Settings

     

  2. Enter the Tracker Name.
  3. 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.

  4. Select Tracker Type > Acquisition. (default setting)
  5. Select Media Partner > Spotify – SAN.
  6. Select Agency Partner. (optional)
  7. Enter the Destination URL.
  8. NOTE: The Destination URL is not relevant and should simply be your website.

  9. Enter a Deep Link. (optional)
  10. Enter any Custom Parameter(s). (optional)
  11. Click Save. (If no further trackers need to be created)
  12. Click Save & Add Another Tracker. (If additional trackers need to be created)
  13. Click Save & Create Postback (to navigate directly to the Partner Configuration page).
  14.  

    Tracker Settings
    A. Campaign and Segment selection/creation section.


Install Postback Configuration

  1. Select Apps & Assets > Partner Configuration.
  2.  

     

  1. Click Add a Configuration.
  2. Select Media Partner > Spotify – SAN.
  3. Click Go.
  4.  

    Add a Postback

     

  5. Select Install > Postback Tools () > Edit.
  6. Enter the Spotify Product ID.
  7. Select the Spotify Event Name > first_open.
  8. Click Save.

 

Install Postback Settings


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: If a reengagement campaign does not need to be set up, but the data associated with post-install events needs to be sent to Spotify – SAN, follow the steps within the Create a Postback Section below.

 

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 > Spotify – SAN.
  5. Select an Agency Partner. (optional)
  6. Select the Spotify Event that will map to the selected Kochava event.
  7. Add Reengagement Event.
  8.  

    BEST PRACTICES: While multiple events can be added to the reengagement tracker it is highly recommended that only 1 event be added for each reengagmeent tracker.

     

    NOTE: A Reengagement event can be added by clicking on the “+” and removed by clicking “X“.

  9. Click Save (If no further trackers need to be created).
  10. Click Save & Add Another Tracker (If additional events need to be created).
  11. Click Save & Create Postback (to navigate directly to the Partner Configuration page).
  12.  

    Reengagement Tracker Settings
    A. Campaign and Segment selection/creation section.

 

Post-Install Event Postback Configuration:

  1. Select Apps & Assets > Partner Configuration.
  2.  

     

  1. Select Spotify – SAN > Network Tools () > Postbacks.
  2. Locate the desired event and Click Create for a new configuration or Edit for an existing configuration.
  3. Enter the Spotify Product ID.
  4. Select the Spotify Event Name.
  5. Click Save.
  6.  

    Reengagement Postback Settings


Standard Post-Install Event List:

 

KeyDescription
session_startWhen a user successfully launches an instant of the app.
page_viewThe user has viewed the page content.
start_trialWhen a user successfully signs up for a given trial product.
subscribeWhen a user pays for a subscription within a 24-hour lookback of exposure (impression or click) to a media campaign.
registration_completeWhen a user completes a user registration.
sign_upWhen a user completes an app sign up.
sign_inWhen a user completes an app sign in.
searchWhen a user completes a search.
share_with_friendLink shared with contact.
content_viewThe user has viewed the ad content.
first_video_viewWhen the user makes the initial video view.
video_streamVideo complete.
add_to_cartItem has been added to cart.
checkout_startCheckout process has been started.
purchaseItem has been purchased.
ad_viewThe user has viewed the ad content.
ad_clickThe user has clicked the ad content.

NOTE: Attribution will only performed by Spotify on IP or probabilistic matching.


Click and Impression Attribution Macros:

Click-through attribution, also known as click tracking, is the term used when a click leads to a user action within a certain attribution window. View-through attribution, also known as impression tracking, is the term used when an impression leads to a user action within a certain attribution window. The attribution window is supported for 7 day click lookback and 14 day impression lookback to meet your business needs.

 

URL ParametersDescriptionType
campaign_groupGroup of the campaignstring
campaign_nameName of the campaign.string
campaign_idID of the campaign.string
creative_nameName of the creativestring
creative_idID of the creative.string
site_idID of the site that served the ad.string
line_item_idThe LineItemId of the creative displayedstring
country2 Digit country code where ad was served.string
timestampUnix timestamp in seconds.integer
platformPlatform of the device.string

NOTE: Only campaign level metadata is passed to Kochava, no device level data is passed on attribution claims.


Example Attribution Response

Match:

{
"success": true,
            “attributionMode”: “BMA”, 
	"type": "impression",
	"metadata": {
		"creative_id": "Sample Creative",
		"site_id": "e734bc1af39681954243918812cb7009",
		"unix_date": "1476137388"
	},
	"match": {
		"idfa": "EA7583CD-A667-48BC-B806-42ECB2B48606"
	}
}

 

No Match:

{
    "success": false,
    "attribution_mode": "BMA",
    "type": null,
    "matched_by": null,
    "matched_by_keys": null,
    "metadata": null,
    "match": null
}

 
 

Last Modified: Oct 11, 2023 at 8:11 am