Editorial Guidelines
Editorial Values
Editorial Values Policy
The following polices are intended to provide the framework for exhibiting content and advertising on, and affirming the editorial values of, GSTV’s programming network. GSTV reserves the right to accept or reject content in its discretion, and to amend these policies from time to time:
PETROLEUM INDUSTRY REFERENCES: GSTV will not publish content that refers in any manner to the petroleum industry, including references to fuel pricing, supply, or related operations. Content must not contain language, imagery, or messaging that conveys negativity, criticism, or unfavorable comparisons regarding fuel prices, gas stations, or their owners/operators. Messaging may not capitalize on spikes in, or sustained periods of, high gas prices, nor may it suggest that a product, service, or offer will alleviate consumer sensitivity to fuel costs. All content should preserve a neutral, respectful tone that supports GSTV’s relationships with its retail partners and avoids any implication that could be construed as harmful to the perception of station environments. INTEGRITY & INDEPENDENCE: GSTV operates independently of politically partisan, governmental, and special interests. GSTV will not air content influenced by political pressures or personal interests. SERVING THE PUBLIC INTEREST: GSTV will seek to air stories of topical significance and community interest. GSTV will air content that reflects human diversity, broad experience, and the realities of the natural world. NO HARM & OFFENSE: GSTV reserves the right at any time to decline material that we deem unfit or inappropriate for our audience. Examples of types of programming and/or advertising we may reject on such grounds include, but are not limited to: profane language, live surgeries, death, destruction, violence, rioting, rape, murder, glorification of any criminal or criminal activity, display of images such as weaponry, ammunition, bloodshed that glorify a crime or perpetrator, illegal narcotics/drug paraphernalia, sexual or excretory organs or activities, sexually suggestive material such as massage parlors, adult entertainment, nudity, and condoms. DISCLAIMERS/PERSONAL INFORMATION: A disclaimer is required for all content which users are prompted to participate in a sweepstakes, promo, etc. Content which includes persons and/or locations, all addresses, phone numbers, credit card details etc. must be edited or covered. Phone numbers, email addresses, and website URL’s used within the content, whether intentionally or not, must be cleared by the owner of the details prior to go live as well as adhering to the content guidelines and standards. PRIVACY: GSTV will respect individual privacy throughout our operation.
GSTV QR Codes Best Practices
General Guidelines
Link your QR code to a specific value-add website or offer (e.g., long form content, sweepstakes page to enter, discount/coupon, etc.) vs. generic home page
Include a prompt or instructional message on screen that identifies the benefit the consumer will receive by scanning (e.g., scan code to enter to win, scan code for exclusive content, etc.).
Provide consumers an alternative way of accessing the information on the QR code (e.g., short URL)
Use Dynamic QR codes (vs. static), this will allow you to better track performance and update your content
Understand KPIs and benchmarks for success (e.g., conversion rate, cac, etc.)
Discuss alternate/supplemental measures of success
Scan rate/CAC will not capture the full value of a GSTV campaign. Supplemental measurement may be required to assess brand impact, conversion in other channels (halo affect)
Creative Spec Guidelines
The QR code should be at minimum 250x250 (no smaller than 200x200) pixels on a 1920x1080 creative.
The QR code should be placed in the center or lower corners of the creative.
The QR code should be on screen for the length of the creative (or as long as possible, at minimum 15 seconds).
For a downloadable version of our GSTV QR Codes Best Practices, click here.
Creative Best Practices and Video Spec Guide
GSTV offers a unique 1:1 viewing experience. The viewer is on-the-go and on their consumer journey. As a brand, you have the opportunity to communicate with a consumer, knowing their current mind set, location and potential next steps.
Contrast
Graphics should be high-contrast, bright backgrounds screen best
Avoids Cropping
Title safe ensures that text and graphics are visible
No Motion Blur
Avoid using motion blur for optimal performance
Bold Text
Use bold type in darker colors. For legal copy, minimum point size should be 8.
Why is this important?
Compatibility
Can accommodate 4:3 and 16:9 screens
Video
Focus & Attention
Center safe content allows viewers to easily follow along
GSTV prefers broadcast quality files—files designed or encoded for web are insufficient quality for the GSTV network. Spots airing on GSTV perform their best when they have audio and full motion video.
What do we need?
Resolution
1920x1080
Use maximum render quality
Target 20.00 mbps.
Max file size: 100mb
File Type
MP4 File
Audio
Codec
H.264
Frame Rate
29.97 FPS
5 second minimum video length
30 second maximum video length
If accommodation for a longer length is required, reach out to your GSTV rep.
Avoid using the low end of the audio spectrum (20Hz-250Hz), as videos relying heavily on bass and drums will not present well through our speakers. Low-mid and high-end frequencies are preferred.
48Hz/24-bit Minimum
96kHz/24-bit Preferred
AAC Codec
True stereo mixL Music & Effects (M&E) Mix on L channel, dialogue/VO (D) on R channel
True Peak level should be -2 maximum level
If mastering from a 5.1 mix, do not create a 2.0 track by simply mixing down the 5.1.
File Submission
Please upload your files to gstv.com/uploads
All ready-to-air spots must be received by GSTV 5 business days prior to air date.
GSTV requires a minimum of 15 business days to create a spot once all assets have been supplied by the client. This includes, and is not limited to, images, fonts, video footage, music, voiceover, etc.
Jump to: Editorial Values • QR Code Best Practices • Video Specs