Your whole flyer operation. From street to sale.

Choose where to go. Organize the crew. Track the ground you cover. Connect your flyers to the response on your website. DoorDroppr brings the physical campaign and the digital results together.

One organization, many campaigns
A field app alongside the planning tools
The same record from the street to the sale

Get early access

Private beta. Paid checkout and print ordering are separate launch items.

AreaA neighborhood with the right audience

WorkOne campaign, three crew territories

FlyersEvery batch tied to the campaign

ResponseScan, lead, booking, revenue

One business. A connected chain of work.

A line on a map can tell you where someone walked. The platform adds the context you need to run a business around that work. Field activity arrives from one side, website response from the other, and both land in the same campaign record.

On the street

Field app on iPhone: Start a shift, walk, end the shift. GPS runs in the foreground and the background.
Live team map: The latest position of everyone on an active shift, with dispatch notes.
Print-partner console: A separate web app where a print partner sees assigned orders. Not open for commercial orders yet.

Positions, distance, door estimates
Planned route, territory, dispatch

The campaign record

Organization: Your business, its members and their roles
Campaign: The area you chose and when you ran it
Territories: The pieces of that area, with planned routes
Shifts: Who walked, the GPS trail, distance and doors
QR codes: One per campaign, territory, crew member or flyer
Scans: Every scan, logged before the redirect
Conversions: Leads, bookings and purchases your site reports
Results: The funnel from doors to revenue

Scan token on the landing URL
Lead, Booking, Purchase events

On your website

Tracked redirect: Sits behind every QR code. It records the scan, then forwards the visitor to your page.
Pixel snippet: doordroppr('init', PIXEL_ID) reads the token and reports events from the browser.
Server endpoint: Your server can send the same events with a secret key.

The organization is your home base.: Your business owns its campaigns, members, and results. Team members join once, with roles that control what they can manage. A small owner-operated business can plan and walk its own campaigns, and a manager can coordinate a larger crew.
The campaign holds the whole story.: A campaign ties the neighborhood, territories, shifts, QR codes, and conversion activity together. You can review what was planned, where work happened, and which responses came back to that campaign.
Your customers stay on your website.: A flyer scan goes through a tracked redirect to your existing destination. The pixel or conversion API reports supported activity back to DoorDroppr. Keep the booking system, store, or lead form your business already uses.

Follow one flyer through the system.

Six steps, and what each one writes to the campaign record. DoorDroppr is a measurement layer. It is not a booking system or a CRM, so the sale itself happens in the tools you already run.

Step	What happens	What is recorded
Plan	The owner creates a campaign for a neighborhood and one or more territories inside it. A territory can carry a planned path.	Campaign, territories, planned path
Code	QR codes are created for the campaign and can be narrowed to a territory, a crew member or a coupon. Each area gets one code.	One code per area
Walk	A crew member starts a shift and the app sends GPS positions as they walk. The live team map shows everyone on an active shift.	Shift, positions, distance, door estimate
Scan	A resident scans the flyer. The redirect looks up the code, records the scan, then forwards them to your page with a scan token on the URL.	Scan time, coarse location from the IP address, browser
Convert	The resident books or buys on your own site. The pixel, or your server, sends a Booking or Purchase event that carries the token back.	Event, plus one conversion with its value
Measure	Results roll the chain up in one read, so the campaign screen shows the whole funnel at once.	Shifts, doors, distance, scans, bookings, revenue

What the record cannot prove. GPS shows where a phone travelled. It does not prove a flyer reached a door. Door counts are estimates, and revenue appears only when your website reports a value.

Where things stand.

The private-beta product contains field tracking, campaign operations, neighborhood scouting, QR attribution, and one QR code per area. Commercial print ordering, live payments, learned verification, and the paid marketplace have separate launch dependencies. Availability and data coverage vary by feature and market.

Showing 29 of 29 items

