Works with your stack
Cookie consent for Pixel Caffeine
pixel on every page
Pixel Caffeine adds the Meta pixel to every page as soon as a pixel ID is saved. It has no consent setting. The pixel is advertising, so it has to wait for the visitor’s yes.
By AdEspresso · adespresso.com
Is this your product? Tell us if anything here is out of date. Write to us
Pixel Caffeine
WordPress plugin
- Tested version
- 2.3.3
- How
- Tested automatically around each Cookie Rocks version
- Last test
- 7 November 2026
What Pixel Caffeine adds to your visitors’ browser
Trackers it loads
- Meta Pixel →Marketing3 browser storage keys
Cookies seen in our test
fr
Also from your server Meta Conversions API only when its server-side option is on (off by default) and a token is saved. A banner holds what runs in the visitor’s browser. What Pixel Caffeine sends from your server is set in Pixel Caffeine itself.
What matters for consent with Pixel Caffeine
The pixel starts at once
The pixel code is printed in the page itself, in the head or the footer. Nothing in the plugin waits for a choice.
The cookies are Meta’s
Pixel Caffeine sets no cookie of its own. The cookies come from Meta’s script, so holding that script holds them too.
Server events
The optional Conversions API sends events to Meta from your server, with no consent check. No banner can hold them. It is off until you save an access token: leave it off if you cannot hold it.
Cookie Rocks with Pixel Caffeine
- Holds the scripts it adds to your pages, such as tags, pixels or a chat, until the visitor consents. In advanced Consent Mode, Google’s tags load with consent denied instead.
What our tests found on Pixel Caffeine
Good to know · Pixel CaffeinePixel Caffeine is closed on WordPress.org and gets no updates
Pixel Caffeine is closed on WordPress.org since 30 November 2021 at the author's request and can no longer be downloaded there. Sites that still run it use a copy that gets no updates from the directory.
Seen in our tests, 18 October 2026, Pixel Caffeine.
Sent from your server · Pixel CaffeinePixel Caffeine's Conversions API sends events from the server, no consent check
setting “aepc_enable_server_side” · by default: no
Events go to graph.facebook.com from the site's server, so no banner can hold them. It is off by default and needs a saved access token.
Read in its code, 16 October 2026, Pixel Caffeine 2.3.3.
Full detail
Pixel Caffeine's optional Conversions API sends events to graph.facebook.com from the site's server, on template_redirect and shutdown and through its REST route aepc/v1/fbq, without any consent check. No consent banner can hold these server events. It is off by default and needs a saved access token.
Set before the choice · Pixel CaffeinePixel Caffeine prints the Meta pixel on every page, with no consent setting
As soon as a pixel ID is saved, the pixel code is in every page. The plugin sets no cookie itself: _fbp and _fbc come from Meta's script. A filter can add type="text/plain" to the tag.
Read in its code, 16 October 2026, Pixel Caffeine 2.3.3.
Full detail
Pixel Caffeine 2.3.3 has no consent setting and no fbq('consent') call: as soon as a pixel ID is saved, it prints the Meta Pixel code (fbq('init') and fbevents.js) in an inline script on every page, in the head or the footer. It sets no cookie of its own; _fbp and _fbc come from Meta's script and the plugin only reads them. Its filter aepc_init_script_attributes can add type="text/plain" to the pixel tag.
How we test it
Around each version, with its latest release
Around each Cookie Rocks version, a fresh WordPress installs its latest version from WordPress.org next to Cookie Rocks and runs the same checks. A new version joins the next run on its own.
- Pixel Caffeine 2.3.3, tested on 7 November 2026.
- The banner shows, the trackers of the test page wait for consent and load after it, and Cookie Rocks raises no PHP error.
- Its own tags, set with a test ID, do not load before the choice and load after “Accept all”.
- Settings of the test: Meta Pixel ID (test value).
- Last run: Pixel Caffeine 2.3.3 on 7 November 2026, with WordPress 7.1.3.
Analytics and ad pixels
Other plugins of the same kind.
Questions
Can the pixel tag be held?
Yes, by its tag. Pixel Caffeine has a filter that can mark the pixel tag so it does not run until a consent plugin releases it. Cookie Rocks holds known trackers such as the Meta Pixel until consent.
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 Pixel Caffeine users
The pixel waits for a yes.
advertising needs consent
Every feature of the complete plugin for 30 days, no card.
- 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
Get your trial key
Your e-mail and your site. Your key arrives as soon as you confirm your e-mail.