Scan Behind Login

Last updated on October 16, 2024

The Scan Behind Login feature in CookieYes allows for the detection and identification of cookies set after user login, ensuring a thorough analysis of your website’s cookie compliance.

Note

Scan Behind Login is available to Ultimate plan users on request. Reach out to our Technical Support to access this feature.

To activate this feature, we require your registered website URL, your login form URL, and details about your login page. This documentation explains how to obtain the required data.

Note

  • CookieYes Scan behind login only works with websites that use cookie-based logins, i.e. sites that temporarily store login details in cookies.
  • Your website should display a same-page login, with all necessary fields—such as email or username, password, and submit button—on a single page.

How to Obtain Data Required for Scan Behind Login

Create a Test Account: Create a test account in your application. You will need to share the login credentials for this account, including the email or username and password.

To gather the required information for each field on your login form, follow these steps:

Step 1: Open Developer Tools

  1. Right-click on your login page.
  2. Select Inspect to open the Developer Tools.

Step 2: Locate the Login Form

  1. In the Elements tab of Developer Tools, hover over the HTML elements. The section of code for the login form will be highlighted as you hover.
  2. The form is typically enclosed in a <form> tag. Click to expand the <form> to make all the forms visible. Make sure you identify the correct form if there are multiple forms on the page.

Step 3: Identify Form Field Item

example of login field items

1. Email Input

email input
  • Locate the Email Input Field: Look for for an <input> tag, which is a box where users enter their email or username. Typically, it uses a label like Email or Username, making it easy to identify.
  • Required Details:
    • itemType:input ; This will be marked as input in the code.
    • identifier: username ; Look for a part of the code that says id="username" or name="username". This is the field’s identifier.
    • identifierType:id ; This usually indicates how the field is recognized in the code (often id or name).
    • value: The email placeholder or value of the newly created test account (e.g. test@gmail.com)

2. Password Input

password input
  • Locate the Password Input Field: Look for an <input> tag labeled Password.
  • Required Details:
    • itemType: input This will also be marked as “input.”
    • identifier: password Look for id="password" or name="password".
    • identifierType: "id" Similar to the email field, it will often be id or name.
    • value: The password placeholder or value of the newly created test account (e.g. 12345678)

Note:

Your login form may include additional fields beyond just email and password, so be sure to include extra fields that are present.

3. Submit Button

submit button
  • Locate the Submit Button: Find the <button> tag or <input> tag of type submit. This is the button that users click to log in. It typically uses a label like Email or Username.
  • Copy the Required Details:
    • itemType: button This is typically marked as “button” or “input type=’submit'” in the code.
    • identifier: submit Look for id="submit" or similar labels.
    • identifierType: id This is often id or name.

4. Login Trigger (If Present)

Identify Login Trigger: A login trigger is a button or link that opens the login form when users click it and it is usually labels such as Log In, Sign In. It appears on pages where the login form is not immediately visible.

login trigger
  • Required Details:
    • In the code, check for any onclick events associated with the submit button.
    • Note any specific functions or actions mentioned next to the submit button in the code.

Step 4: Compile the data

Once you have collected all the necessary details, you can compile them as follows:

Registered Website URL:

Login form URL: 

Form field Items

       Email Input
          itemType: "input"
          identifier: "email"
          identifierType: "name"
          value: "test@gmail.com"
       
        Password Input
          itemType: "input"
          identifier: "password"
          identifierType: "type"
          value: "12345678"
        
        Submit Button
          itemType: "button"
          identifier: "button"
          identifierType: "type"

       Login trigger :

After compiling the data, send it to our technical support at support@cookieyes.com

Gathering the required details about your login form and any triggers allows for a thorough scan of your cookie usage behind the login wall.

Have more questions?

Reach out to us and we'll answer them.

Contact us