TUNE Cloud Mode Integration Beta

Send events to TUNE using RudderStack cloud mode.

After you have successfully instrumented TUNE as a destination in RudderStack, follow this guide to correctly send your events to TUNE in cloud mode.

Track

You can use the track call to record user actions along with any associated properties.

A sample track call is as shown:

javascript

rudderanalytics.track(
  "Product Purchased", {
    affId: '1sw11AX',
    amount: 30.0,
    transactionId: 'X112312'
  })

The following table lists the mappings between RudderStack and TUNE properties:

RudderStack property	TUNE property	Description
`properties.adv_sub`	`adv_sub`	Advertiser sub ID 1.
`properties.adv_sub{n}`	`adv_sub{n}`	Advertiser sub ID where {n} ranges from the values 2 to 5.
`properties.adv_unique{n}`	`adv_unique{n}`	Advertiser sub-unique ID where {n} ranges from the values 1 to 5.
`properties.affId`	`aff_id`	ID of the partner promoting the offer.
`properties.amount`	`amount`	Amount of the generated sale (on conversion).
`properties.conversionUniqueId`	`conversion_unique_id`	Non-expiring unique IDs.
`properties.goalId`	`goal_id`	Goal ID for the offer.
`properties.goalRef`	`goal_ref`	Reference ID of the goal for the offer. It only affects attribution only when no goal ID is provided.
`properties.offerId`	`offer_id`	ID of the offer in TUNE.
`properties.payout`	`payout`	Offer payout to the publisher.
`properties.promoCode`	`promo_code`	Promo code.
`properties.revenue`	`revenue`	Offer revenue from the advertiser.
`properties.securityToken`	`security_token`	Advertiser’s unique token string for conversion authentication.
`properties.status`	`status`	Conversion status. It can be one of the following: `approved` `rejected` `pending`
`properties.transactionId`	`transaction_id`	TUNE transaction ID.