RICH MEDIA BUILDS
- Format: .PSDor .AI file with open layers or HTML files
- All source files/assets should be supplied separately
- Fonts used in the creative
- High Resolution Logo
- Brand Guidelines
- Final HTML will be created by Near
RICH MEDIA SLAs
- Once we have received all assets, we require approximately10 business days for rich media builds
- Creative build times may vary depending on the complexity of the build. If it is clear from the outset that the build is complex, we will flag that we require extra build time.
- If the scope changes (eg. functionality of the rich media unit) during the build process, we may require extra build time.
- In order to maintain efficient build times, it is important that Near, the Agency and the Client are on the same page when it comes to the user flow and functionality of the build. Please discuss wireframes with your Near representative.
- If sending of assets or feedback by the client is delayed this may lead to increased build time.
- The following are standard turn around times:
First round mocks:2 business days after assets received
Revisions to mocks: 1 business dayafter receiving feedback.Please note, the number of rounds of revisions required will impact build time.
HTML Production: once the flat mocks have been approved, it takes 4-5 business days for HTML production and for demo link to be sent to client for approval
Revisions to HTML: 1 business dayafter receiving feedback. Please note, the number of rounds of revisions required will impact build time.
Schedule Campaign to go live:Once the demo link has been approved, it takes 1 business day for trafficking and processing creative before the campaign can go live
MOBILE AD SPECIFICATION
Base Banners (.jpg / .gif / .html format):
- 728x90 px- 35 kb max
- 320x50 px- 15kb max
- 320x480px- 50 kb max- Interstitial
- 480x320 px- 50 kb max-Interstitial
*Note: Please share open layered .PSD files along the banner.
Expandable Banner (Dynamic & Static):
- 320x50 expands to 320x480 pixels
- 728x90 expands to 768x1024 pixels
- Format: .PSD or .AI filefile with open layers or HTML files
- All source files/assets should be supplied separately
- Final HTML will be created by Near
- Fonts used in the creative
- Note: Final HTML5 file will need to be within 7kb
Landing page:
- Format: .PSD or .AI filefilewith open layers
- Dimension: 640 x 960 pixels
- All source files/assets should be supplied separately
- Fonts used in the creative
Video Interstitial
3rd Party Hosted
DFA VAST xml tags
Near Hosted
1. Video files in .mp4 format. We can try to convert the file from .mov to .mp4, but sometimes doing so will change the quality of the video.
2. Video file size has to be under 5 MB.
3. Video length has to be either 15 or 30 seconds
4. Minimum resolution required is 320x480px
Rich Media Supplied by Client
Expandable on mobile 320x50—>320x480 (Must be in HTML5 format and MRAID compliant)
Expandable on tablet 728x90—>480x320(Must be in HTML5 format and MRAID compliant)
Interstitial banner 320x480(Must be in HTML5 format and MRAID compliant unless it's a .JPEG / .GIF / .PNG)
Landing page640x960 (HTML5) - 100% width responsive (heightshouldbe left proportionate),
Both Expandable and landing page should be built only with Javascript framework.
Creative much come as one single HTML file with images and fonts as the only source file. It should not call any assets dynamically or in real time.
HTML5 file must be within 7kb, and all image files together must be within 200kb
Rich Media Supplied by Client – Dynamic Message
Rich Media supplied by the client that uses a dynamic message linked with Near’s location targeting, as well as the requirements listed above under “Rich Media Supplied by Client,” has the following additional specifications:
Leave space for dynamic message
If the dynamic text needs to be on all frames of the creative,make sure to leave space in the same position ofall frames for animated banner for Near to print dynamic distance/suburb
Font file must be supplied for dynamic text