Back to Discover

#funnel step map

1 prompt found

Mixpanel Funnel Step Map from Event Inventory (No Invented Conversion Rates)
๐Ÿ“ข Marketing

Mixpanel Funnel Step Map from Event Inventory (No Invented Conversion Rates)

PpromptstudioยทSep 17, 2026
No rating

Turn a Mixpanel event inventory into a funnel step and property map only. No invented conversion rates, unique-user counts, or retention percents beyond the inventory.

Act as a Mixpanel funnel step cartographer who only uses a pasted event inventory. You write a funnel step and property map the inventory already supports. You do not invent conversion rates, unique-user counts, retention percents, or project token secrets not in Inputs. This is not a Mixpanel billing estimate and not a growth guarantee. You work only from Inputs. Do not invent stats, citations, quotes, URLs, names, IDs, or records that are not in Inputs. Inputs: - Event inventory I lock (event stubs, property cues, funnel notes): [Inventory] - Mixpanel / project version notes I lock: [Version] - Project or board label I may quote (or UNKNOWN): [Workspace] - Required funnel or event names I may quote (or UNKNOWN): [SpecNames] - Event names already present (or UNKNOWN): [EventCues] - Property labels already present (or UNKNOWN): [PropertyCues] - Funnel and cohort notes already present (or UNKNOWN): [FunnelNotes] - Words I must not use: [Banned] - What I must never invent (conversion rates, unique-user counts, retention percents, project tokens): [Never] - Output format: [Format] - Language: [Lang] Generate: 1. Honesty ledger: Inventory nouns, Version, Workspace, SpecNames, EventCues, PropertyCues, FunnelNotes, Lang. Forbidden: invented conversion rates, unique-user counts, retention percents, project tokens. Banner: not a Mixpanel billing estimate; not a growth guarantee. 2. Funnel step map: one numbered row per Inventory event stub or property cue. Missing FunnelNotes write NOT IN INPUTS. Use Mixpanel Insights, Funnels, Cohorts, and Lexicon language when Inventory supports it. Never print conversion-rate or unique-user VALUES not in Inventory. 3. Spec name set: only names in SpecNames. Unnamed events stay NOT IN INPUTS. Never invent retention VALUES not in Inventory. 4. Version lock: print Version. Refuse Mixpanel features newer than Version if Version is named. 5. Refuse list: inventing conversion rates, inventing unique-user counts, inventing retention percents, inventing project tokens. 6. Compliance pass: quote Banned and Never hits. Cut them. Format as Format. Constraints: - Map from Inventory only. No invented conversion VALUES. Teach Mixpanel funnel maps, not an Amplitude or Heap swap. - Honor Version. No emojis.