What cookies Divi uses

Divi has a list of cookies that are being used to ensure it is working as intended.

Eduard Ungureanu avatar
Written by Eduard Ungureanu
Updated over a week ago

Divi creates a list of necessary cookies to ensure it works as intended. However, none of those cookies are storing any sensitive visitor data such as:

  • visitors IP address

  • visitors location

  • visitors personal information

  • etc

Below is a complete list of all the cookies that Divi is using. Some of those cookies also depend on the features that are enabled.

I. AB Testing

et_pb_ab_{$record_type}_{$post_id}{$test_id}{$cookie_subject}

1. $record_type => AB Testing action type

2. $post_id => Post ID where the AB Testing is enabled

3. $test_id => AB Testing test ID on the post

4. $test_id => Cookie subject

Scope:

et_pb_ab_view_page_{$post_id}{$test_id}

To verify whether current visitor already visit a page with AB Testing subjects.

- Hashed AB Testing subject ID (string)

- When the browser closes

et_pb_ab_read_page_{$post_id}{$test_id}($cookie_subject}

To verify whether current visitor already spends amount of time to read the page with AB Testing subjects.

- 'true' boolean value (boolean)

- 1 year

et_pb_ab_read_goal_{$post_id}{$test_id}($cookie_subject}

To verify whether current visitor already spend at least 3 seconds to read the goal on the page with AB Testing subjects.

- 'true' boolean value (boolean)

- 1 year

et_pb_ab_view_goal_{$post_id}{$test_id}($cookie_subject}

To verify whether current visitor already view the goal on the page with AB Testing subjects.

- 'true' boolean value (boolean)

- 1 year

et_pb_ab_click_goal_{$post_id}{$test_id}

To verify whether current visitor already click the goal on the page with AB Testing subjects.

- 'true' boolean value (boolean)

- 1 year

et_pb_ab_con_goal_{$post_id}{$test_id}($cookie_subject}

To verify whether current visitor already done some specific actions on the modules (AB Testing goals). The actions are:
- Already visits Thank You page and comes from the Shop module
- Already sends message via Contact Form module
- Already subscribes successfully to newsletter on Email Optin module
- Already submits comment via Comment module

- 'true' boolean value (boolean)

- 1 year

et_pb_ab_con_short_{$post_id}{$test_id}

To verify whether current visitors already visit a page with shortcode tracking enabled.

- 'true' boolean value (boolean)

- 1 year

Area: Frontend

et_pb_ab_shop_log

Scope: Determine whether to log the conversion if the visitor is on Thank You page and comes from the Shop module (goal) or not.

Data saved: Post ID, AB Testing subject ID, Test ID as a single string separated by _ (string).

Expiration time:

  • One year

  • Once the conversion is logged

Area: Frontend

et_pb_ab_shortcode_track_{$post_id}

( $post_id => Post ID where the AB Testing is enabled)

Scope: Determine whether to log the conversion if a visitor visits a page with shortcode tracking enabled.

Data saved: Post ID, AB Testing subject ID, Test ID as a single string separated by _ (string).

Expiration time:

  • One year

  • Once the conversion is logged

Area: Frontend

et_pb_ab_comment_log_{$post_id}{$test_id}

  1. $post_id => Post ID where the AB Testing is enabled

  2. $unique_test_id => AB Testing test ID on the post

Scope: Determine whether to log the conversion if a visitor visits a page with shortcode tracking enabled.

Data saved: true boolean value (boolean)

Expiration time:

  • One year

  • Once the conversion is logged

Area: Frontend

II. Builder

et-{$type}-post-{$post_id}-{$editor}

  1. $type => Action type.

  2. $post_id => Post ID where the editor used.

  3. $editor => Editor type. Possible values:

    1. bb => Classic Builder

    2. fb => Visual Builder

