Why is my content not appearing on specific retailer sites?
- Inline Content may not appear by default for Retail partners that are listed under the Premium Partners section of the Inline Content Builder. This means that a certain approval process or sales transaction may need to occur for that Retailer.
- The Retailer may also not be properly integrated or calling the Rich Content service for the particular category, SKU or locale.
- Also make sure the SKU or page is not being restricted in the Partner Publishing Rules section
Contact Support and provide the following information so that we can assist you:
- The Retailer's Product Page URL link
- The Manufacturer Part Number and GTIN (or UPCEAN)
- The page or content URL within the Inline Content Builder.
Does Rich Content support video subtitles or captions?
- Yes. Our player supports display of captions when WebVTT or VTT subtitle files are provided along with each video without your automated feed.
What is Inline Content?
- Inline Content is rich content displayed right on a product detail page. lnline Content utilizes a flexible template to accommodate many visual and highly engaging and interactive content such as text, imagery, videos, 360 spins, hotspots, Augmented Reality, and pdf’s to create a product page that best represents product, the brand, while providing the key information shoppers are looking for.
What is your Quality Control process for new content?
- Data Integration and Workflow:
Our integration process automatically checks incoming and outgoing files for data integrity, valid html, and custom validations defined by the specific syndication project. Updates/changes at sku level can be rendered as a report for review. CNET can check for inappropriate content or text matches however the manufacturer is responsible for the accuracy of the content.
- Management of exceptions:
In the event that a large amount of content has changed and requires manual review, using our automated delta check process (review of source files from delta checks on category and item-level content), a representative sample of content is chosen for human review. Sampling rates are based upon achieving a reasonable accuracy level that ensures content is properly converted without a high impact to the time required to move the lot to production. Content selected for sampling is based upon the historical layers of the creation process (before & after), takes into account any changes in backend code releases, and is reviewed by multiple team members to maximize consistency and minimize any errors related to review by a single individual. Should the content update exceed the acceptable error threshold, the content is then isolated for review by the QA lead, and any issues are communicated back to the appropriate internal or external sources for necessary rework and reprocessing.
