For those willing to fully control the design of their application, we provide a custom mode which literally allows you to compose you own ad unit design to perfectly fit in your applications.

Ad Unit Review Process


At Appsfire, we care a lot about User Experience.
This is why we implemented a review process for custom ad formats: we review all custom implementations of Sashimi to ensure they are reliable, perform as expected, and are free of offensive material. As you plan and develop your custom ad unit, make sure to use these guidelines and resources.
Our servers won't send you any ads before we validate your custom design. Use the debug mode to test your custom design during development.

If you want to customise the Sashimi, our Ad Unit Review Process is the following:

  1. Contact us to express your intentions to customize the Sashimi.
  2. Send our review team materials that can help us validate your design (PSD mock-ups, screenshots, video, etc.).
    This should be done before submitting your application to the App Store.
  3. Wait for our validation, which will enable ads for your application.

We will strive to validate your design in less than one business day.
If you have not heard from us after one business day, please contact your account manager for any question and approval.
Business-related inquiries should be directed to either Assaf.

Ad Unit Review Guidelines

The Ad Unit Review Guidelines provide rules and examples across a range of topics, including user interface design, functionality, and content.
Ensure your apps comply with these guidelines before submitting them for review.
Developers willing to use the custom mode of the Sashimi will need to use some mandatory information in their design.
We listed below the required and optional elements.

Note: we reserve the right to disable custom ad units that don't meet our guidelines, iTunes Store requirements or otherwise violate our Terms of Service.

Required for implementation

In-stream ad units must contain the following:

  • Application title placeholder. This is a placeholder used for the title of the promoted application.
  • Application icon placeholder. This is an image placeholder used for the promoted application icon.
  • Appsfire Ad Badge (PSD file available here for your mock-ups). This is a visual indicator to let the user be aware that the view is an ad.
  • A CTA (likely to be a button). This is a CTA button, its title must be the one provided by Appsfire.
  • A price placeholder. This is a label placeholder used to inform the user of additional price information regarding the promoted application (localized price, free). The title should only be "Free" if the app is free without In-app purchase.
  • A category placeholder. This is a category placeholder used to display the category of the app.

Optional for implementation

Optionally, in-stream ad units could contain the following:

  • A tagline placeholder*. This is a tagline placeholder for the promoted application, defined by the advertiser.
  • A screenshot placeholder. This is an image placeholder used to display a screenshot of the promoted app.

* Strongly recommended: not implementing this element will reduce fill-rate (as certain ads require more metadata to be displayed).

Visual Requirements

Custom ad units must comply with Appsfire’s guidelines.
Please, refer to the Sashimi template mode to have more details regarding the visual requirements.

Can do


  • You can implement a full-screen Sashimi (e.g. a full-screen composite of a slanted iPad showing animated screenshots of the app)
  • You can include your company logo to elevate brand awareness.

Inspired from Fancy

Would be approved
Inspired from Buzzfeed

Would be approved
Inspired from Spotify

Would be approved
Ad Unit in a horizontal feed.

Icon:
Title:
Appsfire Ad Badge:
CTA:
Price:
Category:
Size:
Highly customized shape.

Icon:
Title:
Appsfire Ad Badge:
CTA:
Price:
Category:
Size:
A full screen ad.

Icon:
Title:
Appsfire Ad Badge:
CTA:
Price:
Category:
Size:


Can not do


  • You can not implement views smaller than 30pt * 30pt
  • You can not implement views partially shown (except as part of a collection stacked up with the rest of the other “cells” and that at some point get expanded to be viewed).
  • You can not implement unreadable text
  • Fonts must have a 10pt minimum size. 14pt to 16pt is optimal for reading.

Please note that the minimum allowed size for a Sashimi view is 30pt * 30pt.
If your view is smaller than that, we will not take your impressions and clicks into account. Please verify your view respect those requirements.


Inspired from Fancy

Would be rejected
Inspired from Newsfeed

Would be rejected
Inspired from Spotify

Would be rejected

Icon:
Title:
Appsfire Ad Badge:
CTA:
Price:
Category:
Size:

Icon:
Title:
Appsfire Ad Badge:
CTA:
Price:
Category:
Size:

Icon:
Title:
Appsfire Ad Badge:
CTA:
Price:
Category:
Size:


Concept

We provide a generic view containing all the information needed to create your own Sashimi ad.
The list of the available properties is available in the header of the AFAdSDKSashimiView class.
You can check the API reference for a more friendly interface.

To give you an idea of the possibilities, our own template formats are subclasses of AFAdSDKSashimiView.

Just like the template formats, the custom views are tappable and will trigger the SKStoreProductViewController.

Implementing your own Sashimi

If you need further customization of how a Sashimi ad looks in your app or game, you can derive a custom class and draw the ad yourself. You can then request an ad view from your custom class as such:

// Show Sashimi With Custom Subclass

if (adSdk.numberOfSashimiAdsAvailableForFormat("SASHIMI_ZONE_ID", AFAdSDKSashimiFormat.AFAdSDKSashimiFormatMinimal) != 0) {
    removeSashimiFooterView ();

    sashimiView = adSdk.sashimiViewForSubclass ("SASHIMI_ZONE_ID", MySashimiView.class, new AFAdSDK.AFAdSizeProvider () {
        @Override
        public AFAdSize provideSize() {
            ...
        }
    }, this);
    ...
}

SASHIMI_ZONE_ID is the zone ID for Sashimi in-stream ads, as provided by Appsfire.

In this example, MySashimiView is your custom class derived from AFAdSDKSashimiView that implements its own drawing. Please note that Appsfire will need to check and approve your ad unit displays before your app using the SDK and the custom view can go live.

The appsfire_adUnitSampleApp example contains a full example of a custom view for drawing Sashimi ads. Please also refer to the API documentation for a full list of methods that you will need to implement and methods you can use to retrieve stock assets and fonts to use in your custom view.