The Hushly code is a lightweight JavaScript snippet that you add to the header section of your landing pages. By implementing the specific tags for Experiences, Hub Embeds, Web Experiences, and the Anti-Flicker Tag, your website becomes Hushly-powered.
These tags serve as Hushly's intelligence layer, enabling it to detect visitor behavior, engage users in real time, and capture high-quality, double-opt-in leads from visitors who might otherwise leave your site without completing a form.
Hushly's enterprise customers have tested and approved the Hushly Code for security and performance on their landing pages.
To find the Hushly Code Tags, go to the Left Nav Menu > Setup > Hushly Code.
Tip: Most Hushly customers place the Hushly Tag sitewide and use the Hushly app to specify which landing pages they choose to be Hushly-powered.
Experience Tag:
Using the Experiences Tag, enhance lead conversion rates on your website by offering engaging experiences that provide previews of valuable assets. These previews keep users engaged, significantly increasing the chances of converting them into leads. To learn more, read Setting the Experience Tag.
Hub Embed Tag:
Use the Hub Embed Tag to showcase content on any web page or landing page. Leverage your content Assets to showcase relevant content for users using streams. To learn more, read Setting Hub Embed Tag.
Web Experience Tag:
When a person visits a Web Page configured with a Web Experience Tag, Hushly recognizes the Segments the Visitor belongs to and shows the relevant content. To learn more, read Setting the Web Experience Tag.

Anti Flicker Tag: An Anti-Flicker Tag is a snippet of code (usually JavaScript) used on websites to prevent visual flickering or flashing when running A/B tests or personalization scripts.
Related Topics:
Setting the Experience Tag
Setting Hub Embed Tag
Setting the Web Experience Tag
Your Content Security Policy for Hushly
Was this article helpful?
That’s Great!
Thank you for your feedback
Sorry! We couldn't be helpful
Thank you for your feedback
Feedback sent
We appreciate your effort and will try to fix the article