Understanding the Attributed By Filter and Event Property Usage
Can you explain the “Attributed by…” filter. Is this any user who has fired any event with the given event property?
Can you explain the “Attributed by…” filter. Is this any user who has fired any event with the given event property?
Hi Ashton C., Please stand by as I search the Mixpanel knowledge base for an AI-powered answer. I normally take about 15 seconds or so. In case AI cannot answer your question, feel free to reach out to Mixpanel support at mixpanel.com/get-support. If you have follow-up questions for this thread, please tag me again with your question: @kapa.ai <follow-up question> 👋
Feel free to ask a follow-up question once I've answered by mentioning me with @kapa.ai
“Attributed by…” is part of Mixpanel’s Attribution feature, not a generic “has this property anywhere” filter.Conceptually: - You first pick a conversion metric (e.g. Purchases).
- Then in Breakdown, you choose the computed property “Attributed by…” and select an attribution property (e.g. utm_source). [Attribution; Blog guide]
- Mixpanel then looks back from each conversion event over a defined lookback window and finds touchpoint events that have that property. It applies the chosen attribution model (last touch, linear, etc.) and assigns conversion credit to the property values it finds. [Attribution glossary]So: - It is not “any user who has ever fired any event with this property.”
- It is “conversion events whose attributed touchpoints (within the lookback window) have this property value,” according to the attribution model.When you then filter on an attribution segment (e.g. “Attributed by utm_source = Google”), you’re narrowing conversion events to those whose computed attribution includes that value, not just users who ever had utm_source = Google. [Attribution FAQ]
kapa.ai is still learning and improving, please let me know how I did by reacting below.
ℹ️ Tip: Mention @kapa.ai in the thread for follow-ups or DM the app for 1-to-1 help.
Let me check the knowledge base for you again. One moment! 📚
You don’t need to explicitly define “attributed touchpoints” in your data model—Mixpanel derives them automatically.What you do need: 1. A conversion metric
In your report, you pick the event you care about (e.g. Purchase) as the metric. [Attribution]2. An attribution property on touchpoint events
In the Breakdown section, choose Attributed by… and then select a property like utm_source, utm_medium, or a custom “channel” property. Mixpanel then treats any events in the lookback window that have this property as touchpoints. [Attribution; Glossary]3. A lookback window + model
Mixpanel automatically applies a model (default: Last Touch, 30‑day lookback) and computes how much credit each touchpoint gets. [Attribution; Attribution FAQ]So you don’t define “this event is a touchpoint” in the UI; you just ensure the relevant events carry the attribution property, and Mixpanel infers touchpoints from those events within the lookback window.
kapa.ai is still learning and improving, please let me know how I did by reacting below.
ℹ️ Tip: Mention @kapa.ai in the thread for follow-ups or DM the app for 1-to-1 help.
