Stories can be delivered via your CDN. For context, a content delivery network, or content distribution network, is a geographically distributed network of proxy servers and their data centers. This allows for optimal delivery so you can serve your users using the fastest local infrastructure.
Training Sessions can be arranged with any members of your teams. The recording of initial kick-off sessions is recommended. Please reach out to your account manager for additional information.
MOAT Brand Safety and Viewability data is available with all Brand Story campaigns, typically, at no additional cost. Please reach out to your account manager for additional information.
Typically, there is no CMS integration required. Stories are published alongside existing content using custom subdomains or reverse-proxy configurations. Some integrations may be possible so that for example, users are logging in with existing credentials. Please get in touch for additional details.
Stories can be published directly to your domain on a custom subdomain (i.e. stories.domain.com/story-slug) or in a subfolder on the root domain (i.e www.domain.com/stories/story-slug).
Currently, only one domain can be set up per account. A new domain has to be set up on a different Studio account.
Yes, custom fonts can be added via the admin panel. Preferred formats are .woff or .woff2 but .ttf and .otf are also supported. Fonts will then be available for your entire team.
Most third party analytics providers can be included with your story. Tracking can be added on the story level or, for more granular segmentation, on scene level via the 360 Writing mode. Please note that Moat trackers are automatically fired with all Brand Stories and data is available via your Account Management team.
Depending on your plan, you can invite 5, 10 or more team members in the Studio. You can assign different roles, such as Admin, Editor or Member.
Any team member invited to your account can create Brand Stories. Typically, graphic designers are the best suited to create the content. Members of the ad-operations team can monitor campaign performance, while commercial teams can monitor assets creation and submit for client approval.
Any team member invited to your account can create Brand Stories. Typically, graphic designers are the best suited to create the content.
There are no distinct specifications for building Brand Stories. You are free to use any available assets: images, videos, shapes, fonts.
Instagram Stories content can be re-created with Newsroom Studio, provided all assets are available. These can be downloaded as a .zip file from Instagram and then uploaded to the ‘my Library’ section.
(To preview your stories) Go to the My Stories page, select the story you wish to preview and then click the Preview button on the top right side.
The Preview URL should be used only for testing purposes as it is not served by a CDN. It is not cached so updates show immediately. The Production URL serves via a global CDN, optimised for high traffic and low latency, wherever your users are so updates may take a few minutes to become visible.
The Web Stories format is generally more appropriate for editorial content with regard to search engines and discovery while Branded Stories (NWS) is better fit for branded stories allowing for more engagement via social cards, shoppable scenes and such.
Depending on the ad server, the platform generates a 3rd party delivery tag for each Branded Story. If your ad server is not already on the approved and tested partners list, the Newsroom team can assist with the accreditation process and all the technical details (the type of tag - JS or Iframe, click macros, etc)
First you need to create a Kit that will act like a folder for your future templates. Then you can create scene templates, one at a time in this kit. To do so, go back to your story Click the 3 dots menu on top of the scene you want to save as template. You need to create separate templates for each scene type (cover, standard, quiz, poll) - and they will show up once you switch the category at the top.
Click the share icon on the cover. You can share directly on Linkedin, Twitter or Email, for the other social networks you can simply copy the link.
Yes, please ask your account manager about the approved vendors or creators available for hire. Turn around time is typically 24 to 72 hours.
All published stories are automatically submitted to the sitemap. To access the sitemap go to Dashboard > Domain & Hosting. All stories published on the stories.nws.ai domain become part of the NWS.AI global sitemap and automatically get submitted to Google Search Console.
Brand Stories can run in desktop environments too with additional parameters attached to the tag.
Brand Stories can deliver via standard creative tags via most ad-servers or DSPs, certified under platforms such as Google’s DV360 and Xandr. The unit can target any display unit and no specific inventory allocations need to be performed. The 300x250 for example is an ideal size as long as it allows Friendly or Safe Frame technology.
The story ad-unit can render in both Friendly iFrame and Safeframes environments. They auto-expand to the full viewport width X height when Friendly Frames are available and full viewport width x 700 pixels if Safeframes are present.
Campaign landing pages are typically text-heavy experiences that consumers tend to abandon in under 45 seconds. Brand Stories are stand-alone web destinations, allowing for their URLs to be used as destination pages with any display, video or social campaign.
Brand Stories can be shared on Social Media using their production URL. Please make sure you set up all Poster images so they preview correctly when shared.
Although a mobile-first experience, Brand Stories render well on desktop as well.
Video tracking is not available on the platform. Conceptually, the Story format is different from the video-ad formats as it encourages active consumption, breaking down content into individual scenes that make it much easier to track progress and depth.
All data presented in the UI is available programmatically via APIs. Please reach out to the account management team for additional information.
Impression trackers can be added on the Story level via Tags and Analytics, or on Scene level via the Writing mode in the Story editor.
The story and all assets are highly optimized for mobile and served by a global CDN. However, the load time also depends on number of scenes, layers and images/video used in the story as well as on network speeds.
Brand Stories measure all impressions lost due to Heavy Ads content removals. We recommend to keep the content in the cover scene (typically video) under 4mb to avoid Heavy Ads removals.
GDPR consent is typically collected by the publisher running Brand Stories on site level. That generally implies consent is given for all content and third parties allowed to run. Some eser added trackers/embeds/attachments may require GDPR consent. This can be gathered by including your own CMP in the story code.
Click trackers can be added as custom ad-server URLs with any CTA elements in the story.
Please see Media Solutions pages for Benchmarks on each individual product.
The platform uses industry-standard macros to pass information between its internal ad-serving components and any external ad-server or DSP. All communications is carried via creative tags, available for export with every Brand Story created on the platform.
The number of times a story has been loaded, whether in or out of view.
Total sum of all scene views, including views resulting from auto-advance.
The number of users that interacted with the story (only the first interaction is counted for each story load). This could mean they went to the next scene, opened the share menu, or unmuted a video. It is generally fairly similar to the second scene impressions, since going to the next scene is the most common first interaction.
The Interaction rate is calculated as number of interactions / number of story views and shown as a percentage.
The number of times there was a heavy ad intervention (the story ad was removed by the browser for using too many resources).
The average time spent on a story, which is recorded independently from scene time and capped at 100 seconds if the browser is left open.
The average time spent on individual scenes. Every time a user changes a scene, we send a time e.g. 5 seconds, and it's the average of those. Auto-advance implies a maximum for this value. The timer is capped at 20 seconds, to prevent skewing the average when the page is left open, and there is no auto-advance.
The same as AVG Depth except excludes first scene impressions (excludes users who didn't interact with the story). This is calculated as: (next scenes / story impressions) / number of scenes * 100.
How far (number of scenes) is reached into a story on average. This is calculated as: (scene impressions / story impressions) / number of scenes* 100. In the case of auto advance, it may not be due to user interaction.
The total number of Attachments that were opened in a story. Attachments are tracked separately to CTA actions, despite the buttons often looking similar.
The number of CTA taps that open a URL, call a phone number or open an email client.
We collect two types of data: 1: Anonymised usage statistics (non personally identifiable) that count events such as content impressions and other user interactions. 2: Information that the users willingly share as part of their content experience - such as name, email, phone number, address or answers to fixed or open ended questions.
Content creators can include links to privacy and data usage policies.
We offer a templated Policy here - link - that covers all the basics. However, we recommend you consult your legal and compliance teams.
Newsroom AI will act as a data processor, facilitating the collection and safe storage of both personally identifiable data and anonymised data. The data belongs to the Data Controllers. Controllers are in most cases the final clients, if campaigns are facilitated over multiple intermediaries (data processors) - such as solution providers, media or advertising agencies.
Processors must ensure that the personal data that they process are kept confidential. Processors are required to keep personal data confidential except on instructions from the controller, unless the processor was required by law to process that data.
The data controller is the person (or business) who determines the purposes for which, and the way in which, personal data is processed. By contrast, a data processor is anyone who processes personal data on behalf of the data controller (excluding the data controller’s own employees). This could include anything as seemingly trivial as, for example, storage of the data on a third party’s servers, or appointing a data analytics provider.
The data controller will be authorizing data processors to store and operate data collected on its behalf. The controller will ultimately be responsible for the security and integrity of data collected via third parties and will be the identifiable point of contact in relationship with the consumer.
The data controller must allow consumers to permanently remove their data. This operation is available via a link to Newsroom AI’s platforms.
Newsroom AI is legally obligated to comply with the EU's GDPR framework, even while engaging with non-EU solution providers, agencies or consumers.
Experiences delivered programmatically into placements managed by publishers will be subject to publisher’s GDPR and cookie practices, as such policies apply to all direct or programmatica relationships the publisher will engage in. So the experience will not have to carry any cookie / privacy pop-ups.
Promotions can be subject to additional Terms and Conditions that can be linked into the experience.