<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>desktop on asdfasdfasdfasdfddd</title><link>https://academy.test.quriobot.com/tags/desktop/</link><description>Recent content in desktop on asdfasdfasdfasdfddd</description><generator>Hugo -- gohugo.io</generator><language>en-us</language><atom:link href="https://academy.test.quriobot.com/tags/desktop/index.xml" rel="self" type="application/rss+xml"/><item><title>Different bots on Desktop and Mobile, different pages, etc</title><link>https://academy.test.quriobot.com/publishing-your-bot-embedding-and-dedicated-pages/different-bots-on-desktop-and-mobile-different-pages-etc/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://academy.test.quriobot.com/publishing-your-bot-embedding-and-dedicated-pages/different-bots-on-desktop-and-mobile-different-pages-etc/</guid><description>If you want to show different Quriobots on Mobile and Desktop (or maybe no bot on mobile, for example) this page will explain how to do it using trigger conditions.
In short what you need to do is to set mutually exclusive conditions for the different bots (in this example, mobile vs desktop):
Step 1: set a trigger condition for the first bot to only trigger on the mobile device</description></item><item><title>Special tricks for publishing QB via Google Tag Manager</title><link>https://academy.test.quriobot.com/how-to-build-an-advanced-bot/special-tricks-for-publishing-qb-via-google-tag-manager/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://academy.test.quriobot.com/how-to-build-an-advanced-bot/special-tricks-for-publishing-qb-via-google-tag-manager/</guid><description>Maybe you already are publishing our Quriobot via Google Tag Manager but here we share some real next-level implementation methods for Google Tag Manager!
Note, that most of those tricks are not necessary as we support trigger conditions so you can have great flexibility when and where to show your bot.
Note: most of these examples are not for the faint-hearted, they require development skills (and most likely lots of trial and error.</description></item></channel></rss>