Is the recommendation to not put the deployment code in the global header or footer intended to limit the intercept views just based on licensing limitations? Are there other reasons that this should be avoided? If there is an Always On intercept on every page, does it matter if the code is in the header/footer or on the pages themselves?

Thanks for your questions!

• Is the recommendation to not put the deployment code in the global header or footer intended to limit the intercept views just based on licensing limitations?


• Yes, this recommendation is just based on licensing limitations, as we charge by views to the intercept.


• Are there other reasons that this should be avoided?


• No.


• If there is an Always On intercept on every page, does it matter if the code is in the header/footer or on the pages themselves?


• If you want to display the same thing on every page it is fine to add the deployment code to the global header/footer. If you’re looking to hide the intercept on some pages, the global header/footer should not be added because it eats up views for intercepts not actually displayed.

Excellent, thank you so much for the clarification!

@jwiggington I wanted to follow up on your questions:
The website / app feedback update from last week was added in error and we have corrected the support page to reflect this. We still recommend adding the code snippet to the global header/footer within your website. The benefits of this include only needing to do a one-time code placement, allowing website visitors to provide feedback on any page of the website, and collecting aggregate operational data such as Time Spent on Site and Page Count. If you prefer to only add a digital touchpoint to a handful of pages instead of the full site, you’re welcome to add the code snippet directly to those pages instead, but you may miss out on some of the benefits mentioned above.