On-Site interactions are messages that are shown on the screen while the user is active on the website. This may include pop-ups that we commonly see for email signups, content recommendations, live sales, etc. This triggers the user to perform some action. Engaging the visitors on your site with targeted messages that are personalized is one of the most effective ways to build trust.

Purpose of On-Site Interactions

The purpose is to engage the visitors/end-users to perform a specific action like:

• Show the latest articles
• Capturing email addresses
• Conducting survey
• Trigger inactive users
• Spin and Win(Gamification)
• Countdown(create urgency for an event)
  and more

Advantages of using On-Site Interactions

On-Site interactions have multiple advantages:

• No limitation of different OS(iOS, macOS, Windows, etc)
• Direct interaction with end-users (No need to worry about the open rate)
• Keep the user engaged on your website
• Increase average visit duration

Prerequisites

To get started, we would need a LIVE RSS feed (feed format - mandatory) of your website to be configured at our end to configure On Site Interactions. Please note that currently, we can configure only one RSS feed for any website.

Additionally, ensure that the below IPs are whitelisted so that our servers are able to successfully crawl your website for information:

• 34.87.172.143
• 34.124.138.192
• 35.185.183.159

RSS Feed Format

We follow a specific format for the RSS feed to configure On-Site Interactions for your website. If the feed does not follow this format, the On-Site widget will NOT show up on the website.

Feed Requirements (very very important)

1. XML Version - 1.0 or higher
2. RSS Version - 2.0 or higher
3. Article Title (<title></title>) - String (required)
4. Article Link (<link></link>) - String URL (required)
5. Article Image (<media:content><media:thumbnail><url></media:content>) - String URL (required)
6. Article Description (<description></description>) - String (optional)
7. Article Published Date (<pubDate></pubDate>) - String (optional)

If #1 and #2 are not followed, we will not be able to parse the feed at all.

If #3, #4, and #5 are not followed (but #1 and #2 are followed), we will be able to parse the feed; however, the widget will not show up on the website.

For more information on the feed formats that we use, see the below guides:

1. Supported Namespace Modules by RSS 2.0 - https://en.wikipedia.org/wiki/RSS#Modules
2. Media Consumption in RSS 2.0 - https://en.wikipedia.org/wiki/Media_RSS
3. Media RSS Specifications - https://www.rssboard.org/media-rss