Fast attribution data conflicts with the need to stop bad runs before they spread.
The pipeline must keep downstream metrics moving while engineers retain judgment over data that shopping decisions depend on.
Who you’d be doing this for
“I saved three gift ideas, then saw the same retailer visit show up twice in my activity.”
Yeji Fujita · Visual Planner
They save product Pins and revisit shopping ideas, creating actions that feed the attribution data under review.
What is at stake
Schema-driven duplicates are reaching downstream shopping metrics even when aggregate checks pass. You must decide what AI flags on its own and what an engineer must verify before holding data.
Why it isn’t already fixed
Every obvious fix costs something else. That’s the part you’d have to decide.
- early detection vs. false holds
- AI evidence vs. engineer approval
- data velocity vs. metric trust
- platform stability vs. richer inspection
Why Pinterest
Shopping attribution connects saved product ideas and retailer actions to the performance signals used across Pinterest.
Written with these in mind
Not your kind of problem? 40 more at Pinterest, or browse every organization.
This is the setup. The work is inside.
Running it puts you in the room: the full situation and its constraints, stakeholders who push back in their own words, and the decisions that are yours to make. What you produce becomes a Day One Plan — work you can show someone instead of describing.