System Recall Campaigns

System Recall Campaigns alert shoppers when a vehicle they own has an open, unresolved manufacturer recall, and guide them to book a service visit to get it resolved. It is a vehicle-audience group: eligibility is evaluated per owned vehicle, not at the shopper level.

At a glance

Notices

3 — Recall First Notice, Recall Second Notice, Recall Third Notice

Audience type

Vehicle audience (evaluated per owned vehicle)

Primary data

OEM recall data (NHTSA) plus DMS service appointment data

Trigger

Escalating notice schedule tied to how long the recall has been open, for as long as the vehicle remains unserviced

Notices in this group

This group contains three notices for the same underlying recall, escalating the longer it stays open without the vehicle being brought in for service.

Recall First Notice — sent when a new recall opens on an owned vehicle.
Recall Second Notice — sent if the recall is still open roughly two weeks later.
Recall Third Notice — sent if the recall is still open roughly a month later.

How it works

Goal

Get the shopper to book a service visit and resolve an open safety recall on a vehicle they own, before it reaches the point of escalating outreach.

Audience

Owners of a vehicle with an open OEM recall. Because this is a vehicle audience, each qualifying vehicle a shopper owns is evaluated on its own — a shopper with two recalled vehicles can be active in more than one notice at the same time.

Trigger

Each notice fires based on how long the recall has been open, measured from the recall's start date: roughly day 0–1 for the First Notice, day 13–14 for the Second, and day 29–30 for the Third.

Suppression

A shopper is pulled out of all three notices as soon as the recalled vehicle has a qualifying service appointment on record — they stop receiving outreach the moment they've taken action, whether or not the repair itself has been completed yet.

Data used

Recall data comes from NHTSA (the U.S. National Highway Traffic Safety Administration) and is matched automatically against each dealer's own vehicle inventory — there's no client-side setup for the recall data itself. Service and appointment data comes from the dealer's DMS integration.

Requirement: Both OEM recall data and DMS service appointment data must be present for an account for these notices to build correctly. If a dealer's DMS integration doesn't include service appointment data, the system can't confirm whether a recalled vehicle has already been brought in — and the audience can't be built. Learn more about supported appointment data and DMS here.