Snipfire Pro features Pro
Pro · The pages in this section need Snipfire Pro, installed next to the free plugin. Plans
| Feature | What it does | Plan |
|---|---|---|
| SCSS and LESS | Write stylesheets in SCSS or LESS, with shared partials | Pro |
| Testing mode | Try a snippet on the live site where only you, your team and people with a preview link see it | Pro |
| Cookie consent | Hold tracking scripts back until the visitor accepts cookies, then run them without a reload | Pro |
| Visual hook finder | See every hook on a real page, and create a snippet on one in a click | Pro |
| Team access | Choose what each WordPress role may do: nothing, view, CSS/JS/HTML only, or everything | Pro |
| Activity log | Who changed which snippet or setting, when, and from where | Pro |
| More conditions | Visitor country and region (EU, continent), referrer, language, cookie consent given, WooCommerce cart and customer rules | Pro |
| History | The last 50 versions of each snippet, instead of 10 | Pro |
| Git sync | Two-way sync of your snippets with GitHub or GitLab | Agency |
All of these are also in the Agency plan, which adds Git sync. The free trial is of the Agency plan, so you can try everything.
If Pro is switched off or your licence ends
Your snippets keep running. Settings that need Pro are kept with each snippet and stay safely off until Pro is active again: a script waiting for cookie consent doesn't run, a snippet in testing mode runs for nobody, Pro conditions never match, and SCSS/LESS stylesheets keep their last compiled CSS. Details in Licence.
Something unclear or missing? Tell us