Capability	Status	Detail
Organization
Organizations, members and roles	Built	Owner, admin, crew and a read-only viewer.
Joining by invite code	Built	A member joins once and works inside that business.
Data scoped to each organization	Built	Every table is limited to the organization that owns the rows.
Plans and limits inside the app	Partly built	A plan screen and server-checked limits exist. There is no checkout.
Field work
Starting and ending a shift	Built	One flow from picking a route to the shift summary.
GPS tracking, foreground and background	Built	iPhone, with the screen off and the phone in a pocket.
Planned-route guide	Built	A suggested walking line drawn on the map.
Walking directions to the start and back	Built	Pedestrian routing to the first street and back afterwards.
Coverage history and replay	Built	Covered streets add up across shifts.
Territories	Built	A campaign divided into areas of work.
Live team map	Built	Depends on each phone's permissions and signal.
Crew leaderboard	Built	Ranks crew by doors, scans and distance.
Door counts	Partly built	Shown as estimates. They are not a count of flyers delivered.
Flyers and attribution
QR codes scoped to a campaign, territory or crew member	Built	Created with the campaign.
Tracked redirect and scan logging	Built	The scan is recorded before the visitor is forwarded.
Smart flyers, one code per flyer	Built	A batch creates a unique code for every sheet.
Pixel snippet	Built	Six standard events, from ScanLanding to Call.
Server-side conversions	Built	The same events sent from your server with a secret key.
Event funnel and campaign results	Built	From doors to scans, bookings and revenue.
Attribution on a later visit	Partly built	The scan token is kept in a first-party cookie. A full multi-touch model is not built.
Print ordering and fulfilment	Partly built	The order loop and a print-partner console exist. Payment is simulated and commercial ordering is not open.
Native platform plugins	Planned	The snippet and Google Tag Manager work today.
Scouting and evidence
Census scouting with a fit score	Built	Income, density and ownership. Data coverage varies by market.
Rule-based delivery signals	Partly built	Field capture and rule-based signals exist.
Learned verification model	Planned	Still in development.
Commercial
Paid checkout and published prices	Planned	Free, Pro and Business are named. Prices are undecided.
App Store listing	Planned	The iPhone app is installed by invitation today.
Android	Planned	Not available yet.
Delivery marketplace	Planned	Depends on stronger evidence and real payments. It is not an open paid service.

Four roles.

Owner	Everything, including billing and handing the business to someone else. Creating an organization makes you its owner.
Admin	Runs the business day to day, with campaigns and crew. No billing and no ownership.
Crew	Walks. Joins with an invite code and works the territory they are given.
Viewer	Read-only. Suited to someone who needs to see results and manages nothing.

Four boundaries.

Between organizations	A member of one organization cannot read or write another organization's rows.
Print partners	A separate kind of account. A partner reaches the orders assigned to them, the codes to print and the status they report. Never location, scans or revenue.
Pixel keys	A public pixel ID for the browser and a secret key for servers. The secret is stored only as a hash and can be rotated.
Ownership	An organization always has at least one owner. The database refuses a change that would leave it with none.

Start with the part you need.

You should not have to change everything about your operation to start understanding it.

Run your own drops.
Use neighborhood scouting, campaign planning, tracking, and results together. Start as an owner-operator, then add members and territories when you need a crew.
Uses
Scouting, Campaigns, GPS tracking, Results
Status
In the private beta
Field tracking
Measure an existing distribution service.
If someone already handles your delivery, use campaign QR codes and website attribution to measure the response. You can begin with the measurement layer without moving the entire crew into DoorDroppr.
Uses
QR codes, Redirect, Pixel
Status
In the private beta
The pixel
Prepare for a broader delivery network.
The longer-term direction adds independent walkers who choose delivery jobs, handle flyer custody, and complete routes for businesses. The marketplace depends on stronger evidence and real payment infrastructure. It is not an open paid service today.
Uses
Marketplace
Status
In development
The marketplace

One record, from the street to the sale.

Bring your area, your crew, your flyers and your results together.

Join the list
Get your invite by email
Walk your first street