CRM Field Setup
How to structure your CRM to receive and activate Grizz data.
Naming Convention
All Grizz fields should be created with a Grizz_ prefix on the API name and a Grizz prefix on the UI label. This makes it immediately clear which fields are Grizz-sourced, prevents naming collisions with native CRM fields, and makes list views and reports easier to filter.
API / Field Name
Grizz_LinkedIn_URL
Used in automations, workflows, and integrations
UI Label
Grizz LinkedIn URL
Displayed to CRM users on the record layout
Recommended Fields
Create the following custom fields on the Company / Account object. All fields should be read-only for end users — Grizz data is written by your import or integration process, not manually.
| UI Label | API / Field Name | Type | CSV Column | Description |
|---|---|---|---|---|
| Company Identity | ||||
| Grizz Company ID | Grizz_Company_ID | Text | company_id | Grizz's internal company identifier — useful for deduplication and re-enrichment |
| Grizz Company Name | Grizz_Company_Name | Text | company_name | Company name as normalised by Grizz |
| Grizz Domain | Grizz_Domain | Text | domain | Primary web domain (without protocol) |
| Grizz LinkedIn URL | Grizz_LinkedIn_URL | URL | linkedin_url | LinkedIn company page URL |
| Grizz Profile URL | Grizz_Profile_URL | URL | grizz_url | Direct link to the company's profile in the Grizz platform |
| Contact & Location | ||||
| Grizz HQ Phone | Grizz_HQ_Phone | Phone | hq_phone | HQ main phone number |
| Grizz HQ Email | Grizz_HQ_Email | hq_email | HQ general email address | |
| Grizz HQ City | Grizz_HQ_City | Text | hq_city | HQ city |
| Grizz HQ State / Region | Grizz_HQ_Region | Text | hq_region | HQ state or region |
| Grizz HQ Country | Grizz_HQ_Country | Text | hq_country | HQ country |
| Firmographics | ||||
| Grizz Employee Range | Grizz_Employee_Range | Text | employee_range | Headcount band (e.g. 50-200) |
| Grizz Revenue Range | Grizz_Revenue_Range | Text | revenue_range | Estimated annual revenue band |
| Grizz Activity | Grizz_Activity | Text Area | grizz_activity | Grizz-generated description of the company's business activity |
| Grizz NAICS | Grizz_NAICS | Text | naics | NAICS 6-digit industry code(s) |
| ERP Intelligence | ||||
| Grizz ERP | Grizz_ERP | Text | erp_tech_stack | Detected ERP software name |
| Grizz ERP Confidence optional | Grizz_ERP_Confidence | Text | erp_confidence | Signal confidence tier: A (ultra), B (high), or C (limited) |
| Grizz ERP Job Title optional | Grizz_ERP_Job_Title | Text | erp_job_title | Title of the job posting that confirmed the ERP signal |
| Grizz ERP Keyword Usage optional | Grizz_ERP_Keyword_Usage | Text Area | erp_keyword_usage | Exact text excerpt from the job posting that mentioned the ERP |
| ATS Intelligence | ||||
| Grizz ATS | Grizz_ATS | Text | ats_tech_stack | Detected ATS software name |
| Grizz ATS Confidence optional | Grizz_ATS_Confidence | Text | ats_confidence | Signal confidence tier: A (ultra), B (high), or C (limited) |
| Grizz ATS Job Title optional | Grizz_ATS_Job_Title | Text | ats_job_title | Title of the job posting that confirmed the ATS signal |
| Grizz ATS Keyword Usage optional | Grizz_ATS_Keyword_Usage | Text Area | ats_keyword_usage | Exact text excerpt from the job posting that mentioned the ATS |
| Other Technology Signals | ||||
| Grizz Other Tech Signals | Grizz_Other_Tech_Signals | Text Area | other_tech_signals | Comma-separated list of other confirmed software signals |
CRM Automation Recommendations
Some Grizz fields have direct equivalents in native CRM fields — for example, Grizz_LinkedIn_URL
and the native LinkedIn URL field.
Grizz recommends building CRM-native automation to merge this data into those primary fields.
The right strategy depends on how mature your CRM data is.
For mature CRMs
Enrichment Mode
Native fields already have good data. Use Grizz to fill gaps only.
THEN set [LinkedIn URL] = [Grizz LinkedIn URL]
For early-stage CRMs
Override Mode
Native fields are sparse or unreliable. Always write Grizz data to primary fields.
(when Grizz value is not blank)
Field-by-Field Automation Guide
| Grizz Field | Native CRM Field | Enrichment Mode Rule | Override Mode Rule |
|---|---|---|---|
| Grizz_Company_Name | Account Name / Company Name | If blank, set from Grizz | Always set from Grizz if not blank |
| Grizz_Domain | Website / Domain | If blank, set from Grizz | Always set from Grizz if not blank |
| Grizz_LinkedIn_URL | LinkedIn URL | If blank, set from Grizz | Always set from Grizz if not blank |
| Grizz_HQ_Phone | Phone | If blank, set from Grizz | Always set from Grizz if not blank |
| Grizz_HQ_City | City / Billing City | If blank, set from Grizz | Always set from Grizz if not blank |
| Grizz_HQ_Region | State / Billing State | If blank, set from Grizz | Always set from Grizz if not blank |
| Grizz_HQ_Country | Country / Billing Country | If blank, set from Grizz | Always set from Grizz if not blank |
| Grizz_Employee_Range | Number of Employees | If blank, set from Grizz | Always set from Grizz if not blank |
| Grizz_Revenue_Range | Annual Revenue | If blank, set from Grizz | Always set from Grizz if not blank |
| Grizz_ERP | ERP System (custom field) | If blank, set from Grizz | Always set from Grizz if not blank |
| Grizz_ATS | ATS System (custom field) | If blank, set from Grizz | Always set from Grizz if not blank |
Update Cadence
Grizz data is refreshed continuously as new job signals are processed. We recommend re-importing
or re-running your Grizz audiences on a monthly cadence to
keep tech stack and firmographic data current. When re-importing, match records to your CRM by
Grizz_Company_ID or
Grizz_Domain to avoid creating duplicate accounts.