Data Tracking

What Authority Documents are most commonly used in lists…..

…and in which industry?

This can help us

• identify target ADs to suggest for customers based on their company industry

• prioritize ADs to map when versions come out

• market ADs to specific clients

AD usage by company industry by AD release availability

1. of active accounts

2. Of demo accounts

….by paid customers and free customers?

This can help us

• prioritize ADs to map when versions come out

• market ADs to clients

• convert free to paid

AD usage by # of accounts w/lists by AD release availability

1. # of active accounts

2. # of demo accounts

….and how are customers using the lists?

This can help us identify what features to maintain and iterate on.

AD usage by # of lists by AD release availability

1. # of active lists

   1. # of published lists

   2. # of shared lists

   3. # of published and tracked lists

What Authority Documents are most commonly used in builds…..

…what build types are customers using and in which industry?

This can help us

• identify target ADs to suggest for customers based on their company industry

• prioritize ADs to map when versions come out

• market ADs to specific clients

• identify what features to maintain and iterate on.

AD usage by # of builds

1. by industry

2. by build type

…what build types are distinct customers using and in which industry?

This can help us

• identify target ADs to suggest for customers based on their company industry

• prioritize ADs to map when versions come out

• market ADs to specific clients

• identify what features to maintain and iterate on.

AD usage by # of accounts w/ builds

1. by industry

2. by build type

How often are customers creating lists?

This can help us identify what features to maintain and iterate on.

How often are customers updating lists?

This can help us identify what features to maintain and iterate on.

*need to be able to differentiate where modified date is different than creation date.

How often are customers creating builds?

This can help us identify what features to maintain and iterate on.

How often are customers creating compare builds?

This can help us identify what features to maintain and iterate on.

*need to be able to differentiate where modified date is different than creation date.

What’s the average number of Authority documents per list?

This can help us identify how many ADs to target for suggested lists.

*Hubspot may have a limitation with averages, due AD counts derived from a string and not a number value.

What’s the average number of lists per account?

This can help us identify what features to maintain and iterate on.

*Hubspot may have a limitation with averages, due List counts derived from a string and not a number value.

What’s the average number of builds per account?

This can help us identify what features to maintain and iterate on.

*Hubspot may have a limitation with averages, due AD counts derived from a string and not a number value.

How many days after an account is created is a list created?

How many days after an account is paid is a list created?

How many days after an account is paid is a build created?

ch_accounts.Account_Status

1. active = Paid

2. demo = Free

3. frozen = Payment overdue

4. deleted = Deleted

5. merged = Merged

6. po-create = PO-created, not paid

Indicates who has paid us, who hasn’t, who owes us, etc.

Can help onboarding, retention, etc.

authority_documents.AD_live_status

1. 1 = Live

2. 0 = Deprecated

Indicates what ADs are live.

Can help filter AD, List, Build usage.

May only care about Live ADs.

authority_documents.AD_Release_availability

1. For Subscribers = available for paid accounts

2. Private = available to owning CCH account (client mapped or mapping services)

3. Free = available to all cch accounts

4. For purchase = available for an additional fee (only a handful exist and only 1 has sold a few copies - payments handled outside the CCH system)

5. Null = Not Mapped OR Legacy document (mapped before release availability types existed)

*Keep DB Value in Hubspot, i.e. (For Subscribers, etc.)

Indicates who has access to use the AD mapping in the current CCH.

Can help filter AD, List, Build usage.

authority_documents.AD_status

1. Released = available in CCH

2. Restricted = available in the CCH to limited accounts
   ------ values we may not need to track----

3. Redacted = deprecated (NOT available in CCH)

4. In Edit = in mapping, in a Mapper Tool project (NOT available in CCH)

5. Re-Queued = needs to be mapped (NOT available in CCH)

6. Recommended = cataloged, not mapped (NOT available in CCH)

7. Not Applicable = will not map
   ---possible legacy values----

8. On Hold = needs to be mapped (NOT available in CCH)

9. In Review = in mapping, (NOT available in CCH)

10. Queued = Mapping Project

*Keep DB Value in Hubspot, i.e. (Released, etc.)

Indicates if the AD is available in the CCH.

Can help filter AD, List, Build usage.

May only care about Released, Restricted ADs.

ch_authdoc_list.list_active_status

1. A = Active

2. D = Deleted

3. R = Archived

Indicates if the list is current or not.

ch_build_archive.build_type

1. xlsdoc = has additional compliance docs add on

2. xls = regular build

3. xlsdoc+ = has implementation controls & additional compliance docs, etc. addon

4. xls+ = has implementation controls