Marketing Sources in Mav
A Marketing Source is the doorway a lead vendor posts through to reach Mav. This is what one is, how a posted lead becomes a conversation, and every field Mav will accept - separately for auto and home playbooks.
What are Marketing Sources?
A Marketing Source pairs a lead vendor with a playbook and gives you a unique posting URL. Your vendor sends each new lead to that URL as an HTTP POST, and Mav starts the paired playbook on that lead within seconds.
Because the URL identifies both the vendor and the playbook, you create one Marketing Source per combination. Two vendors feeding the same auto playbook means two sources; one vendor feeding both an auto and a home playbook also means two sources. That is what makes per-source reporting possible - every lead arrives already tagged with where it came from.
One vendor, one playbook, one URL
Two ways to create one
- From the directory. Pick a known vendor from Mav's lead source directory, choose the playbook, and the source is named and wired for you. Mav stamps the source and sub-source on every lead automatically, so attribution is consistent and cannot be overwritten by the vendor.
- As a custom source. For a vendor not in the directory, your own landing pages, or a partner feed. You name it yourself, and the vendor may pass its own tracking fields —
source,sub_source,sub_id, and the rest of the tracking set — to describe traffic at a finer grain than the source name alone.
How it works
-
Go to Integrations > Marketing Sources
-
Select your source from the directory and click “Integrate”
- If your source isn’t listed in the directory, select “My Sources” and choose “New Marketing Source.” Then follow the steps listed below. Be sure to give your source a clear distinctive name.
- Select the playbook (Home or Auto) where you want to send your leads and click Save & View Instructions
-
You’ll be provided with a postingURL and lead parameters. You can also opt to email the instructions to yourself or a team member.
-
Send leads to that URL via form or JSON
-
Mav tracks the source automatically and kicks off the follow-up
FIND YOUR POSTING URL
Open Integrations → Marketing Sources → My Sources and click Integration Instructions on the source. The panel shows the posting URL, the exact field list for that source, and a sample request — and the Email Instructions button sends all of it to your vendor in one message.
How to send leads to Mav
Once you have a postURL, leads can be sent in one of two formats:
-
Form Submission (URL-encoded)
- Send a form submission (like from a website form) using POST to the provided URL. Include fields like:
first_name=Jane&last_name=Doe&phone=1234567890&email=jane@example.com
- Send a form submission (like from a website form) using POST to the provided URL. Include fields like:
-
JSON format
-
You can also send leads in JSON format:
curl -X POST "https://hiremav.com/marketing_sources/acc_2SbUe8xLqEqrL3/mks_kgaafDRBWshCzp" \-H "Content-Type: application/json" \-d '{"first_name": "John","last_name": "Doe","email": "john.doe@example.com","phone": "5551234567",...}'Each postURL can accept either format, and Mav will automatically associate the lead with the correct Marketing Source.
-
Auto and Home accept different fields
The field list is not one universal set. It is chosen by the type of the playbook attached to the source. A home playbook accepts the home list; every other playbook accepts the auto list.
Anything not on the list for that source is dropped. The lead is still created — the post succeeds, no error is returned — but the unrecognized fields never reach the lead record. A vendor sending its auto payload to a home source will look perfectly integrated while the home data quietly disappears.
The same fact, a different name
Several fields exist in both lists under different names. These are the ones worth checking field by field, because the value looks right and lands nowhere.
| THE FACT | AUTO PLAYBOOK | HOME PLAYBOOK |
|---|---|---|
| Date of birth | date_of_birth | dob |
| Credit tier | credit_rating | credit |
| Current carrier | current_insurance_carrier | current_insurance_company |
| Insured since | current_insurance_since | insured_since |
| Policy expiration | driver_1_policy_expiration_date | policy_expiration |
| Consent identifier | tcpa_opt_in_token | leadid_token |
| Consent proof | tcpa_opt_in_url | trusted_form_url |
| Consent record | tcpa_language | tcpa_consent |
| Currently insured | driver_1_insured_past_30_days | currently_insured |
| Traffic source | custom sources only, as source |
src |
| Landing page | custom sources only | landing_page |
What only one side has
- Auto only. Every driver and vehicle field, plus
marital_statusanduser_agent. A home source will not keep a single vehicle or driver field. - Home only. Every property field — roof, stories, square footage, construction, heating, security — plus
primary_phoneandorigin_phone. An auto source will not keep any of them.
Auto Playbook Fields
The four core fields are required on every post. Everything else is optional — and everything else is worth sending. Each field you include is one less question your agent has to ask before it can quote, and one more thing your rep sees the moment a call transfers.
| FIELD | WHAT IT IS |
|---|---|
| CORE — REQUIRED | |
| first_name | The lead's given name.REQUIRED |
| last_name | The lead's family name.REQUIRED |
| The lead's email address.REQUIRED | |
| phone | The lead's phone number. Must be a valid US mobile number.REQUIRED |
| RESIDENCE — EITHER SPELLING IS ACCEPTED | |
| address | Street address. Also accepted as current_residence_address. |
| city | City. Also accepted as current_residence_city. |
| state | State. Also accepted as current_residence_state. |
| zip | ZIP code. Also accepted as current_residence_zip. |
| APPLICANT | |
| date_of_birth | Full date of birth, used for quoting and verification. |
| gender | The lead's gender. |
| marital_status | Single, married, divorced, and so on. |
| credit_rating | Self-reported credit tier — excellent, good, fair, poor. |
| CURRENT COVERAGE | |
| current_insurance_carrier | The company providing the current policy. |
| current_insurance_coverage | The type of coverage currently held. |
| current_insurance_since | How long the lead has been continuously covered. |
| CONSENT AND SESSION | |
| tcpa_opt_in_token | Consent token — a Jornaya or ActiveProspect identifier. |
| tcpa_opt_in_url | Link to the consent proof, often a session recording. |
| tcpa_language | The full disclosure text the lead was shown. |
| ip_address | The lead's IP at the time of submission. |
| user_agent | Browser and device user agent string. |
| device_type | Device used — mobile, desktop, tablet. |
| CALL ROUTING | |
| did | The number Mav should transfer this lead's call into, overriding the source's default. |
| FIELD | WHAT IT IS |
|---|---|
| IDENTITY — PER VEHICLE, BOTH SPELLINGS ACCEPTED | |
| vehicle_1_make | Make. Also accepted as 1st_vehicle_make. |
| vehicle_1_model | Model. Also accepted as 1st_vehicle_model. |
| vehicle_1_year | Year. Also accepted as 1st_vehicle_year. |
| vehicle_1_vin | VIN. Also accepted as 1st_vehicle_vin. |
| vehicle_2_make | Second vehicle. Also 2nd_vehicle_make — and the same for model, year, and VIN. |
| vehicle_3_make | Third vehicle. Also 3rd_vehicle_make — and the same for model, year, and VIN. |
| USAGE AND COVERAGE — VEHICLES 1 AND 2 ONLY | |
| vehicle_1_sub_model | Sub-model or trim. |
| vehicle_1_ownership | Owned, leased, or financed. |
| vehicle_1_primary_use | Commute, pleasure, business. |
| vehicle_1_average_one_way_mileage | Average one-way commute distance. |
| vehicle_1_annual_mileage | Miles driven per year. |
| vehicle_1_average_days_per_week_used | Days per week the vehicle is driven. |
| vehicle_1_security_system | Anti-theft or security system type. |
| vehicle_1_parking | Where the vehicle is usually parked. |
| vehicle_1_desired_collision_coverage | Desired collision deductible. |
| vehicle_1_desired_comprehensive_coverage | Desired comprehensive deductible. |
| vehicle_2_… | Every field above repeats for the second vehicle, plus vehicle_2_coverage_type. |
Primary driver
| FIELD | WHAT IT IS |
|---|---|
| PROFILE | |
| driver_1_age | Current age. |
| driver_1_birthdate | Date of birth. |
| driver_1_gender | Gender. |
| driver_1_marital_status | Marital status. |
| driver_1_credit_rating | Credit tier. |
| driver_1_education | Education level. |
| driver_1_occupation | Occupation. |
| LICENSE | |
| driver_1_license_status | Valid, permit, suspended, foreign. |
| driver_1_licensed_state | State that issued the license. |
| driver_1_age_when_first_licensed | Age at first licensing. |
| driver_1_suspended_or_revoked_in_the_past_5_years | Suspension or revocation history. |
| driver_1_filing_required | Whether an SR-22 or similar filing is required. |
| RESIDENCE | |
| driver_1_current_residence | Own or rent. |
| driver_1_years_at_current_residence | Years at the address. |
| driver_1_months_at_current_residence | Additional months at the address. |
| INSURANCE HISTORY | |
| driver_1_insured_past_30_days | Whether insured within the last 30 days. |
| driver_1_insurance_company | Current insurer. |
| driver_1_insured_since | Date continuous coverage began. |
| driver_1_policy_expiration_date | When the current policy expires. |
| driver_1_current_insurance_company_years | Years with the current insurer. |
| driver_1_current_insurance_company_months | Additional months with the current insurer. |
| driver_1_continuously_insured_years | Years continuously insured. |
| driver_1_continuously_insured_months | Additional months continuously insured. |
| RISK HISTORY | |
| driver_1_tickets_accidents_claims_past_3_years | Tickets, accidents, or claims in the last 3 years. |
| driver_1_dui_dwi_in_the_past_5_years | DUI or DWI in the last 5 years. |
| driver_1_date_of_dui_dwi | Date of the DUI or DWI. |
| driver_1_dui_state | State where it occurred. |
| driver_1_bankruptcy_in_past_5_years | Bankruptcy in the last 5 years. |
| driver_1_reposessions_in_the_past_5_years | Repossessions in the last 5 years. Send it with this exact spelling. |
| driver_1_additional_drivers | Whether other drivers should be covered. |
| driver_1_additional_vehicles | Whether other vehicles should be covered. |
| INCIDENTS 1–3 | |
| driver_1_incident_type_1 | What kind of incident it was. |
| driver_1_approximate_date_1 | Roughly when it happened. |
| driver_1_damages_1 | Damage resulting from it. |
| driver_1_at_fault_1 | Whether the driver was at fault. |
| driver_1_insurance_paid_amount_1 | Amount the insurer paid out. |
| …_2 and …_3 | The same five fields repeat for a second and third incident. |
Second driver
| FIELD | WHAT IT IS |
|---|---|
| driver_2_first_name | Given name. |
| driver_2_last_name | Family name. |
| driver_2_email | Email address. |
| driver_2_daytime_phone | Daytime phone number. |
| driver_2_address | Street address. |
| driver_2_city | City. |
| driver_2_state | State. |
| driver_2_zip | ZIP code. |
| driver_2_birthdate | Date of birth. |
| driver_2_age | Current age. |
| driver_2_gender | Gender. |
| driver_2_marital_status | Marital status. |
| driver_2_credit_rating | Credit tier. |
| driver_2_education | Education level. |
| driver_2_license_status | License status. |
| driver_2_licensed_state | State that issued the license. |
| driver_2_age_when_first_licensed | Age at first licensing. |
| driver_2_suspended_or_revoked_in_the_past_5_years | Suspension or revocation history. |
| driver_2_filing_required | Whether an SR-22 or similar filing is required. |
Home Playbook Fields
The same four core fields are required. The rest describes the property and the coverage the homeowner is shopping for - the detail that lets Mav qualify before a rep ever picks up.
| FIELD | WHAT IT IS |
|---|---|
| CORE — REQUIRED | |
| first_name | The lead's given name.REQUIRED |
| last_name | The lead's family name.REQUIRED |
| The lead's email address.REQUIRED | |
| phone | The lead's phone number. Must be a valid US mobile number.REQUIRED |
| APPLICANT | |
| dob | Date of birth. |
| gender | The lead's gender. |
| credit | Self-reported credit tier. |
| primary_phone | Primary phone in national format, if different from phone. |
| origin_phone | The originally captured phone in E.164 format. |
| PROPERTY ADDRESS | |
| address | Street address of the property. |
| city | City. |
| state | State. |
| zip | ZIP code. |
| THE PROPERTY | |
| property_type | Single family, condo, townhouse, mobile home. |
| year_built | Year the home was built. |
| construction_type | Frame, masonry, brick veneer. |
| roof_type | Roof material, and age if known. |
| stories | Number of stories. |
| square_footage | Living area in square feet. |
| bedrooms | Number of bedrooms. |
| bathrooms | Number of bathrooms. |
| home_value | Estimated value of the home. |
| heating_type | How the home is heated. |
| garage | Garage type and capacity. |
| home_security | Security or alarm system details. |
| smoke_alarm | Whether smoke alarms are installed. |
| COVERAGE | |
| currently_insured | Whether the home is insured today. |
| current_insurance_company | Current insurer. |
| insured_since | When the current coverage began. |
| policy_expiration | When the current policy expires. |
| coverage_type | The coverage the lead is shopping for. |
| liability | Desired liability limit. |
| deductible | Desired deductible. |
| claims | Prior claims history on the property. |
| CONSENT, SESSION, AND ROUTING | |
| tcpa_consent | The consent flag or captured consent value. |
| leadid_token | LeadiD or Jornaya consent token. |
| trusted_form_url | TrustedForm certificate URL. |
| ip_address | The lead's IP at the time of submission. |
| device_type | Device used to submit the form. |
| src | Traffic source identifier. |
| landing_page | URL of the page the lead came from. |
| did | The number Mav should transfer this lead's call into, overriding the source's default. |
FIELD REFERENCE · CUSTOM SOURCES