Quest conversions cannot support both reporting and ranking when campaign mappings disagree.
Advertiser confidence depends on stable measurement, while delivery systems need timely inputs from the same conversion records.
Who you’d be doing this for
“I had to explain why yesterday’s conversion total changed after we’d already shared it with the studio team.”
Wagner Hernandez · Growth Lead at a game studio
Runs Quest campaigns and uses conversion reporting to decide which community activations receive more spend.
What is at stake
Quest conversion totals differ across delivery and measurement for active campaigns. You have to weigh a fast pipeline correction against preserving auditable history and dependable ML inputs.
Why it isn’t already fixed
Every obvious fix costs something else. That’s the part you’d have to decide.
- reporting continuity vs. canonical accuracy
- historical lineage vs. rapid correction
- ML input stability vs. refreshed attribution
- BigQuery cost vs. full reconciliation
Why Discord
Quest measurement connects advertiser spend to activity across community spaces without changing the core member experience.
Written with these in mind
Not your kind of problem? 16 more at Discord, 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.