November is a milestone month for RampedUp, we are happy to report we have grown key B2C fields like mobile_phone and contact_personal_email_address to record highs. We are also introducing two new fields for our B2C clients:
- volunteering: These are the causes important to the contact.
- contact_instagram_url: While not largely populated, this field has been requested on numerous occasions for a growing median.
November's Data Dictionary with Counts
In an effort to keep our B2B contact data as accurate as possible, we will no longer populate job_title, job_start_date, company_hq_name, and company_hq_ru_id IF the last updated date is older than 12 months. This data is still available, but in the contact_experience array, with the job_end_date marked as UNKNOWN. We have already received favorable feedback from test cases in terms of quality without impacting expectations for volume.
That is why we thought it was a good time to introduce this QA step. As of October, over 85 percent of our database falls within the 12-month update window. We updated 251,224,704 this month alone! But more importantly, the records falling outside of this window do so because they have not shown any activity to be picked up by our social media or domain scanners. That means we haven't seen their profile on a corporate website or social media for over a year.
As such, we are introducing a field showing that last time we saw a web-based signal called contact_last_updated_from_web. Unlike the contact_last_updated, This field does not incorporate the contact_professional_email_validation_status_date for VALID responses.
This step is consistent with earlier QA fields we introduced, namely contact_active_ru_id. If you recall, when the contact_active_ru_id does not equal the contact_ru_id, then we have identified this record as duplicate. As such, we have rolled all the pertinent information to the active record, with the exception of the LinkedIn URL. In the very near future, we plan on consolidating that field in an array under one RUID as well.
In the same spirit of Quality Assurance, we are also introducing the contact_memorialized_date field. While small in volume, it does respect the wishes of those that have asked that this record be identified as such.