Delivery membership & benefit eligibility · PUBLIC RESEARCH BRIEF
DoorDashWhich DashPass moment makes eligibility feel clear and fair?
DoorDash's current DashPass support materials cover an automatically renewing membership whose benefits depend on eligible orders and merchants. They also describe Family Sharing for eligible plans, with separate accounts, payment methods, order histories and delivery preferences. This brief tests benefit and eligibility explanations, not order or retention effects.
Updated 2026-09-29 · Simulation results not yet generatedCHANGE ONE THING. LEARN WHAT MATTERS.
Three questions for the GTM team.
For DashPass Family Sharing, would showing eligibility and privacy boundaries before the invite or during acceptance better prevent failed or misunderstood invitations? Use fictional accounts and do not send an invite.
Set up this study →At DashPass renewal or cancellation, would a verified usage recap or a concise terms summary better help members understand their options without pressure? Use synthetic orders and no payment method.
Set up this study →PROPOSED AUDIENCE
Who should weigh in?
North American adult DoorDash consumers who are active, lapsed or prospective DashPass members. Include a range of order frequency, merchant mix, household structure, partnership-plan status and familiarity with Family Sharing. Proposed audience; no order, savings, renewal or retention outcome is implied.
TWO TIME HORIZONS
Trial today. A habit tomorrow?
Near term · 0–90 days
Over 0–90 days, test checkout, Family Sharing and membership-management prototypes with synthetic accounts, merchants and baskets. Measure eligibility comprehension, mistaken benefit assumptions, privacy understanding and task completion. Do not place orders, invite people, change memberships or process payment.
Longer term · 3–12 months
Over 3–12 months, follow approved cohorts across merchant availability, household changes and promotional periods. Examine benefit discovery, eligibility inconsistency, partnership-plan confusion, renewal expectations, support contacts and offer fatigue. Order, savings or retention claims require observed records and controls.
What would make the result actionable?
Use versioned DashPass terms, synthetic accounts and independently adjudicated eligibility. Hold merchant, minimum, geography and basket constant across concepts; include ineligible, expired and no-benefit cases; separate perceived fairness from actual outcomes and require human review.
A Gather simulation returns hypothetical customer reactions. Quantifying revenue, traffic or retention needs actual business inputs and validation against observed behavior.