Native Ads Building Blocks in the Spotlight, Part I

At PubNative, our mission is to enable mobile publishers to effectively monetize their app with flexible native integrations that preserve their user experience. As we wrote in an earlier blog post, we believe that the current native advertising solutions available on the market (mostly those in the form of pre-defined templates that require to integrate an SDK) are not flexible enough to offer a genuine native experience to users. These “one-size-fits-all” solutions might be native in some context (usually, the context for which they have been designed, eg. in-feed ads), but in no case can they be fit for every app’s unique design. For this reason, one of the core USPs of PubNative is to offer flexible native ad integrations through an API. PubNative’s API allows publishers to request up to and over 25 elements (and counting, as we are constantly adding to the list) to serve as building blocks to create ads that truly match the form, the function and the content of their apps.

Harness the Flexibility

In order for publishers to better understand how they can harness PubNative’s flexibility, we would now like to cast light on these 25+ building blocks, through a series of blog posts aimed at explaining and visualizing how these elements can be used within apps. We start today with the first five elements, using two examples of apps that have integrated PubNative: Happy Mall Saga by Happy Labs and Adobe Air.

  1. The banner image
  2. The app title
  3. The app description
  4. The call-to-action
  5. The app icon

native ads adobe HMS For each element, we will specify the parameter name and format in the response, as well as, if applicable, the various values that can be requested. For the complete API documentation, head to our Developer Portal.

  1. The Banner Image

    • Parameter in the response: “banner_url”ad banner
    • Format of the response: URL
    • Banner dimensions which can be requested: “1200×627” (default), “640×334”, “300×50”, “320×50”, “300×250”, “320×480”, “480×320”, “1024×768”, “768×1024”
    • Description: The URL linking to the banner image used in the ad, also available in various dimensions (we will keep on adding to the list).

    banner image

  2. The App Name
    • Parameter in the response: “title”app title
    • Format of the response: string
    • Description: The app title provided by PubNative, which can be different from the one in the App Store (could be shorter, for instance).

     

    app name no shadow

  3. The App Description

    • Parameter in the response: “description”app description
    • Format of the response: string
    • Description: A short description of the advertised app provided by PubNative in over 10 languages that is different from the App Store’s description (again, shorter).

    app description no shadow

  4. The Call-to-Action
    • Parameter in the response: “cta_text”call to action
    • Format of the response: string
    • Description: The text that appears on the button leading to the App Store landing page of the advertised app.

    Call to Action

  5. The App IconIcon
    • Parameter in the response: “icon_url”
    • Format of the response: URL
    • Icon dimensions which can be requested: “50×50” (default), “100×100”, “150×150”, “200×200”, “256×256”, “300×300”, “400×400”
    • Description: The URL linking to the app’s icon, available in various dimensions.

    app icon no shadow

We hope the description and visualization of these five first elements has aided your understanding of how you can use PubNative to create beautiful ad units within your apps. For more inspiration, head to the “Integration Example” section of the Developer Portal. Stay tuned for the next installment of our Native Ads Building Blocks in the Spotlight series, where the next five elements will be unveiled. For any questions, do not hesitate to send us an email at blog@pubnative.net.

BACK

Leave a Reply

Your email address will not be published. Required fields are marked *