Segment targeting
AppLovin MAX SDK version 12.6.0 introduces a privacy-safe way to target waterfalls. The APIs introduced in this version target a generic key-value numeric pairing. You are responsible for mapping the segment key and the applicable value(s) that represent the users you target.
For example, you could establish segments that represent the genres that interest a user.
You could represent these segments with the key number 849.
Genre values might include “horror”, “thriller”, and “romance”.
You could represent these by the values of 1, 2, and 3 respectively.
The following code shows how you would add a user to the horror and romance genre segments, if you defined your keys and values in that way:
val initConfig = AppLovinSdkInitializationConfiguration.builder( "«SDK-key»" )
.setMediationProvider( AppLovinMediationProvider.MAX )
.setSegmentCollection( MaxSegmentCollection.builder()
.addSegment( new MaxSegment( 849, Arrays.asList( 1, 3 ) ) )
.build() )
.build();
⋮
AppLovinSdk.getInstance( this ).initialize( initConfig, sdkConfig -> {
⋮
val initConfig = AppLovinSdkInitializationConfiguration.builder("«SDK-key»")
.setMediationProvider(AppLovinMediationProvider.MAX)
.setSegmentCollection(MaxSegmentCollection.builder()
.addSegment(MaxSegment(849, listOf(1, 3)))
.build()
)
.build()
⋮
AppLovinSdk.getInstance(this).initialize(initConfig) { sdkConfig ->
⋮
}
MASegmentCollection *segmentCollection = [MASegmentCollection segmentCollectionWithBuilderBlock:^(MASegmentCollectionBuilder *builder) {
[builder addSegment:[[MASegment alloc] initWithKey:@(849) values:@[@(1), @(3)]]];
}];
ALSdkInitializationConfiguration *initConfig = [ALSdkInitializationConfiguration configurationWithSdkKey:@"«SDK-key»"
builderBlock:^(ALSdkInitializationConfigurationBuilder *builder) {
builder.mediationProvider = ALMediationProviderMAX;
builder.segmentCollection = segmentCollection;
}];
let segmentCollection = MASegmentCollection { builder in
builder.add(MASegment(key: 849, values: [1, 3]))
}
let initConfig = ALSdkInitializationConfiguration(sdkKey: "«SDK-key»") { builder in
builder.mediationProvider = ALMediationProviderMAX
builder.segmentCollection = segmentCollection
}
MaxSegmentCollection collection = MaxSegmentCollection.Builder()
.AddSegment(new MaxSegment(849, new List<int>() {1, 3}))
.Build();
MaxSdk.SetSegmentCollection(collection);
MaxSdk.InitializeSdk();
AppLovinMAX.addSegment( 849, [1, 3] );
AppLovinMAX.initialize( «SDK-key» ).then( ( conf: Configuration ) => {
})
AppLovinMAX.add_segment(849, [1, 3])
AppLovinMAX.initialize(«SDK-key», init_listener)
AppLovinMAX.addSegment( 849, [1, 3] );
MaxConfiguration? sdkConfiguration = await AppLovinMAX.initialize(«sdk-key»);
AppLovinMAX.addSegment(849, [1, 3]);
AppLovinMAX.initialize(«SDK-key», function (configuration) {
});
For an example of how you can use segment targeting, see SDK integration guides > Platform > Overview > Data and keyword passing.
You can either choose not to target by segment (Do Not Enable) or you can choose to target by segment (Enable) and then type in a subset of those numeric mappings that your app passes to MAX, as «segment»:«value» pairs that conform to the following rules:
- You must put a plus (to indicate inclusion) or minus (to indicate exclusion) in front of each segment.
- To negatively target a property value, put a
-in front of the segment (for example,-849:2targets those devices for which the segment849does not have the value2). - To target a set of values for one segment, pass each value with the segment individually.
The following example matches campaigns for which the value of the
849segment is 1, 2, or 3:+849:1, +849:2, +849:3 - There is no way to target a range of values (other than by targeting each value in the range individually, or negatively targeting each value outside the range).
- The comma in comma-separated values functions as an ∨ (or) operator.
A new line functions as an ∧ (and) operator. So, for example,
means [( §849≡1 ) ∨ ( §850≡2 )] ∧ [( §849≡1 ) ∨ ( §851≡3 )].+849:1,+850:2 +849:1,+851:3 - The minimum segment value is
0; the maximum is32000.
Cookieの設定