Before creating a support ticket, fill in the following table for Form Data issues:
|Exercise||Successfully Verified Exercise?||Problem Encountered on Step(s) #?|
|Provide Form URL (Required)|
|Can You Trigger Identification Before Submission for the Same Company in Question?|
|Is the Form Submitting the Data?||Provide screenshot|
|What is the Identification Rate /Match-Rate?||If nothing alarming comes up and you'd like to run a match with us, submit this data to your CSM.|
|API Priority - Understanding Company Data vs. User Data|
|Identify Your Current API Priority||Note API priority here and changes, if any.|
Submitting a Support Ticket
Copy and paste the completed table into the Support ticket. Note that without a completed table, resolution to your ticket and response may be delayed. If an Exercise doesn't apply to you, leave it blank.
Can You Trigger Identification Before Submission for the Same Company in Question?
Often you can trigger the same company on your own form by doing a simple exercise to prove your integration is working:
- Go to the Form page you normally collect data from.
- Fill out the fields as you normally would EXCEPT for email use the company you are troubleshooting. For example instead of your own email, type email@example.com.
- This should populate your hidden fields with asdf company data. To verify, open the console.
- Visit the site with the script:
Open the console (Command Option J) or right-click and choose Inspect Element, and then click Console.
- In the console type: Demandbase.Connectors.WebForm.CompanyProfile
- Click the icon before the Object to expand. Observe the asdf company has been identified.
- Now that you've identified the same company data is available PRIOR to a submission, you must follow this guide to verify that company data is actually sent to you at the time of submission. See Is the Form Submitting Data for more information.
- If you followed all the steps above successfully most likely you're experiencing an end user problem. Your firstname.lastname@example.org is probably using an ad-blocker which can prevent Demandbase from running. Complete the above table and open a Support ticket to check it for you.
What is the Identification Rate/Match-Rate?
Demandbase doesn't really have a match-rate. The idea that we match at a certain rate is a bit misleading because the QUANTITY of Demandbase data identifying your leads is as good as the QUALITY of data given to Demandbase. Quality leads provide company data in some form or fashion because they want to be contacted and are genuinely interested in the subject. The opposite is true for leads that provide little to nothing about themselves in which case we can't really call them a lead.
So before we go down the rabbit hole of data discrepancy let's talk some numbers:
- How many forms is Demandbase deployed on? In order to understand the breadth of the issue we need to look at deployment. Is it possible for example that 2 forms on separate pages are identical because of their master templates but one doesn't have Demandbase on it? This can skew your data.
- Observing a Demandbase-Enabled Form:
- What are your total form submissions regardless of Demandbase matching?
- Of total from #1, identify the submissions that had a valid COMPANY email address.
- Of total from #1, identify the submissions that had a Demandbase match, typically filter submissions that had a Demandbase SID or Marketing_Alias field.
- Does #2 & #3 come close? By How much?
- The difference between 2 & 3 can vary for example when you have a lot of SMB companies filling your forms we won't identify as many as we'd like due to the nature of SMB's changing structure frequently.
- You've now identified a percentage of your submissions matched by Demandbase based on the quality of data provided through the company emails or company IP's. Submit this data along with your form submission data to your CSM and they can run an internal match to light up any dark spots you may have missed.
API Priority - Understanding Company Data vs. User Data
Depending on the API priority configuration you will receive different kinds of data on form submissions. Sometimes a user enters a company that is different than the automatic identification that Demandbase performs. This is not totally unexpected because API priority dictates which data set to use at the time of submission.
As explained in Understanding Forms Visitor Identification, Demandbase returns firmographic information using three APIs: IP, Domain, and Company Autocomplete.
However, the Company Profile that Demandbase returns to the Form Connector will choose only one of the API return values. The Company Profile value is determined by the Form Connector's API priority order.
The default API priority order is Domain API -> IP API -> Company Autocomplete API. This means that if all three APIs identify the visitor, the Demandbase Forms Connector will use the information returned by the Domain API. Likewise, if the IP API and Company Autocomplete APIs return data, but the Domain API does not, the Forms Connector will use the information returned by the IP API.
Identify your current API Priority
- Browse to a Demandbase-Enabled form on your site.
- The Demandbase Form should've attached to the form. Open the console by Right Click, Inspect Element and select the Console tab.
- In the Console Type
Observe the Priority Map as demonstrated below and take note of it. 3 is the HIGHEST and 1 is the LOWEST which means Domain will override IP data in the form below.