Technical FAQs

Before you invest in a new piece of technology, you want to make sure it’ll work with your current systems and platforms. We’ve compiled answers to the most common questions clients ask us about integrations, display, optimization, customization, and publishing. For in-depth technical support questions, just send us a message using the chat feature in the Studio.



Q: How does Ceros work with our CMS? A: The content you build on Ceros can be embedded into your CMS by taking the embed code for your Ceros experience and inserting it into the HTML of a post or page. If your site is built responsively, your embedded Ceros experience will also dynamically respond to page size, but you can also embed in a static web page as well.

Q: Can Ceros integrate with our eCommerce platform? A: Yes! There are two ways you can integrate eCommerce components from Magento, Demandware, or your eCommerce platform of choice in Ceros Experiences:

  1. You can lightbox in existing product panels from your eCommerce site.
  2. You can use our SDK to listen for click and touch events on products in your Experience. These events can then trigger your existing product quick-views or other functionality on your site within an Experience.

For details on the Ceros SDK, check out our Developer Portal.

Q: How does Ceros integrate with email service providers? A: Email clients are notoriously inconsistent in the way they render your email content for readers. Some clients block images and other non-text content by default; others apply different fonts and spacing to your content. All this goes to say that Ceros Experiences can’t be delivered via email, but you can create emails that link out to Ceros Experiences. If you want to give viewers a sneak peek of your interactive content, you can always use a GIF creator to show a portion of your Ceros Experience and drop that into your email service provider.

Q: How does Ceros integrate with analytics programs like Google Analytics and Omniture? A: For Google Analytics, there’s a dedicated field where you can drop in your UA ID. For other analytics products like Omniture, Google Tag Manager, or Mixpanel, you can drop in a tracking snippet in the Custom HTML section of your Experience. You can add link-based tracking parameters to your Ceros content URL as well. On our end, we track in-experience visitors, opens, views, clicks, shares, and other engagement metrics, which you can view in your Project’s Analytics Dashboard.

Q: How does Ceros integrate with marketing automation platforms (MAPs)? A: You can drop your marketing automation platform’s tracking code into the Custom HTML field under Settings, which will pass through any Ceros Experiences viewed to your MAP contact records. You can also lightbox in lead capture forms from your marketing automation platform, either to gate the Experience itself or to capture information as part of a call-to-action within the piece.

Q: Can we leverage UGC (user-generated content) in our Ceros Experiences? A: Using the Lightbox feature in the Studio, you can pull in UGC such as social media feeds, reviews, and other external content. You can also use our beta Custom HTML feature to display feeds natively on the canvas—ask your account manager for more information.

Q: Can we integrate lead capture forms into Ceros content? A: You can pull in an existing lead capture form created with your marketing automation or CRM platform using our Integrations with HubSpot and Marketo, as well as using the Embed Object Tool

Q: How does Ceros integrate with Facebook? A: You can create a custom title, description, and thumbnail image to populate when your experience is shared on social media. Check out this article to learn more.

Q: What can we do with the Ceros Software Developer Toolkit (SDK)? A: Our SDK gives you the ability to:

  • Dynamically insert a Ceros Experience on your site.
  • Query an Experience for its pages and layers based on their ID or the metadata applied to them in the Studio.
  • Navigate between pages within an Experience.
  • Disable and enable pages within an Experience.
  • Get the state and properties or other metadata for a page within an Experience.
  • Start and pause animations on a page within an Experience.
  • Find all components within a given Layer.
  • Show or hide Layers.
  • Get the metadata applied to a specific Layer or Component.
  • Start and stop videos.
  • Show or hide specific components.
  • Simulate click events on specific components.
  • Subscribe to events fired within an Experience.


Q: Is Ceros content responsive? A: Ceros Experiences responsively scale up and down, but keep in mind that if your content is designed for larger screen sizes, it won’t scale down well for mobile. Many of our clients design a mobile variant that’s served at smaller screen sizes for an optimal viewing experience across devices. 

Q: What kind of code does Ceros output?   A: Ceros Experiences are output as HTML5 and JavaScript code.

Q: Can we embed Ceros Experiences in our website, blog, or third-party site? A: You can! Upon publishing an Experience, you’ll receive two embed codes you can drop into any HTML editor: one for embedding full height, and one for embedding at a restricted height with internal scroll bars. This article covers more details about how to embed experience.

Q: Can you view Ceros in a Native Mobile or Tablet app? A: You can embed a Ceros Experience in a native app using a WebView. This is works in much the same way as embedding an Experience into a website. For an example of how this works, check out Tennis Tuesday’s iOS app.

Optimization & Personalization

Q: Do you support A/B testing? A: Since Ceros content lives on the web, it plays nicely with third-party A/B testing platforms. You can drop your integration pixel into the Custom HTML field under Settings and then set up your test as usual.

