Skip to main content
All CollectionsTroubleshooting
Troubleshooting steps for live campaigns
Troubleshooting steps for live campaigns

Common issues when launching a campaign

Mariana avatar
Written by Mariana
Updated over 6 months ago

When launching a campaign there may be some common settings that can be checked if the campaign isn't displaying as expected.

Not seeing the campaign at all

The most important step when launching a campaign is ensuring that ConvertFlow's install code is added to the targeted website, especially when launching popups, sticky bars, and embedded campaigns. Please head to our "Launching a Funnel" section for instructions on how to install ConvertFlow →

When our script is installed correctly, the ConvertFlow admin widget will be visible on the website:

NOTE: Keep in mind that launching popups, sticky bars, and embedded campaigns is only possible for customers on paid plans →

Popups and Sticky bar campaigns

When testing a popup campaign on the live site, there are some reasons why it may not trigger when expected. Here are some areas to check when troubleshooting a popup campaign:

  • The trigger type - Checking the trigger type selected is configured correctly so the campaign displays when expected. For example, the "Upon click only" trigger type will only work when the trigger class is added to the button intended to show the popup →

  • Trigger suppression rule - A trigger suppression is enabled when a visitor uses the campaign's close button to close out the popup, only then will the trigger suppression activate for the set number of seconds or days:

    When testing campaigns it's possible to use the admin widget's reset tracking feature to bypass the suppression rule:

  • Site-wide conditions - These conditions are assigned at a website level and will apply to all campaigns. This means that if a site-wide condition is set to exclude a specific page on the website, no campaigns will show on that page. Learn more about site-wide conditions here →

  • Campaign conditions - Campaign conditions apply to standalone campaigns and may prevent them from popping up when they're not met. Learn more about targeting conditions here →

    In both these cases, please refer to the admin widget to troubleshoot whether a campaign may not be triggering due to conditions not being matched. This article will explain how to use the admin widget to troubleshoot a live campaign →

  • Website cookies - Some website cookie policies will suppress the ConvertFlow script if the policy isn't accepted. In these cases, it's best to make sure ConvertFlow is exempt from the website's cookie policy as campaigns will not trigger if the visitor rejects the opt-in. Alternatively, make sure to accept the site's cookie policy to ensure ConvertFlow's script fires.

Embedded campaigns

Since embedded campaigns have two ways of being added to a website (a full embed form and area snippets) the first step is to verify which method was used.

Landing page campaigns

There are a couple of reasons why a landing page may not show and hosting the page on our default secure domain convertflowpages.com is the best way to verify the proper functioning of a landing page.

NOTE: Landing page URLs will always need to have a path after the / so they must look like this - team.convertflowpages.com/blog

Not seeing correct content on the live campaign

If the campaign is live and is showing correctly on the preview page but not on the live site, make sure to click the “Publish” button. This will ensure that the live campaign is up-to-date with the version in the builder:

This option is there for when a campaign is live and edits need to be made without disabling the campaign. The edits can be made, saved, see/test them in the preview page, and finally published once they're ready, without affecting the live campaign's functionality. 

If the changes are still not showing, please use the "Refresh Tracking" option from the admin widget. This will ensure the most recent version of the campaign is shown instead of the cookied version.

Did this answer your question?