"I can't see my published campaign"
It’s pretty common to wonder why a campaign isn’t showing up on your site, especially during setup or testing, but sometimes also when the campaign is live. Most of the time, the reason is a small setting that’s easy to miss, like a scheduling rule, a device filter, or a targeting condition that doesn’t match your current session.
This guide will help you quickly go through the most common things to check so you can get your campaign live without needing to contact support. If you prefer talking to a real person, feel free to reach out to our support!
Step One. Check Targeting
Make sure that your campaign is actually published (state "Live") and that you are checking the correct website connected to that account.
Go through your targeting:
Does the campaign have scheduling that doesn't match todays date
Is the campaign targeted at specific URLs? Look for typos, missing slashes, or full vs partial match issues.
Does the campaign have session conditions that don't match your current visit, such as device targeting, UTM targeting, or JavaScript
Check repetition settings. If you've already signed up for the campaign, you would normally not see the campaign again.
Check your Triggers. Are you performing the correct trigger to activate the campaign, eg. doing enough page views or scrolling down?
Are you in the correct Audience? Most campaigns in Triggerbee are audience-targeted, meaning you might not just be a match for your campaign. Check out step three to investigate this part further.
Step Two. Patience
If you have recently published your campaign, the reason for you not seeing it might be due to cache. This is especially common when being on the website while publishing campaigns. Try checking your website in incognito mode.
You can check your Visitor Feed or the Campaign Statistics to see if the campaign is getting views from visitors other than yourself. That's usually a good sign!
Step Three. Deep Dive Troubleshooting
If you have checked all of the above and still are not seeing your campaign, we recommend the following steps:
Visit your site as a specific person
By adding an email to the URL, it is possible to visit your website as a specific Triggerbee Profile. This is useful for troubleshooting audience targeted campaigns.
If you know that [email protected] is in the audience of your campaign, you can add that email address (identifier) to the URL like this. This will trick Triggerbee into thinking that you are that person, and thus, display campaigns accordingly.
www.yourwebsite.com?utm_custom[email][email protected]
Note: Be careful when using the utm_custom[email] debugging. All events you perform will be logged to that email address. Always use Incognito mode when doing this.
Debug Mode
To activate debug mode, add ?tb-debug=1 to your URL. In debug mode, we will log messages related to campaigns in the console.
For instance, if your current URL does not match the campaign targeting, you will see that in the console in debug mode.
Still not seeing your campaign? Please reach out to [email protected] to get an extra pair of eyes to test your campaign.
"I can't see my campaign in preview mode"
When previewing a campaign, it should open up directly, regardless of the triggers and timing options you have configured the campaign with. Still, there are a number of reasons why your campaign doesn't show up when previewing.
Removal of query string
To force open a campaign while previewing, Triggerbee uses query strings. Sometimes those are removed by your website, so check the URL of the tab that is opened when you have clicked to preview a campaign. It should contain a query string that looks similar to this:
https://www.mysite.com/?dev=true&tb-widget-preview=1234567&tb-nocache=true
If the query string isn't there, it could be that your website redirects the visitor to another domain, and while doing so, removes the query that forces the Triggerbee Campaign open. You can fix this by going to your Account Settings and configuring the "Campaign Preview URL" with the URL that your website is trying to redirect you to.