Lolly Apprentice Update

A153C3FD-6006-49B9-958E-3292D3F34C83-980×551

With this week being National Apprenticeship Week, we wanted to catch up with our apprentices, new and old, to see how they are faring in their apprenticeship, or in their permanent role at Lolly.

Daniel Burton

Daniel began his apprenticeship in 2016, and since his graduation has become an integral part of the Lolly team in his role as App Developer.

“After starting out at Lolly doing an apprenticeship, I have been given the support and resources to progress my skills and become an App Developer. Although I am involved in a lot of things in Lolly, my main focus is adding to and improving the Lolly App with things such as In Venue ordering and Desk Delivery.”

Tyler McCrory

Since his graduation from the apprenticeship scheme in 2018, Tyler has been developing his skills even further at Lolly as an IT Support Technician.

“The times are very strange right now for everyone, but working at It’s Lolly has been exciting and kept my mind busy throughout the pandemic. I have been interested in the Level 4 Network Engineer course which would boost my position and help me master skill sets within the IT sector. I personally feel like I have improved considerably throughout the year and hope to continue this for 2021!”

Alex Patey

Alex started his apprenticeship in 2020 and is due to graduate his apprenticeship next year.

“My apprenticeship has been progressing very well, I have learned a great deal of new skills and developed my ability to program greatly. At the moment I am working on a website project, where I am required to use the full breadth of my knowledge, from front end UI design and implementation, to data handling on the back end. I have had a great experience with Its Lolly and hope to continue to work for them in the future.”

Daniel Fletcher

Daniel joined Lolly on the apprenticeship scheme in December 2020.

“I’ve always been interested in computing. However, having taken a computing course at college that wasn’t very inspiring and was more focused on coding and structured education, I was keen to find something that would allow me to study in a more practical, independent manner. The Lolly apprenticeship offered that and I think it will be a valuable qualification for the future.

The work is engaging, the team are all really nice and I feel as though I’ve found the right place for me.”

← Previous Next →

FUNCTION PROVIDER	COOKIE NAME	DATA STORED	PURPOSE	DURATION
itslolly.com	_grecaptcha	Works by creating a unique id (UID) for each visitor and stores variables based on this UID.	To Distinguish between human visitors and bots	Persistent
	moove_gdpr_popup		Cookie set by the UK cookie consent plugin to record that you accept the fact that the site uses cookies.
	olfsk	Works by creating a unique id (UID) for each visitor and stores variables based on this UID.	Th is cookie is necessary for the login function on the web site.	2 Years
	hblid	Works by creating a unique id (UID) for each visitor and stores variables based on this UID.	Identifies the visitor across devices and visits, in order to optimize the chat-box function	2 years
	wcsid	Works by creating a unique id (UID) for each session and stores variables based on this UID.	A session identifier to keep track of a single chat session	Session
	_ok _okbk _okcs _okdetect _oklv	Works by creating a unique id (UID) for each visitor and stores variables based on this UID.	Identifies the visitor across devices and visits, in order to optimize the chat-box function	Session
	_okck	Works by creating a unique id (UID) for each visitor and stores variables based on this UID.	Identifies the visitor across devices and visits, in order to optimize the chat-box function	1 day
	_okdetect	Works by creating a unique id (UID) for each visitor and stores variables based on this UID.	Identifies the visitor across devices and visits, in order to optimize the chat-box function	Persistent
google.com	_GRECAPTCHA rc::d-#	Works by creating a unique id (UID) for each visitor and stores variables based on this UID.	To Distinguish between human visitors and bots	Persistent
	rc::a rc::b rc::c	Works by creating a unique id (UID) for each visitor and stores variables based on this UID.	To Distinguish between human visitors and bots	Session
doubleclick.net	test_cookie	Works by creating a unique id (UID) for each visitor and stores variables based on this UID.	To check if the user's browser supports cookies	1 Day

Host	COOKIE NAME	Purpose	DURATION
itslolly.com	_dc_gtm_UA-#	Used by Google Tag Manager to control the loading of a Google Analytics script tag.	1 day
itslolly.com	_ga	Registers a unique ID that is used to generate statistical data on how the visitor uses the website.	2 Years
itslolly.com	_ga_#	Registers a unique ID that is used to generate statistical data on how the visitor uses the website.	2 Years
itslolly.com	_gid	Registers a unique ID that is used to generate statistical data on how the visitor uses the website.	1 day
itslolly.com	collect	Used to send data to Google Analytics about the visitor’s device and behavior. Tracks the visitor across devices and marketing channels.	Session

Host	COOKIE NAME	Purpose	DURATION
itslolly.com	_hjAbsoluteSessionInProgress	The cookie is set so Hotjar can track the beginning of the user's journey for a total session count. It does not contain any identifiable information.	1 day
itslolly.com	_hjFirstSeen	This cookie is used to determine if the visitor has visited the website before, or if it is a new visitor on the website.	1 day
itslolly.com	_hjid	This cookie is set when the customer first lands on a page with the Hotjar script. It is used to persist the Hotjar User ID, unique to that site on the browser. This ensures that behavior in subsequent visits to the same site will be attributed to the same user ID.	Persistent
itslolly.com	_hjIncludedInPageviewSample	his session cookie is set to let Hotjar know whether that visitor is included in the sample which is used to generate funnels.	1 day
itslolly.com	_hjTLDTest	When the Hotjar script executes we try to determine the most generic cookie path we should use, instead of the page hostname. This is done so that cookies can be shared across subdomains (where applicable). To determine this, we try to store the _hjTLDTest cookie for different URL substring alternatives until it fails. After this check, the cookie is removed.	Session

Host	COOKIE NAME	PURPOSE	DURATION
itslolly.com	_gcl_au	Used by Google AdSense for experimenting with advertisement efficiency	3 months
itslolly.com	_uetsid	Collects data on visitor behaviour from multiple websites, in order to present more relevant advertisements	Persistent
itslolly.com	_uetsid_exp	Contains the expiry-date for the cookie with the corresponding name	Persistent
itslolly.com	_uetvid	Collects data on visitor behaviour from multiple websites, in order to present more relevant advertisements	Persistent
itslolly.com	_uetvid_exp	Contains the expiry-date for the cookie with the corresponding name	Persistent

google.com	ads/ga-audiences	Used by Google AdWords to re-engage visitors that are likely to convert based on the visitor's online behaviour across websites.	Session
google.com	pagead/1p-user-list/#	Used for measurement of advertisement efforts and facilitates payment of referral-fees between websites	Session

bing.com	MUID	Enables user tracking across Microsoft domains	1 year