Advanced settings

Configure advanced SDK settings such as custom parameters, price floors, and user segmentation to optimize ad delivery and monetization.

Read time 13 minutes

Set UserID

If you’re using server-to-server callbacks to reward your users with ironSource rewarded ad units, or using Ad Quality user journey, you must define a unique identifier for each user (“UserID”), using the setUserID method. Set the UserID before the init request, to make sure you avoid any data losses, related to the user. Use a unique identifier, with a format of 64 characters NSString. 

IronSource.setUserId(userID)

Define Segments

You can now easily tailor the way you serve your ads to fit a specific audience! You'll need to inform our servers of the users' details so the SDK will know to serve ads according to the segment the user belongs to.

ironSource supports three methods to convey data to our servers to outline the user segment, namely:

  • Device Properties: the ironSource SDK collects certain standard parameters that pertain to the users' device automatically such as device model, device manufacturer, app version, OS, etc. You do not need to convey this data to us
  • User Properties: user data which is not collected by our SDK, such as age, gender, creation date, etc. (see full list of supported segment properties with descriptions below) must be relayed through the API. Follow the instructions to send us these details so our SDK can apply the relevant ad settings to the segments you defined on the ironSource platform
  • Custom Segments: you can create a custom segment with predefined conditions without conveying user details to our servers and tailor ad settings for that user segment on the ironSource platform

Pass User Properties

Once you've defined segments on the ironSource platform, you should inform our servers of the user's particulars.

First, init the segment:

let segment: ISSegment = ISSegment()

Define what properties to send to our servers on which to base the segments. You can transmit this information through one of the following methods:

  1. If you are familiar with the segment that the user belongs to, enter the segment name:

    segment.segmentName = "YOUR_SEGMENT_NAME"
    
  2. Send us the user details. ironSource provides a range of standard user properties that you can set to attribute a user to a segment in the API. See table below for descriptions.

    // Set user age
    segment.age = USER_AGE
    // Set user gender
    segment.gender = ISGender.IRONSOURCE_USER_FEMALE
    // Set user's total in-app purchases
    segment.iapTotal = USER_IAP_TOTAL
    // Set user's level
    segment.level = USER_LEVEL
    // Set user's paying status
    segment.paying = USER_PAYING_STATUS
    // Set user creation date
    segment.userCreationDate = NSDate() as Date!
    

    In addition, you can set up to 5 custom user properties per segment:

    segment.setCustomValue("CUSTOM_VALUE", forKey: "CUSTOM_KEY")    
    

    Next, to serve your ad units based on segments, call the following function complete with either the segment name or user properties:

    IronSource.setSegment(YOUR_SEGMENT);
    

Supported Segment Properties

Segment PropertiesTypeLimitationDescription
segmentNameString- alphanumeric - up to 32 lettersThe given name of the segment in your ironSource account
AgeInt1-99The user's age
GenderenumIRONSOURCE_USER_MALE or IRONSOURCE_USER_FEMALEThe user's gender
PayingBooleanYes or No- True if the user has spent any money on in-app purchases - False if the user has not spent any money on in-app purchases
iap_totalDouble1-999999.99The total amount of money that the user has spent on in-app purchases
userCreationDateNSDateCannot be smaller than 0The date the user installed the app
Custom Parameterskey=string, value=string- ironSource supports up to 5 custom parameters - alphanumeric - up to 32 lettersAny additional data you'd like to dispatch to our server

Obtain the User's Segment Name

  1. Adopt this interface in your class to conform to the Segment Name protocol and enable the receipt of the segment name [icode]ISSegmentDelegate[/icode]

  2. Register to the following delegate to receive the segment name that your user belongs to. The SDK will then notify your delegate of the event.

    IronSource.setSegmentDelegate(self)
    
  3.  (void)didReceiveSegement:(NSString *)segment
    
    func didReceiveSegement(_ segment: String!)
    

Custom Parameters for iOS

The ironSource SDK supports custom parameters for Rewarded Video. You can pass custom parameters upon the initialization of the ad unit and receive the parameters upon a user's completion event.

You can now pass custom parameters for all mediation networks on Unity LevelPlay.

Implementation Code

Rewarded Video

  • Custom Parameters can be set several times per session.
  • To reset the value, use clearRewardedVideoServerParameters, and then set the new value.
