Skip to content

Works with your stack

Cookie consent for If-So Dynamic Content

its own check, not ours

← Cookie Rocks for your stack

If-So shows different content to different visitors. It sorts its own cookies into consent categories, but it asks only a few consent plugins it knows, or a filter for developers. Without one of those, it sets every cookie.

By If-So · if-so.com · WordPress.org

Is this your product? Tell us if anything here is out of date. Write to us

What matters for consent with If-So

Versions already seen

_ifso_last_viewed remembers which content versions the visitor already saw, for If-So’s statistics. Its lifetime is a plugin setting.

Visit counts

ifso_visit_counts counts the visitor’s visits, to show personalised content. If-So files it under preferences.

A PHP session cookie

If-So starts a PHP session on your pages, so PHPSESSID is set on the first page, before any choice. It is not one of If-So’s classified cookies and is not removed. If-So’s team considers it generally necessary. You can turn it off under If-So > Settings > Geolocation > Disable use of PHP sessions.

Its own consent check

Before setting a cookie, If-So checks its category and deletes a cookie that is no longer allowed. It does this only with the consent plugins it knows, or a developer filter. Otherwise every category counts as allowed. If-So’s team told us, in November 2026, that the next version will also read the WP Consent API, and that the default of its developer filter will be fixed.

Cookie Rocks today

In our test, ifso_visit_counts and _ifso_last_viewed did not stay in the browser before the choice or after Reject all, and stayed after Accept all. Cookie Rocks recognises _ifso_last_viewed as statistics and ifso_visit_counts as preferences, and lists them in your cookie policy. PHPSESSID was set in every case.

What our tests found on If-So

  • Good to know · If-SoCookie Rocks removes If-So's visit and statistics cookies until consent

    ifso_visit_counts and _ifso_last_viewed wait for consent.

    Seen in our tests, 17 November 2026, If-So 1.10.4.

    Full detail

    If-So sets ifso_visit_counts (about 360 days) through an admin-ajax call and _ifso_last_viewed on the next page. With Cookie Rocks 2.11.8, neither stayed in the browser before the choice or after Reject all, and both stayed after Accept all. If-So itself checks consent only with Cookiebot, Cookie Notice or Complianz, or a developer filter; it does not read the WP Consent API.

  • Good to know · If-SoIf-So starts a PHP session cookie on every page

    PHPSESSID is set before any choice and stays.

    Seen in our tests, 17 November 2026, If-So 1.10.4.

    Full detail

    If-So starts a PHP session, so PHPSESSID is set on the first page before any choice. It is not one of the cookies If-So sorts into consent categories, and Cookie Rocks 2.11.8 does not remove it.

Questions

What happens after the 30-day trial?

The banner, your visitors’ choices and your proofs of consent keep working. Without a key, most settings lock, updates and support stop. Take a key at any time and everything opens again.

For If-So sites

Dynamic content, after the choice.

its own check, not ours

Every feature of the complete plugin for 30 days, no card. If-So keeps working as it does today.

  • During the trial: everything, including the full settings and the scans
  • After 30 days without a key: the banner, your visitors’ choices and your proofs of consent keep working
  • What waits for a key: most settings, updates and support

How the trial works, in detail

Cookie Rocks

Get your trial key

Your e-mail and your site. Your key arrives as soon as you confirm your e-mail.

One trial per domain. Local and staging sites never use up your key.

We keep your e-mail address to send your key and help you with it, as explained in our privacy policy. No newsletter, nothing else.