Using Fyber’s SDK for User Segmentation

Lately, developers have been asking us how we can support their user segmentation efforts. We know that user segmentation is crucial for developers who want to apply different monetization strategies to different groups of users. We’ve been considering these questions and would like to shed light on the capabilities of our SDK to support user segmentation rules for ad serving.

We’re happy to report that our SDK offers full compatibility with your pre-existing user segmentation rules, and even beyond that, we’re building more advanced tools to be rolled out this summer. By using our SDK in conjunction with the user segmentation rules you have put in place, you can serve ads to select groups of users.

contentmanagement (1)
Most commonly, we see developers separating their user pool into paying users vs. non-paying users, or new users vs. returning users. These user segments are often a core component of developers’ ad monetization strategies, influencing ad serving and targeting.

If you want to segment your users so that only non-paying users see ads, or so that paying users only see ads after a certain level, it’s simple to implement. By adding just a snippet of code, you can ensure that our SDK is only called to serve an ad when specific user segments encounter your ad placements.

Our developer portal contains a step-by-step guide to help you leverage our SDK capabilities for user segmentation rules.

-Jan Ustohal
Senior Product Manager


Read these next

Contact Us

    By sharing your information you are agreeing to receive communications in regards to any questions or requests submitted on this form. Fyber will keep your information solely for internal tracking purposes and will not use this information for any other purpose. You may request to delete the information provided at any time.

    If you send us a message by clicking the "Send" button, we use a recaptcha service provided by Google LLC to check whether the message was sent by a natural person or a computer program ("bot") in order to ensure that only valid user requests are forwarded to us. Google LLC processes personal information from your browser, such as your browser settings and your click behavior on this screen. Please refer to the Privacy Policy for further information on data processing procedures of our third-party services.

    Error: SSL certificate problem: certificate has expired