Works with your stack
Cookie consent for Amelia booking forms
the form brings guests
Amelia’s booking form does more than book. It can load payment scripts, Google Maps, reCAPTCHA, and in paid versions Google Analytics and the Meta pixel, as soon as the form appears. Its server can also send the visitor’s IP address to a location lookup to guess the phone country.
By Melograno Venture Studio · wpamelia.com · WordPress.org
Is this your product? Tell us if anything here is out of date. Write to us
Amelia
WordPress plugin
- Tested version
- 2.4.14
- How
- Tested automatically around each Cookie Rocks version
- Last test
- 7 November 2026
- Latest version
- 2.4.14 tested
- Active installs
- 90,000+
What Amelia adds to your visitors’ browser
No trackers In our test of Amelia 2.4.14 on 7 November 2026, the plugin itself added no tracker and no cookie. What you place in your pages with it, such as a video or a map, still counts.
What matters for consent with Amelia
Its own cookies are small
The form remembers light or dark mode, and keeps the booking in the browser during a payment redirect. Login cookies exist only for customers who sign in.
Payment and map scripts
The scripts of the payment methods you enable, like Stripe and PayPal, load on the form page before the payment step. Google Maps loads with an address field and a key.
Tags inside the form
When Google Analytics or a Meta pixel ID is set inside Amelia, its own script loads them as soon as the form appears, with no consent check. Cookie Rocks does not hold tags created inside that script. Leave those fields empty and set the tags up in your site’s own tag instead, which it holds until consent.
The phone country
With the phone country on auto, your server sends the visitor’s IP address to an outside lookup. Choose a fixed country: no call, and no wrong country served from a page cache.
What our tests found on Amelia
Set before the choice · ameliabookingAmelia 2.4.14 and Google Fonts
Amelia 2.4.14 loads Roboto font files from fonts.gstatic.com before any choice on a page with its shortcode. In our test on Cookie Rocks 2.11.2 the Pro copy did not catch them: the call to Google stayed after the daily check.
Seen in our tests, 7 November 2026, ameliabooking 2.4.14.
Set before the choice · Cookie RocksTags created inside a form script are not held
Cookie Rocks 2.11.0 does not hold Google tags or a Meta pixel created in JavaScript from a script of the site, the way Amelia's form script creates them: gtag.js and fbevents.js load before the choice. Tested with a script of the same form, because Amelia's own option is paid.
Seen in our tests, 6 November 2026, Cookie Rocks.
Sent from your server · AmeliaAmelia sends the visitor's IP address to iplocate.io from the server
setting “Default phone country code” · by default: auto
With the phone country on auto, each page with a booking form triggers this lookup. With page caching, the first visitor's country is served to everyone.
What to do: Choose a fixed default phone country.
Read in its code, 5 November 2026, Amelia 2.4.14.
Full detail
With the default phone country set to auto, Amelia's server sends the visitor's IP address to www.iplocate.io/api/lookup/ each time a page with a booking form is built, and writes the country found into the page settings (wpAmeliaSettings). With page caching, the first visitor's country is served to everyone and the call happens only when the cache is filled. A fixed default phone country avoids the call: the setting is auto by default, and the site owner can change it.
Good to know · AmeliaAmelia's booking form sets a colour mode cookie for visitors
- maz-resolved-color-mode (light or dark, 1 year) when the form loads in automatic colour mode, the default.
- ameliaToken and ameliaUserEmail only after a panel login, 30 days by default.
- ameliaCacheData in sessionStorage keeps the booking during a redirect payment.
- Fonts are served from the site.
Read in its code, 16 October 2026, Amelia 2.4.11.
Full detail
The Amelia booking form sets a first-party cookie, maz-resolved-color-mode (light or dark, 1 year, path /, SameSite=Lax), when it mounts with the automatic colour mode (default). ameliaToken and ameliaUserEmail exist only after a customer or employee logs in to the panel and last 30 days by default. sessionStorage ameliaCacheData keeps the booking during a redirect payment. Fonts are served from the site.
Set before the choice · AmeliaAmelia loads payment scripts on every page with a form
- PayPal (www.paypal.com/sdk/js) and Stripe (js.stripe.com/v3/).
- Square (web.squarecdn.com, with a stylesheet from developers.google.com), also in the free version.
- Razorpay (checkout.razorpay.com).
- Google Maps with Places, when a Maps key is set and an address field exists.
Read in its code, 16 October 2026, Amelia 2.4.11.
Full detail
On every page with an Amelia form, the server enqueues the scripts of the enabled payment methods before the payment step: www.paypal.com/sdk/js, js.stripe.com/v3/, web.squarecdn.com/v1/square.js with a stylesheet from developers.google.com (Square, available in the free version) and checkout.razorpay.com. maps.googleapis.com/maps/api/js with Places loads when a Google Maps key is set and an address custom field exists.
Set before the choice · AmeliaAmelia loads Google and Meta tags with no consent check
When configured, its form script loads Google's tag and the Meta Pixel as soon as a form shows. Its reCAPTCHA adds Google's script too. These are paid features.
What to do: Do not enable Meta Pixel or Google Analytics inside Amelia; load them through the site's own tag, which a consent plugin can hold.
Read in its code, 16 October 2026, Amelia 2.4.11.
Full detail
Amelia's form script public.js, served by the site, loads googletagmanager.com/gtag/js (vue-gtag) when Google Analytics or Google Tag is configured, and connect.facebook.net/en_US/fbevents.js then fbq('init') when a Meta Pixel ID is set, as soon as a form mounts, with no consent check and no gtag('consent') call. Its reCAPTCHA component adds google.com/recaptcha/api.js itself. These integrations are reserved to paid licences. Amelia does not use WP Consent API.
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.
- Amelia 2.4.14, 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.
- Settings of the test: Default settings after activation.
- Last run: Amelia 2.4.14 on 7 November 2026, with WordPress 7.1.3.
Bookings, events and courses
Other plugins of the same kind.
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 Amelia users
Bookings, with the visitor’s choice first.
pick a phone country
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.