Derived Format/Name:

  • et-editing-post-{$post_id}-bb

    Scope: As identifier if Classic or Backend Builder is editing the post data.

    Data saved: bb or bfb as builder type ID (string)

    Expiration time: 5 minutes, Once the autosave process done

    Area: Backend

  • et-editing-post-{$post_id}-fb

    Scope: As identifier if Visual Builder is editing the post data.

    Data saved: fb as builder type ID (string)

    Expiration time: 5 minutes, Once the autosave process done

    Area: Backend

  • et-was-editing-post-{$post_id}-bb

    Scope: As identifier if Classic or Backend Builder was being used to edit the post data.

    Data saved: bb or bfb as builder type ID (string)

    Expiration time: 10 seconds

    Area: Backend

  • et-was-editing-post-{$post_id}-fb

    Scope: As identifier if Visual Builder was being used to edit the post data.

    Data saved: fb as builder type ID (string)

    Expiration time: 10 seconds

    Area: Backend

  • et-saving-post-{$post_id}-bb

    Scope: As an identifier if Classic or Backend Builder saves the post data.

    Data saved: bb or bfb as builder type ID (string)

    Expiration time:

    • Once the saving process done

    • Set editor in use

  • Area: Backend

  • et-saving-post-{$post_id}-fb

    Scope: As identifier if Visual Builder is saving the post data.

    Data saved: fb as builder type ID (string)

    Expiration time:

    • Once the saving process done

    • Set editor in use

    Area: Backend

  • et-saved-post-{$post_id}-bb

    Scope: As identifier if Classic or Backend Builder saved the post data successfully.

    Data saved: bb or bfb as builder type ID (string)

    Expiration Time:

    • 5 minutes

    • Set editor in use

    Area: Backend

  • et-saved-post-{$post_id}-fb

    Scope: As identifier if Visual Builder saved the post data successfully.

    Data saved: fb as builder type ID (string)

    Expiration time:

    • 5 minutes

    • Set editor in use

    Area: Backend

  • et-recommend-sync-post-{$post_id}-bb

    Scope: Recommends Visual Builder to sync post data from Classic Builder.

    Data saved: bb or bfb as builder type ID (string)

    Expiration time:

    • 30 seconds

    • Once the sync process run

    Area: Backend

  • et-recommend-sync-post-{$post_id}-fb

    Scope: Recommends Classic or Backend Builder to sync post data from Visual Builder.

    Data saved: fb as builder type ID (string)

    Expiration times:

    • 30 seconds

    • Once the sync process run

    Area: Backend

  • et-syncing-post-{$post_id}-bb

    Scope: As identifier if Classic or Backend Builder is syncing post data from Visual Builder.

    Data saved: bb or bfb as builder type ID (string)

    Expiration time:

    • 30 seconds

    • Once the saving process done

  • Area: Backend

  • et-syncing-post-{$post_id}-fb

    Scope: As identifier if Classic or Backend Builder is syncing post data from Visual Builder.

    Data saved: fb as builder type ID (string)

    Expiration time:

    • 30 seconds

    • Once the saving process done

    Area: Backend

  • et-editor-available-post-{$post_id}-bb

    Scope: As identifier if Classic or Backend Builder editor is available for the current post.

    Data saved: - bb or bfb as builder type ID (string)

    Expiration time:

    • - 30 minutes
      - Before the window is closed

    Area: Backend

  • et-editor-available-post-{$post_id}-fb

    Scope: As identifier if Visual Builder editor is available for the current post.

    Data saved: fb as builder type ID (string)

    Expiration time:

    • 30 minutes

    • Before the window is closed

    Area: Backend

  • et-reloaded-post-{$post_id}-vb

    Scope: As identifier if Visual Builder is reloaded.

    Data saved: - true boolean value (boolean)

    Expiration Time: - 5 minutes

    Area: Backend

et_forced_localstorage_clear

Scope: To verify whether the Classic Builder should clear module definitions on local storage or not.

Data saved: Elegant Theme product version (string)

Expiration time: 5 minutes

Area: Backend

et-pb-recent-items-{$recent_item_storage}

Scope: Store recent items generated for Select Advanced options.

Data saved: - Recent items for select options separated by | (string)

Expiration time: 1 year

Area: Backend

et-pb-recent-items-colors

Scope: Store recent used colors generated for Color field type

Data saved: Recent colors separated by | (string)

Expiration time: 1 year

Area: Backend

et-pb-recent-items-font_family

Scope: Store recent font families list generated for Font Family field type

Data saved: Recent font families for font family options separated by | (string)

Expiration time: 1 year

Area: Backend

Did this answer your question?