Q: Can Ceros serve different content or languages based on geographic region? A: You’ve got two options for serving different Ceros content based on IP address:

  1. You can create a single-page Experience that asks the user to select their region or language and link to the appropriate content based on their selection.
  2. You can embed your Experiences in pages you host on an appropriate subdomain and use your domain’s HTTP or JS redirect logic to take viewers to the content you want to serve based on their IP location.

Q: Do you provide user permissions that restrict publishing privileges to admins only? A: Admins can add other users to individual projects to restrict access in the Studio. However, all users on a given project have the ability to edit and publish content. If you just want to be able to share an in-progress Experience with your team, you can distribute a preview link without adding team members as users.

Q: Can I restrict who views a specific Ceros Experience? A: You can use our time-triggered lightbox feature to require a login and password to view an Experience.

Q: Can you personalize content with Ceros based on user preferences, behaviors, or other stored CRM data? A: We’re currently building out integrations with Eloqua and other marketing automation platforms to allow for personalization within Experiences and personalized serving of Ceros content on your domain. 

Q: How does Ceros work with search engines? A: Ceros is fantastic for SEO because it drives longer dwell times and lower exit rates. The more engaging your website is, the more Google and other search engines will like it—and interactive content is the best way to drive more engagement. You have full control over the page title and meta description for your standalone Ceros Experiences, as well as Alt text for images. By default, we generate a NoScript HTML version of your content that can be parsed by search engines, but if you prefer, you can create a custom marked-up version of your text to override the default NoScript HTML. In the event that you’re embedding an Experience into a page on your domain, you can check the “Disable SEO for this Experience” box in Settings to prevent the standalone version of your Experience from being crawled. You will then need to include the title, meta description, and NoScript HTML in the code for the page where you’re embedding the Experience.

Publishing & Hosting

Q: Can we schedule content to be published at a later date? A: Not right now, but this is a feature we’re considering for future development.

Q: How can I make my Ceros content easily shareable? A: You can add a social sharing menu to any Experience using our built-in sharing menu. You can also integrate custom click-to-tweet links and other social sharing options using a typical share link generator.

Q: Can I host Ceros content on my own vanity domain?  A: Yes, for an additional fee, you can set up your own vanity domain and have Ceros content published on it. You can learn more about setting up vanity domains in this article.

Q: Can I host the code for my Ceros Experiences on my company’s servers? A: We offer the ability to export published Experience code from the Admin and host on your own servers for an additional cost.

Q: Can I unpublish an Experience if I don’t want it to be live any more? A: You can effectively unpublish content in one of two ways. You can delete the entire Experience in the Admin, which will also remove any Analytics from your Dashboard; you can also check the “Disable SEO for this Experience” box in Settings to prevent search engines from crawling your Experience, and add a lightbox with a message that blocks your Experience from being viewed.


Q: Where and how does Ceros host content? A: Here’s a rundown of how our published content and products are hosted.

  • All published Experience content, media, and other assets are served from S3 with Fastly in front as a CDN.
  • Admin and Studio content is served from Ceros-managed AWS EC2 instances.

Q: Do you have any documentation around performance data, load times, etc.? A: Loading times depend upon many factors. Image/video sizes, end-user connection, experience size, etc. all contribute to higher load times. We have several Ceros Academy articles explaining how to decrease load times:

Q: Is encryption used when transmitting restricted, private, or proprietary data to/from the service provider? A: Secure TLS connections are used for all logged in sessions. We support secure connections for published experience content but do not force it.

Q: Do you conduct internal and external audits as prescribed by industry best practices? A: No, we do not conduct any at this time.

Q: Do you follow industry best practices to support safe and secure facilities? A: Yes, we follow best practices for both personnel and information.

Q: Do you support secure deletion of electronic data? A: When deleting content from within Ceros, the data is not completely purged from our database in cases where users would like to recover content they didn’t mean to delete.

Q: How do users accounts and roles work? A: Users can have one of two roles. Either Account Owner or just Members. Account Owners have access to all projects and can make account level changes. Members only have access to the projects in which they are invited to and can not make any account level changes.

Q: Can we restrict individual user access to specific projects? A: Yes. A user can be given access to only certain projects and not the entire account. Also, that user can not make account level changes.

Q: Do you support identity federation standards to authenticate users? A: Yes, we support Single Sign-On.  Ceros supports both password authentication and enterprise SSO using identity standards: LDAP, SAML, and OAuth.

Q: How does your patching test and deployment work? A: Patches (e.g. hotfixes) go through a very similar process as the rest of our product releases. The fixes are reviewed by another developer and functionally tested by QA. Depending upon the fix, we will then test the fix on our Stage environment. If that all passes, then we deploy to production.

Q: Do you restrict, log, and monitor access to your Information Security Management Systems? A: All access is restricted to developers through our Cloud Management provider. Any access to the servers themselves is logged in the server audit trail.

Q: How does your encryption setup work? A: Passwords are stored in an encrypted one-way hash so that they are unable to be reverse engineered. Experience data is not encrypted before storage in AWS S3.