Use Lookup fields to dynamically populate field options and values with the data from submitted entries. Lookup fields can be used for several types of dynamic field relationships. Use them to:
Retrieve submitted values and use them as options in a dropdown, radio, or checkbox field, or for display only.
Set up cascading field options. This is perfect for country/state/city or year/make/model fields where the available options are filtered by the value selected in a prior field.
Filter down to a price or final value. Allow the user to select options from Lookup fields which will ultimately display a final price or value in a text/number field.
Dynamically populate field values. Allow users to select or enter a value in a Lookup field which will populate fields in the form with values from the same entry.
Select the field in the form builder to see its options in the Field Options tab. The panel has 3 parts: the basic settings at the top, the Lookup Options section, and the Advanced section.
A Lookup field has the following standard options:
To allow users to select more than one option in a Lookup dropdown, check Multiselect. It sits below Limit options to those created by the current user and is unchecked by default. Users hold down the Command or Control key to select more than one option.
The Get Options From setting loads options into your Lookup field from entries submitted in another Formidable form. Nothing is selected by default. Start by selecting the form, then the field you want to pull the entries from.
In the Display Type dropdown, choose how to show the options: Dropdown, Radio Buttons, Checkboxes, Single Line Text, or List (for display only). Dropdown is the default.
The List option displays a value when it's watching another Lookup field.
A Lookup field can show its options as images. It does this automatically when the Display Type is Radio Buttons or Checkboxes and the options come from a field that uses images. The source can be a Radio Buttons, Checkboxes, or Product field with image options, or a File Upload field.
After you choose the source, click Update and select the field again. These settings then appear in the field options:
Image option label: Shown only when the options come from a File Upload field. Choose another field from the form the options come from to label each image, or keep File name to use the name of the uploaded file.
Image Size: Choose Small, Medium, Large, or Extra Large. Small is the default.
Hide option labels: Check this box to show the images without their text labels.
With a File Upload source, the options show as images only when most of the uploaded files are images.
A Lookup Dropdown field can show a value in place of its normally blank first option. To set one, open the Advanced section and enter it in the Placeholder Text setting, which is empty by default.
To show suggestions to users as they type a search, check Autocomplete. This box is unchecked by default. This feature uses the Slim Select dropdown library, so autocomplete also works on mobile devices.
When Multiselect and Autocomplete are both checked, users can choose several options without holding down the Command or Control key.
To limit the values displayed, click Watch a Lookup Field under Filter by Lookup Fields and choose another Lookup field in your form. The options are then filtered by the value selected in the watched field. No fields are watched by default.
To show only the options created by the user who is filling out the form, check Limit options to those created by the current user. This box is unchecked by default. The limit doesn't apply to administrators.
The options are sorted in ascending order by default. To change this, choose Ascending (A-Z), Descending (Z-A), or No order set in the Option order dropdown.
The Saved Value and Displayed Value settings show only when the source field has Separate Values enabled or is a Dynamic field. Each one is set to Option Value by default. When the options show as images, choose Option Label in Displayed Value to show the option labels under the images instead of the saved values.
If these settings don't show right away, click Update to save the form and refresh the field options.
Display the value submitted in a Lookup field in a form's confirmation message, email, or View. Just insert [x], where x is the ID or key of the Lookup field.
To pull lookup data from another form's entries without exposing it on the front end, enable the Lookup option on a Virtual Field. The looked-up value is stored server-side and never rendered in the form HTML, which is useful when the data needs to stay hidden from the user.
Add an individual Lookup field to your form to use submitted values as its options.
Create a new form or go into an existing form where you want to add a Lookup field.
Add a Lookup field to your form. By default, a Lookup field displays as a dropdown. You can change the Display Type to Radio Buttons, Checkboxes, Single Line Text, or List instead.
Set Get Options From to any form and field on your site.
In the field options, select the Option order that you want. You can display options in ascending order (A-Z), descending order (Z-A), or set no order.
To show the user only the values that they submitted, scroll down to Lookup options. Then check Limit options to those created by the current user. Administrators still see every option. To test the limit, view the form as a user who isn't an administrator.
For a Lookup → Dropdown field, open the Advanced section and enter a value in the Placeholder Text box. It shows on the normally blank first option.
Click Update. On a new form, this button reads Save until the first save, which asks you to name the form. Then go to Preview → On Blank Page. Now the user can select a value from their submitted entries. The placeholder text is the first option.
Note: Currently, the cascading lookup feature has some limitations when the primary field retrieves a value from a Name field.
There are many situations where setting up cascading Lookup fields is useful. One of the most common is a country/state/city scenario. Another common use for this is a vehicle year/make/model scenario. Regardless of the cascading scenario, the directions below can be adapted to apply to your use case.
Create a new form. We'll call this the 'Data form' because it will be used to hold all of the year/make/model data, i.e., all of the data that will be retrieved and filtered in the Lookup fields. Add a text field for the Year, a text field for the Make, and a text field for the Model.
Import a CSV with all of the year/make/model data into the Data form. If you import a CSV, then match up the CSV headings with the fields in your Data form. If you don't have a CSV to import, you can manually create entries in the Data form.
Create a second form. We'll call this the 'End User form' because it will be the form that the end user interacts with.
Add a Lookup field for the vehicle year. Set it up to Get options from: Data form → Year field.
Add a Lookup field for the vehicle make. Set it up to Get options from: Data form → Make field. Click Update (Save on a new form) before you set up the filter. Until the form is saved, the list shows each new Lookup field by its default label, Lookup, instead of the label you gave it. After the update, the builder shows Add Fields, so click the Make field again to reopen its options. We want the Make options to change depending on the selected year. Under Filter by Lookup Fields, click Watch a Lookup Field and select Year.
Add a Lookup field for the vehicle model. Set it up to Get options from: Data form → Model field. We want the Model options to change depending on the selected year and make. Under Filter by Lookup Fields, click Watch a Lookup Field and select Year. Click it again and select Make.
In the End User form, click Update. Then go to Preview → On Blank Page. When you select a Year, the Make options change. When you select a Make, the Model options will update.
Let us say you already have cascading lookup fields and want to filter its options. A common use for this is when you want to show only active employees in another form. Regardless of the cascading scenario, the directions below can be adapted to apply to your use case.
Create a new form. We will call this the Employee Form that will hold all of the employee name/status data, i.e. all of the data that will be retrieved and filtered in the Lookup fields. Add a name field for the Name and a dropdown or radio field for the Status.
Import a CSV with all the name/status data into the Employee form. If you import a CSV, then match up the CSV headings with the fields in your Employee form. If you don't have a CSV to import, manually create entries in the Employee form.
Create a second form. We will call this the End User form because it will be the form which the end user will interact with.
Add a Lookup field for the Status. Set it up to Get options from: Employee form → Status field. Open the field's Advanced section:
Set Default Value to Active.
Set Visibility to Administrator to prevent other users from seeing the field.
Add a Lookup field for the Name. Set it up to Get options from: Employee form → Name field. Click Update so the next list shows the Status field by its label. Click the Name field again to reopen its options. We want the Name field options to change depending on the selected Status. Under Filter by Lookup Fields, click Watch a Lookup Field and select Status.
In the End User form, click Update. Then go to Preview → On Blank Page. The Status Lookup field acts as a filter: the Name Lookup field lists only the employees with Active status. Users who aren't administrators don't see the Status field. As an administrator, you still see it in the preview.
To allow multiple selections in cascading fields, use Lookup checkboxes. One of the most common scenarios is a hotel/floor/room scenario. The directions below can be adapted to apply to this use case.
Create a new form called Data form. This form will be used to hold all of the hotel/floor/room, i.e., all of the data that will be retrieved and filtered in the Lookup checkbox fields. Add a text field for the Hotel, a text field for the Floor Number, and a text field for the Room Number.
Import a CSV with all of the hotel/floor/room data into the Data form and make sure that the CSV headings match up with the fields. If you don't have a CSV to import, you can manually create entries in the Data form.
Create a second form called End User form. This will be the form that the end-user interacts with.
Add a Lookup field for the Hotel and set its Display Type to Checkboxes. Set it up to Get options from: Data form → Hotel field.
Add a Lookup field for the Floor Number and set its Display Type to Checkboxes. Set it up to Get options from: Data form → Floor Number field. Click Update so the next list shows the Hotel field by its label. Click the Floor Number field again to reopen its options. We want the Floor Number options to change depending on the selected Hotel. Under Filter by Lookup Fields, click Watch a Lookup Field and select Hotel.
Add a Lookup field for the Room Number and set its Display Type to Checkboxes. Set it up to Get options from: Data form → Room Number field. For the Room Number options to change depending on the selected Hotel and Floor Number, click Watch a Lookup Field and select Hotel. Click it again and select Floor Number.
In the End User form, click Update. Then go to Preview → On Blank Page. When you check more than one hotel, the Floor Number options include the floors of every checked hotel. When you check one or more floors, the Room Number options update the same way.
There are many instances where it is useful for a user to select options in one or more fields which then spits out a final value that is retrieved by using the options selected in other fields. Lookup fields can be used for this. To help make the instructions below more clear, we will assume the end goal is to create a form where a user selects a State and their age range which then displays a policy price in a Text field.
Create a new form called Insurance Data Form. It holds the insurance policy data. Add a field for the State, a field for the Age, and a Text field for the Price.
Import a CSV with all of the insurance policy data into the Insurance Data Form. If you import a CSV, then match up the CSV headings with the fields in your Insurance Data Form. If you don't have a CSV to import, you can manually create entries in the Insurance Data Form.
Create a second form. We'll call this the 'End user form' because it will be the form that the end user interacts with.
Add a Lookup field for the State. Set it up to Get options from: Insurance Data Form → State field.
Add a Lookup field for the Age. Set it up to Get options from: Insurance Data Form → Age field. Click Update so the next list shows the State field by its label. Click the Age field again to reopen its options. We want the Age options to change depending on the selected State. Under Filter by Lookup Fields, click Watch a Lookup Field and select State.
Add a Text field for the price. In its field options, open the Advanced section and set up the Lookup settings:
Turn on the Lookup toggle.
Set Search In to Insurance Data Form → Price field.
We want the price to change depending on the selected State and Age. In the watch dropdown below Search In, select State. Click Watch a Lookup Field and select Age in the new row. After you save the form, these rows show under the Watch Lookup Fields label.
Typically, check Read Only so users can't change the value. To make the value appear as floating text rather than a field input, type frm_total in the CSS Layout Classes box and press Enter.
In the End User form, click Update. Then go to Preview → On Blank Page. When you select a State and Age, a price is displayed in the Text field.
Set up fields that fill in automatically when a user selects an entry.
Go into edit the form that you want to autofill.
Add a Lookup field. Set it up to Get options from: a form and field. It's acceptable to set it up to get options from the current form. Click Update so the Lookup field shows by its label in the next step.
Set Search In to the same form that the Lookup field is getting its options from. Then select the field whose value you want to fill in (for example, Email).
In the watch dropdown below Search In, select the Lookup field from step 2.
Repeat the previous step for each field that you want to autofill.
Click Update. Then go to Preview → On Blank Page. When you select an entry in the Lookup field, the fields that are 'watching' it populate automatically.
The following field types can be populated automatically by watching a Lookup field:
Text
Paragraph
Email
Website/URL
Time
User ID
Number
Phone
Date
Dropdown
Hidden
Virtual
A Text, Hidden, or Virtual field can search any field in the other form. Every other field type searches only fields of the same type. For example, a Number field can only search a Number field. When the other form has only text fields, the Number field's Search In field list is empty.
This option will be added to additional field types in future releases.
There may be situations where you want a user to enter a first and last name, for example, and then other form fields automatically populate. Or you may want users to enter an ID number and fields automatically populate with data for that ID number. You can set this up with Lookup fields.
Go into edit the form that you want to autofill.
Add a Lookup → Single Line Text field. Set Search In to the form and field that you want to search for a first name. Until the form is saved, this option is labeled Get Options From.
Add a second Lookup → Single Line Text field. Set Search In to the same form as step 2, but a different field. This will be the field for the user to enter a last name. Skip this step if a second lookup field is not needed. Click Update so both Lookup fields show by their labels in the next step.
Add other non-Lookup fields to your form. Open the field options for a field that you want to autofill. Open the field options → Advanced and turn on the Lookup toggle. Set Search In to the same form that the Lookup fields are searching values from. Then select the field whose value you want to fill in.
In the watch dropdown below Search In, select the Lookup field from step 2. Click Watch a Lookup Field and select the Lookup field from Step 3.
Repeat the previous step for each field that you want to autofill.
Click Update. Then go to Preview → On Blank Page. When you type in a first and last name in the Lookup fields, the other fields that are 'watching' them populate automatically. This happens when a match is found for the entered first and last name.
You may want a user to select an entry in the Lookup field and automatically populate another field with its entry ID. A typical scenario is to create a form where a user selects a school, which then displays the entry ID in a field. The directions below can be adapted to apply to this use case.
Create a new form called Data Form. This form will be used to hold the list of school names and their entry ID. Add a text or hidden field for "Entry ID" and another field for "School."
Before you add any schools, add this code example to save the entry ID of each new entry in the "Entry ID" field. Remove any default values and change the visibility to Administrators only if you're using a text field.
Either import a CSV or manually create an entry for each school in the Data Form. The code fills in the Entry ID only for entries created after it's in place. Entries that already existed keep an empty Entry ID, even when you edit and update them. To fill it in for those schools, import or create their entries again, and then delete the old entries.
Create a second form called End User form. It will be the form that the end-user interacts with.
Add a Lookup field for "School". Set it up to Get options from: Data form → School field. Click Update so the next step lists the School field by its label.
Add a text or hidden field for "Entry ID" which will autofill with the entry ID of the selected School. (See the list of the types of fields you can autofill.) In its field options, open the Advanced section and set up the Lookup settings:
Turn on the Lookup toggle.
Set Search In to Data Form → Entry ID field. This is the form where the "School" Lookup field options are stored.
In the watch dropdown below Search In, select the "School" Lookup field from step 5.
Click Update. Then go to Preview → On Blank Page. When you select an entry in the "School" Lookup field, the "Entry ID" field that is watching it populates automatically.
To copy a value from a non-Lookup field to a Lookup field, use the code below. This is especially useful in cases where the first field cannot be a Lookup. For example, the first field's value may be the result of a Field Calculation instead of a simple selection. The best place to add these code samples is either in your Theme's footer section or the After Fields section of your form Settings → Customize HTML tab.
To allow users to enter a value that's automatically validated, use lookup fields. For this use case, we will validate the value entered in a number field.
Create a new form called Number Validation Entry Form. This form will be used to hold the numerical values that will be validated.
Add a number field and label it Number Validation. Submit an entry for each value that you want to include in the validation.
Go into an existing form, or create a new form, where users can enter a value and trigger the validation.
Add a Lookup → Single Line Text field and label it as Number Validation. Set Search In to the Number Validation Entry Form → Number Validation field. Until the form is saved, this option is labeled Get Options From. Click Update now so the field shows by its label in step 5.
Add a Hidden field to the form. In its field options, open the Advanced section and set up the Lookup settings:
Turn on the Lookup toggle.
Set Search In to Number Validation Entry Form → Number Validation field.
We want to validate the value depending on whether it matches an entry in the Number Validation Entry Form. In the watch dropdown below Search In, select the Number Validation Lookup field.
In the form builder, select your Submit button and add conditional logic. Show or enable the submit button if:
Hidden field does not equal to ________(leave blank)
Add an HTML field with a validation message. You can add some CSS styling, if you want.
Add conditional logic to the HTML field and set it up to Show this field if ALL of the following match:
Hidden field equals to ______(leave blank)
Number validation does not equal to ______(leave blank)
This article may contain affiliate links. Once in a while, we earn commissions from those links. But we only recommend products we like, with or without commissions.
In this article
Get More Done In Less Time With Better
WordPress Forms
Upgrade your
workflow with advanced WordPress forms and integrated Views.
We use cookies to improve your experience on our site. By using our site, you consent to cookies.
This website uses cookies
Websites store cookies to enhance functionality and personalise your experience. You can manage your preferences, but blocking some cookies may impact site performance and services.
Essential cookies enable basic functions and are necessary for the proper function of the website.
Name
Description
Duration
Geolocation Config
This cookie is used to store the consent settings based on the visitor's location.
90 days
Cookie Preferences
This cookie is used to store the user's cookie consent preferences.
90 days
These cookies are needed for adding comments on this website.
Name
Description
Duration
comment_author
Used to track the user across multiple sessions.
Session
comment_author_email
Used to track the user across multiple sessions.
Session
comment_author_url
Used to track the user across multiple sessions.
Session
Easy Digital Downloads is a complete eCommerce solution for WordPress.
Name
Description
Duration
edd_items_in_cart
Stores information about the cart.
Session
edd_session_
Stores information about the current user session.
Session
Formidable Forms is used to manage forms on this website.
Name
Description
Duration
frm_form_
Saves the ID of the form and the time the entry was submitted.
2 hours
These cookies are used for managing login functionality on this website.
Name
Description
Duration
wordpress_logged_in
Used to store logged-in users.
Persistent
wordpress_sec
Used to track the user across multiple sessions.
15 days
wordpress_test_cookie
Used to determine if cookies are enabled.
Session
Statistics cookies collect information anonymously. This information helps us understand how visitors use our website.
Google Analytics is a web analytics service offered by Google that tracks and reports website traffic.
Used to determine if the user is in a new session/visit.
Session
__utmt
Used to throttle request rate.
10 minutes
__utmv
Used to store visitor-level custom variable data.
2 years
__utmz
Stores the traffic source or campaign that explains how the user reached your site.
6 months
LinkedIn is a professional networking platform for job seekers, employers, and industry connections.
Name
Description
Duration
fcookie
Used for bot detection.
7 days
AnalyticsSyncHistory
Used to store information about the time a sync with the lms_analytics cookie took place for users in the Designated Countries
30 days
ccookie
To remember if a user received a captcha challenge.
20 minutes
lissc
Pending
1 year
ABSELB
This is Load Balancer Cookie for affiliate marketing
2 years
spectroscopyId
These cookies are set by LinkedIn for advertising purposes, including: tracking visitors so that more relevant ads can be presented, allowing users to use the 'Apply with LinkedIn' or the 'Sign-in with LinkedIn' functions, collecting information about how visitors use the site, etc.
session
brwsr
This cookie is used to Affiliate Marketing Cookie for LinkedIn
2 years
UserMatchHistory
These cookies are set by LinkedIn for advertising purposes, including: tracking visitors so that more relevant ads can be presented, allowing users to use the 'Apply with LinkedIn' or the 'Sign-in with LinkedIn' functions, collecting information about how visitors use the site, etc.
session
lihc_auth_
Used by LinkedIn HelpCenter Live Chat to store language and chat start timestamp. Example names of this cookie include lihc_auth_en, lihc_auth_es, depending on language preference.
Session
lang
Used to remember a user's language setting
session
li_a
Used to authenticate enterprise users on Sales Navigator and Recruiter
30 days
li_gc
Used to store guest consent to the use of cookies for non-essential purposes
2 years
li_ep_auth_context
User to authenticate LinkedIn enterprise customers
30 days
li_rm
Used as part of the LinkedIn Remember Me feature and is set when a user clicks Remember Me on the device to make it easier for him or her to sign in to that device
1 year
bscookie
Used by LinkedIn to track the use of embedded services.
1 year
lms_ads
This cookie is used to identify LinkedIn Members off LinkedIn for advertising
30 days
trkCode
This cookie is used by LinkedIn to support the functionality of adding a panel invite labeled 'Follow Us'
1 year
_guid
This cookie is used to identify a LinkedIn Member for advertising through Google Ads
90 days
trkInfo
This cookie is used by LinkedIn to support the functionality of adding a panel invite labeled 'Follow Us'
1 year
BizographicsOptOut
This cookie is used to determine opt-out status for non-members
10 years
li_oatml
Collects information about how visitors use our site.
30 days
IRLD
This cookie is used for Affiliate Marketing Cookie for LinkedIn
2 years
liap
Cookie used for Sign-in with Linkedin and/or to allow for the Linkedin follow feature.
90 days
l_page
This cookie is used for measuring conversion metrics on LinkedIn
6 months
pushPermInfo
Used across multiple LinkedIn services to determine cool off for push notification prompts
365 days
pushPermState
Used across multiple LinkedIn services to determine the user's push notification permission preference
30 days
ln_or
Used to determine if Oribi analytics can be carried out on a specific domain
1 day
chp_token
Used to denote whether the user has gone through two factor authentication or solved a Captcha.
Session
li_sugr
Used to make a probabilistic match of a user's identity outside the Designated Countries
90 days
lidc
Used by the social networking service, LinkedIn, for tracking the use of embedded services.
1 day
sdsc
This cookie is used for signed data service context cookie used for database routing to ensure consistency across all databases when a change is made. Used to ensure that user-inputted content is immediately available to the submitting user upon submission
Session
bcookie
Used by LinkedIn to track the use of embedded services.
1 year
li_mc
This cookie is used as a temporary cache to avoid database lookups for a member's consent for use of non-essential cookies and used for having consent information on the client side to enforce consent on the client side
6 months
PLAY_FLASH
Used by some LinkedIn services to facilitate the display of messages on page transitions . Users include notifying a user when a form is successfully submitted or fails , and to provide other similar notifications.
Session
li_referer
Used to detect bots. Cookie remembers the referring website before redirecting the user to captcha for authorization
15 minutes
f_token
Used to detect bots for anti-scraping
3 minutes
li_apfcdc
Used for triggering the abuse prevention features on member device.
10 hours
li_odapfcc
Used to control the number of abuse prevention features collected from member device.
2 Years
ac_L
Counts the number of times the account center banner, which is displayed to inform users with an incomplete profile how to complete their profile, was closed by a user to determine display logic
180 days
ac_LD
Contains the date when the account center was displayed to a user to determine display logic
180 days
recent_history_status
Used to determine whether a user enabled or disabled the Guest Recent History Setting
10 years
all_u_b
To know if a user has opted in to viewing LinkedIn on an unsupported browser
21 days
uh
Used to set the user preference for the mobile web platform via a user's settings
Session
abiRedirect
Enables import of address book during onboarding flow for users who choose to import their address book
Session
wwepo
Used to ensure that useres who choose to sign up using phone only have that setting and preference respected
90 days
li_cu
Used to map a user to a captcha challenge page
15 minutes
li_ec
Used to store unbound enterprise users' cookie consent
6 months
denial-client-ip
Stores user IP address for anti-scraping and DOS prevention
5 seconds
li_gpc
Used to remember a user's preferences on LinkedIn's Global Privacy Control
1 hour
denial-reason-code
Used for anti-scraping and DOS prevention
5 seconds
li_gp
Stores privacy preferences for guests to LinkedIn
1 year
rtc
Used as part of anti-abuse processes on LinkedIn
120 seconds
redirectFromM2MInviteSent
Used to notify and provide the appropriate profile display logic when the user sends an invitation to connect on LinkedIn from a LinkedIn member via email.
Session
queryString
This cookie is used to persist marketing tracking parameters
15 days
cookie.policy.banner.eu
Used to display cookie banner in LinkedIn Lite
365 days
cookie.policy.banner.nl
Used to display cookie banner in LinkedIn Lite on the Netherlands site.
365 days
appName
Used to identify the source as the LinkedIn Lite app to send the right service worker to the app
Session
appLang
Used to set the right language on the LinkedIn Lite app
Session
lls-integration
Validates whitelisted partners for content integrations
30 days
feed-sort
Used to remember a member's preference how the feed should be sorted
1 day
integration_type
Used to determine which integration traffic is coming from to render the profile namecard experience
30 days
li_theme_set
Remembers which users have updated their display / theme preferences
6 months
PLAY_LANG
Used by some LinkedIn services to remember a user's language preference
Session
lms_analytics
Used to identify LinkedIn Members off LinkedIn for analytics
30 days
PLAY_SESSION
Used by some LinkedIn services to store session information
Session
li_fat_id
Member indirect identifier for Members for conversion tracking, retargeting, analytics
30 days
redirectFromM2MInviteAccept
Determines the appropriate profile display logic when a user accepts an invitation to connect on LinkedIn from a LinkedIn member via email.
Session
li_giant
Indirect indentifier for groups of LinkedIn Members used for conversion tracking
7 days
sharebox-suggestion
Displays a banner that provides help text to first time users of the Elevate share box
Session
li_cc
Used to ensure a user's phone number is inputted in China
1 week
lss_bundle_viewer
Stores consent when a user agrees to view a Smartlinks link
1 month
interstitial_page_reg_oauth_url
Stores the referring page to ensure the Authentication screen displays correctly
1 day
df_ts
Device fingerprinting sampling for performance optimization
1 day
lil-lang
Stores user's selected language setting for LinkedIn Learning
Session
li_alerts
Used to track impressions of LinkedIn alerts, such as the Cookie Banner and to implement cool off periods for display of alerts
1 year
li_theme
Remembers a user's display preference/theme setting
6 months
li_feed_xray
Used to show new items in developer option 'Feed X-ray'
Session
VID
ID associated with a visitor to a LinkedIn microsite which is used to determine conversions for lead gen purposes
1 year
recent_history
Used to remember URLs visited by the guest to show the pages back where they left off
90 days
Marketing cookies are used to follow visitors to websites. The intention is to show ads that are relevant and engaging to the individual user.
Name
Description
Duration
affwp_campaign
Stores the affiliate campaign name for tracking purposes.
30 days
affwp_ref
Stores the referring affiliate ID for commission attribution.
30 days
affwp_ref_visit_id
Stores the visit ID linked to the referring affiliate.
30 days
LinkedIn Insight is a web analytics service that tracks and reports website traffic.