DCC vs LQE Reports in ELM

321 GANG CUSTOMER STATISTIC

15 organizations rated 321Gang and their ability to support your IBM Rational Engineering solutions as 4.5 out of 5 stars on average.

Learn how these two data sources (DCC and LQE) works and when to use them. DCC / Data Warehouse is more geared towards traditional reporting as LQE as a near real time report capability such as cross-tool traceability, Linked artifact views, Configuration enabled projects.

Learn to create a several reports using Report Builder using different data sources. Learn how graphs are used to help visualize data.

Company
This field is for validation purposes and should be left unchanged.
Packaged Service*
Contact Name*
First Last
Company Name*
Company Email*
Phone*
State*
Select Subject Area*
Subject Line:
Comments? Questions?
reCAPTCHA

See what 321Gang can do for your business

Request a Demo

Privacy Overview

This website uses cookies to improve your experience while you navigate through the website. Out of these, the cookies that are categorized as necessary are stored on your browser as they are essential for the working of basic functionalities of the website. We also use third-party cookies that help us analyze and understand how you use this website. These cookies will be stored in your browser only with your consent. You also have the option to opt-out of these cookies. But opting out of some of these cookies may affect your browsing experience.

Necessary

Always Enabled

Necessary cookies are absolutely essential for the website to function properly. This category only includes cookies that ensures basic functionalities and security features of the website. These cookies do not store any personal information.

Cookie	Duration	Description
cookielawinfo-checkbox-advertisement	1 year	Records consent for the Advertisement cookie category. Provider: 321gang.com.
cookielawinfo-checkbox-analytics	1 year	Records consent for the Analytics cookie category. Provider: 321gang.com.
cookielawinfo-checkbox-functional	1 year	Records consent for the Functional cookie category. Provider: 321gang.com.
cookielawinfo-checkbox-necessary	1 year	Records consent for the Necessary cookie category. Provider: 321gang.com.
cookielawinfo-checkbox-others	1 year	Records consent for the Others cookie category. Provider: 321gang.com.
cookielawinfo-checkbox-performance	1 year	Records consent for the Performance cookie category. Provider: 321gang.com.
CookieLawInfoConsent	1 year	Stores the visitor full consent record, including which categories were allowed and the version of the notice they saw. Provider: 321gang.com.
PHPSESSID	session	Preserves the visitor session state across page requests. Set by PHP and required for the site to function. Provider: 321gang.com.
swpm_session	session	Maintains the logged in session for members using the Simple Membership area. Provider: 321gang.com.
viewed_cookie_policy	1 year	Records whether the visitor has responded to the cookie banner, so it is not shown again on every page. Provider: 321gang.com.

Functional

Functional cookies help to perform certain functionalities like sharing the content of the website on social media platforms, collect feedbacks, and other third-party features.

Cookie	Duration	Description
aiovg_rand_seed	1 day	Keeps the randomised ordering of the video gallery consistent while the visitor browses. Provider: 321gang.com.

Performance

Analytics

Analytical cookies are used to understand how visitors interact with the website. These cookies help provide information on metrics the number of visitors, bounce rate, traffic source, etc.

Cookie	Duration	Description
_ga	13 months	Assigns a randomly generated identifier so returning visitors can be counted without being named. Provider: Google Analytics.
_ga_1CNDNQ9P24	13 months	Stores the session state for a second Google Analytics 4 property, configured inside the Google Tag Manager container. Provider: Google Analytics.
_ga_Z9DJMTP0SM	13 months	Stores the session state for this specific Google Analytics 4 property. Provider: Google Analytics.
_gat_gtag_UA_116926200_1	1 minute	Limits how often data is sent to Google Analytics on busy pages. Provider: Google Analytics.
_gid	1 day	Assigns a short lived identifier used to count and track pageviews within a single day. Provider: Google Analytics.

Advertisement cookies are used to provide visitors with relevant ads and marketing campaigns. These cookies track visitors across websites and collect information to provide customized ads.

Cookie	Duration	Description
__adroll	13 months	Stores the AdRoll advertising identifier used for retargeting. Provider: AdRoll.
__adroll_shared	13 months	Shares the AdRoll advertising identifier between AdRoll and its partner networks. Provider: AdRoll.
__ar_v4	1 year	Identifies the visitor to AdRoll so that 321Gang adverts can be shown to them on other websites. Provider: AdRoll.
__hssc	30 minutes	Tracks the current HubSpot session, including how many pages have been viewed. Provider: HubSpot.
__hssrc	Session	Records whether the visitor has restarted their browser, used by HubSpot to decide if a new session has begun. Provider: HubSpot.
__hstc	6 months	Records the visitor identifier, the first visit, the last visit and the current visit for HubSpot analytics. Provider: HubSpot.
_gcl_au	3 months	Used by the Google Ads conversion linker to attribute a later enquiry back to the advert that brought the visitor to the site. Provider: Google Ads.
_lfa	1 year	Assigns a persistent identifier used to work out which company a visitor belongs to, for sales and marketing follow up. Provider: Leadfeeder.
csync	1 month	Records which advertising partners the visitor identifier has been synchronised with. Provider: Smart AdServer.
hubspotutk	6 months	Identifies the visitor to HubSpot so their browsing can be linked to a contact record in the marketing database. Provider: HubSpot.
IDE	13 months	Builds a profile of the visitor across websites in order to select and measure adverts. Provider: Google DoubleClick.
mako_uid	1 year	Assigns an identifier used to add the visitor to marketing audience segments. Provider: Eyeota.
pi	1 year	Assigns an identifier used to build business intent data about the visitor organisation. Provider: Bombora (ml314).
pid	3 months	Assigns an advertising identifier used to select and measure adverts. Provider: Smart AdServer.
receive-cookie-deprecation	13 months	Records whether the browser is part of Google phased removal of third party cookies, so AdRoll can adapt its tracking method. Provider: AdRoll.
SERVERID	session	Records which Eyeota server handled the request, used during audience synchronisation. Provider: Eyeota.
TapAd_3WAY_SYNCS	2 months	Tracks which partner networks the visitor identity has already been shared with. Provider: Tapad.
TapAd_DID	2 months	Identifies the visitor device so advertising can be matched across the phones, tablets and computers they use. Provider: Tapad.
TapAd_TS	2 months	Records the time of the last cross device identity synchronisation. Provider: Tapad.
TDCPM	1 year	Stores advertising campaign data associated with the visitor. Provider: The Trade Desk.
TDID	1 year	Cross site advertising identifier, set when AdRoll synchronises audiences with The Trade Desk. Provider: The Trade Desk.
test_cookie	15 minutes	Checks whether the browser will accept advertising cookies before any are set. Provider: Google DoubleClick.
TestIfCookieP	13 months	Checks whether the browser will accept advertising cookies. Provider: Smart AdServer.
u	session	Temporary identifier used while synchronising business intent data. Provider: Bombora (ml314).
uuid2	3 months	Assigns a unique advertising identifier used to select adverts across websites. Provider: Xandr.
XANDR_PANID	3 months	Stores an advertising identifier used for audience targeting. Provider: Xandr.

Others

DCC vs LQE Reports in ELM

321 GANG CUSTOMER STATISTIC

See what 321Gang can do for your business

Products

Be Social