> ## Knowledge Base Index
> Fetch the complete knowledge base index at: https://help.omegatheme.com/sitemap.xml
> Use this file to discover available pages before exploring further.
> Pure-Markdown content can be obtained by appending a '.md' suffix to the content URLs listed in the sitemap (without the trailing slash).

# Consentik Shopline: Scan cookie

# How the cookie scanner works

Under GDPR, CCPA and similar laws you are expected to tell visitors which cookies your store sets, what each one is for, and how long it stays on their device. Consentik's cookie scanner does the first part of that work for you: it visits your storefront, collects the cookies it finds, and matches them against a cookie database so most of them arrive already described and sorted into a category.
This article covers what the scanner does, how to review its results, and what it cannot find on its own.

## Where to find it
Go to **Cookies Management**. The **Scan now** button sits in the page header.
![](https://storage.crisp.chat/users/helpdesk/website/-/8/3/8/3/8383e5404a31c000/image_gk72ef.png)
Consentik also starts a scan on its own when you open this page, so most of the time the results are already waiting for you. Use **Scan now** when you have just installed a new app or changed your theme and want fresh results immediately.

## Running a scan
1. Open **Cookies Management**.
2. Click **Scan now**.
3. Wait for the button to stop loading. A scan can take **up to two minutes**. Keep the tab open — closing it cancels the scan.
4. The **Scanned Cookies** table appears above your main cookie list.
If **Scan now** is greyed out, your current plan does not include the scanner. The **Pricing** page shows which plans do.

## Reading the results
The **Scanned Cookies** table shows what the last scan found:
| Column | What it means |
| ---- | ---- |
| **Title** | The cookie name. A `*` means the cookie is matched by prefix, because its name ends in a value that changes per visitor. |
| **Platform** | The service that sets the cookie — Google Analytics, Meta, Shopify, and so on. |
| **Purpose** | A plain-language description of what the cookie does. |
| **Transfer** | Whether the cookie has been copied into your main cookie list. |
Cookies the database recognises arrive with a purpose, a platform and a category already filled in. Cookies it does not recognise still get listed — they simply arrive without a category, and you will find them under the **No category** tab of the main table.
Use **Transfer** (or **Transfer all** / **Transfer selected**) to copy a scanned cookie into your main cookie list. **Restore** does the opposite and removes it from that list again. The scan results themselves are kept either way, so restoring something is not destructive — you can transfer it again later.

## Getting a cookie onto your banner
Transferring a cookie is not the last step. A cookie only appears in your banner's cookie table when **both** of these are true:
* it has a **Category** assigned, and
* its **Status** is **Published**.
Scanned cookies are deliberately left unpublished so that nothing reaches your storefront before you have looked at it. To publish one, open it from the main **Cookies** table and set it to **Publish**. While you are there you can correct anything the scanner guessed wrong — Category, Title, Purpose, Platform, Domain, Type and Retention period are all editable.
The tabs across the main table make the review quick:
* **No category** — needs a category before it can go live. Start here.
* **Not published** — categorised but still hidden from shoppers.
* **Published** — currently visible in your banner.
* **Scanned** — everything the scanner has ever contributed.
You can also add a cookie by hand with **Add cookie**, or bulk-edit through **Import/Export** (`.xlsx`, up to 10 MB). Manual entries behave exactly like scanned ones.
## ![](https://storage.crisp.chat/users/helpdesk/website/-/8/3/8/3/8383e5404a31c000/image_kk9vnm.png)