Block IP Addresses
Prevent visitors with a specific IP address or in a certain range from seeing your campaigns.
Block IP Addresses is an OptiMonk feature that lets you prevent visitors with a specific IP address — or a range of IP addresses — from seeing your campaigns. The most common use case is excluding your own team: when you or your developers, designers, or QA reviewers visit your store, you typically do not want OptiMonk campaigns to fire for you, as it clutters the browsing experience during internal reviews and can distort your campaign analytics with non-customer impressions. By adding your office IP address or your team's IP range to the block list, OptiMonk silently suppresses your campaign for those visitors without affecting anyone else. The feature also covers broader scenarios such as blocking competitor IPs, filtering out known bot traffic from specific IP ranges, or preventing campaigns from displaying to third-party auditors reviewing your site. IP blocking is configured as a targeting rule at the campaign level, giving you precise control over which campaigns are suppressed for which IP addresses.
Key benefits
- Keep internal traffic out of your campaign analytics. Every time a team member visits your store and triggers an OptiMonk campaign, that impression is counted in your campaign data. Over time, especially for stores with active development teams, this internal traffic can meaningfully inflate impression counts and suppress conversion rate figures. Adding your team's IP addresses as an exclusion condition removes them from the data entirely, giving you a cleaner picture of how real customers are engaging with your campaigns.
- Browse and QA your own store without campaigns interrupting the experience. Reviewing product pages, testing checkout flows, and inspecting site changes is harder when your own campaigns keep firing. IP blocking lets your team browse your store as if those campaigns were not active — seeing the clean page without popups — while keeping all campaigns live for actual visitors. This removes the need to use incognito windows, clear cookies, or pause campaigns during internal work sessions.
- Campaign-level control for precise suppression. Because IP blocking is set as a targeting condition on individual campaigns, you can choose exactly which campaigns suppress for which IP addresses. You might block your team's IPs on your main lead-capture popup while leaving a product page campaign visible for internal review purposes — giving you granular control rather than a binary on/off switch for all campaigns at once.
How it works
In your OptiMonk dashboard, select the campaign and click Edit settings. Under "Select who should see the popup," click Add new rule and find the IP address condition in the targeting rule list.
You can add individual IP addresses (for example, a single office connection) or specify an IP range to cover an entire subnet — useful when your office network shares a common IP pool. Set the condition to exclude visitors matching those IPs, and add multiple entries as needed.
Once the condition is saved, OptiMonk checks each visitor's IP address at the moment that campaign is about to display. If the visitor's IP matches any entry in the exclusion rule, the campaign is suppressed silently for that visitor. They see your site normally and are simply not shown that specific campaign.
Frequently asked questions
What is IP Address Blocking in OptiMonk?+
IP Address Blocking is an OptiMonk targeting condition that prevents visitors connecting from a specific IP address or IP range from seeing a campaign. It is configured per campaign as an exclusion rule and is most commonly used to filter out internal team traffic — so that developers, designers, and store managers do not trigger campaigns while browsing the site — but it can also be used to block competitor monitoring, known bots, or any other traffic source identified by IP.
Does IP blocking apply to all campaigns at once, or do I need to set it per campaign?+
IP blocking is set as a targeting condition at the campaign level. You add the exclusion rule to each campaign where you want a given IP or range suppressed. This gives you per-campaign control — for example, you can exclude your team's IP from your main popup while leaving another campaign visible for internal QA review.
Can I block a range of IP addresses, or only individual IPs?+
Both are supported. You can add individual IP addresses for single connections — such as one person's home office — or specify IP ranges to block entire subnets, which is useful for office networks where multiple team members share the same IP pool. You can add as many individual IPs and ranges as needed within a single campaign's targeting rule.
Will blocked visitors know that campaigns have been suppressed for them?+
No. From the perspective of a visitor whose IP matches the exclusion rule, the page behaves exactly as it would without that campaign — no popup fires, no sticky bar appears. There is no error message or notification of any kind. The suppression is silent and invisible to the visitor.
Will blocking internal IPs affect my campaign performance data?+
Yes, in a positive way. Blocking your team's IP addresses means their site visits no longer generate campaign impressions or affect conversion rate calculations. This produces cleaner analytics data that reflects only genuine visitor behavior. If you have been running campaigns without IP blocking for some time, you may notice a slight improvement in measured conversion rates once internal traffic is excluded — because impressions are now more accurately counting real customer sessions only.
Try OptiMonk for free
Launch your first campaign, learn what works, then scale what converts.