[IronSource setRewardedVideoServerParameters:(NSDictionary *)parameters];
[IronSource clearRewardedVideoServerParameters];

Price floor configuration

The Floor Configuration API lets you set a price floor for a specific ad unit. By setting a price floor for each user, you can improve targeting efficiency, reduce latency, and optimize ad performance. The price floor must be assigned when creating the ad object, and it applies to all subsequent loads for that object.

Note: Min SDK version for this feature is 8.9.0.

PropertiesTypeDescription
Bid floordoubleThe price in USD that defines the minimum eCPM applied to traditional instances and bidders.

Intersitial Ads Example

// Define a price floor configuration
LPMInterstitialAdConfig *adConfig = [[[LPMInterstitialAdConfigBuilder new] setBidFloor: 1.23] build]; // Set the price floor in USD
// Apply the configuration to an interstitial ad unit
LPMInterstitialAd *interstitialAd = [[LPMInterstitialAd alloc] initWithAdUnitId:@"adUnitId" config:adConfig];
// Define a price floor configuration
let adConfig = LPMInterstitialAdConfigBuilder()
.set(bidFloor: 1.23) // Set the price floor in USD
.build()
// Apply the configuration to an interstitial ad unit
let interstitialAd = LPMInterstitialAd(adUnitId: "adUnitId", config: adConfig)

Full interstitial implementation here

Rewarded ads Example

// Define a price floor configuration
LPMRewardedAdConfig *adConfig = [[[LPMRewardedAdConfigBuilder new] setBidFloor: 1.23] build]; // Set the price floor in USD
// Apply the configuration to a rewarded ad unit
LPMRewardedAd *rewardedAd = [[LPMRewardedAd alloc] initWithAdUnitId:@"adUnitId" config:adConfig];
// Define a price floor configuration
val adConfig = LevelPlayRewardedAd.Config.Builder()
.setBidFloor(1.23) // Set the price floor in USD
.build()
// Apply the configuration to a rewarded ad unit
val rewardedAd = LevelPlayRewardedAd("adUnitId", adConfig)

Full rewarded ads implementation is available here.

// Define a price floor configuration
LPMBannerAdViewConfig *adConfig = [[[LPMBannerAdViewConfigBuilder new] setBidFloor: 1.23] build]; // Set the price floor in USD
// Apply the configuration to a banner ad unit
LPMBannerAdView *bannerAd = [[LPMBannerAdView alloc] initWithAdUnitId:@"adUnitId" config:adConfig];
// Define a price floor configuration
let adConfig = LPMBannerAdViewConfigBuilder()
.set(bidFloor: 1.23) // Set the price floor in USD
.build()
// Apply the configuration to a banner ad unit
let bannerAd = LPMBannerAdView(adUnitId: "adUnitId", adConfig)

ironSource SDK Error Codes

ironSource provides an error feedback mechanism to provide an explanation for any failure in the SDK integration. You will receive these errors when something went wrong or an aspect of the integration wasn't completed correctly.

The ironSource Error object contains an error code and message. These are all the possible errors and their message based on their functions:

Error CodesAd UnitDescription
508N/A
  • Init failure of the mediation/Network
  • Calling a Demand Only API in non Demand Only mode
  • Calling a non Demand Only API in Demand Only mode
509Interstitial, Rewarded VideoShow Fail: No ads to show
510Interstitial, Rewarded Video, BannerLoad Fail: Server response failed
520Interstitial, Rewarded Video

Show Fail: No internet connection; ShouldTrackNetworkState is enabled Show Fail: No internet connection

524Interstitial, Rewarded Video

Show Fail: Placement %@ has reached its limit as defined per pace Show Fail: Placement %@ has reached its capping limit

526Interstitial, Rewarded VideoShow Fail: Ad unit has reached its daily cap per session
604BannerCan’t load because the placement is capped
605BannerUnexpected exception while loading the banner
606BannerNo banner fill on all the networks on the first load
1007Interstitial, Rewarded VideoAuction Fail: Auction request did not contain all required information
1022Rewarded VideoShow Fail: Cannot show an RV while another RV is showing
1023Rewarded VideoShow Fail: Show RV called when there are no available ads to show
1035InterstitialEmpty Waterfall
1036InterstitialShow Fail: Cannot show an interstitial while another interstitial is showing
1037InterstitialLoad Fail: Cannot load an interstitial while another interstitial is showing
1039InterstitialException while calling show interstitial