Skip to main content

Verify Kickbite thank-you scripts and consent

How brands verify Kickbite thank-you scripts fire only at the same consent level as the rest of the site — private-window Network checks with and without cookies.

Written by Juan Garzon

Use this checklist when Payment Providers (or similar checkout referrers) stay high, or when journeys look like they start on the thank-you page. The usual cause is a consent mismatch: Kickbite loads on thank-you without consent, while the rest of the site only loads Kickbite after consent.
​

Goal: prove that the thank-you Kickbite scripts follow the same consent rules as the site-wide Kickbite scripts.
​

What “correct” looks like

  • Without consent: Kickbite does not load on browse pages or on thank-you.

  • With consent: Kickbite loads on browse pages and on thank-you (after the shopper accepts).

  • Wrong: thank-you fires Kickbite even when cookies were refused, while browse pages stay silent until consent.

Prepare

  • Use a private / incognito window (no existing cookies).

  • Open DevTools → Network. Filter by kickbite or tr.kickbite.io.

  • Keep DevTools open while you browse and checkout.

  • Have a refundable payment method ready for a test order.

Test A — Refuse consent

  1. Open your shop in a private window.

  2. Do not accept the cookie banner.

  3. Browse 2–3 pages (home, category, product). In Network, confirm there are no requests to tr.kickbite.io (no u.js / script.js).

  4. Go through checkout to the thank-you page, still without accepting cookies.

  5. On thank-you, check Network again.

Pass: still no Kickbite requests on thank-you.

Fail: Kickbite loads or fires on thank-you without consent. Fix the thank-you tag / GTM / CMP trigger so Kickbite waits for the same consent event as the rest of the site.

Test B — Accept consent

  1. New private window.

  2. Accept cookies (marketing / analytics — whatever group Kickbite sits in).

  3. Browse a few pages. Confirm Kickbite does load (tr.kickbite.io requests appear).

  4. Complete checkout to thank-you.

  5. On thank-you, confirm Kickbite loads again and the conversion snippet runs (you should see the scripts and a conversion-related call after the page settles).

Pass: Kickbite on browse and thank-you only after consent.

Fail: site-wide never loads after consent, or thank-you still never loads — then the install or CMP mapping is wrong (not only a thank-you exception).
'

Quick tip in Elements

On thank-you, search the page HTML for tr.kickbite.io and w.kbd. Scripts present in HTML does not always mean they ran — Network is the source of truth for whether they fired under that consent state.
​

After you fix a fail

  1. Repeat Test A and Test B.

  2. Wait for one complete Kickbite day (data through yesterday), then check whether Payment Providers share of orders dropped.

  3. If it is still high after consent is correct, contact Kickbite CS with the screenshots below.

What to send Kickbite CS

  • Market name

  • Screenshot: Network on a browse page without consent

  • Screenshot: Network on thank-you without consent

  • Screenshot: Network on browse + thank-you with consent

  • Test order id and date (if you placed one)

Related reading

Did this answer your question?