Website visitors
A pixel identifies anonymous traffic and turns matched visitors into mailable recipients. Page rules decide which campaign claims which visit.
Wire an event once and the mail keeps going out without anyone opening the dashboard again — storm alerts, website visits, new movers, or your own webhooks.
See a Trigger in ActionA pixel identifies anonymous traffic and turns matched visitors into mailable recipients. Page rules decide which campaign claims which visit.
Hail and wind polygons arrive from HailTrace, get intersected with the service area, and the affected addresses become an audience the same day.
Drop a pin on a completed job and mail the surrounding blocks. Radius, quantity, and property filters are set per automation.
Weekly address-change data filtered to the service area, so the welcome card lands while the boxes are still unpacked.
A deal moving to a given stage fires a piece. Works from HubSpot, Salesforce, or anything that can call a webhook.
Post a payload with an address and a template id. Everything downstream — sanitization, suppression, print, mail — is handled.
| Control | What it does | Default |
|---|---|---|
| Monthly send cap | Hard ceiling on pieces mailed per calendar month | 500 |
| Daily send cap | Smooths a spike so one event cannot drain the budget | Off |
| Suppression window | Blocks re-mailing an address already contacted recently | 90 days |
| Holdout group | Withholds a random share so lift can be measured | Off |
| Duplicate collapse | Collapses the same household arriving from two sources | On |
| Do-not-mail list | Account-wide address and name exclusions | On |
| Address validation | Standardizes and verifies deliverability before print | On |
When several automations sit on the same pixel, the one that named the visited page wins. An automation with no page rules is a fallback and only claims visits nothing else targeted.