Conversion tracking
Tell Nohmo what a successful conversion means for your business — a user signup, a deposit, a purchase — and track which traffic sources (Google Ads, Meta Ads, organic, etc.) are driving those conversions.
1. Define your conversion goals
Go to Settings → Conversions in your dashboard and create conversion goals. Each goal has a human-readable name and a unique slug that you reference in code.
User Created
user_created
Money Deposit
money_deposit
Subscription Started
subscription_started
2. Call trackConversion() in your code
Pass the goal slug when the conversion event happens. You can also attach extra properties like amount, plan, or currency.
import { useNohmo } from 'nohmo'export default function SignupSuccess() {const { trackConversion } = useNohmo()useEffect(() => {// Fire once after successful signuptrackConversion('user_created')}, [])return <div>Welcome!</div>}
// With extra properties (e.g. deposit amount)trackConversion('money_deposit', { amount: 500, currency: 'USD' })
For plain HTML / Django templates, use the global window.nohmo object:
<script>// After a successful depositwindow.nohmo.conversion('money_deposit', { amount: 500 })</script>
3. View results in Traffic → Conversions
Open the Traffic page in your dashboard and switch to the Conversionstab. You'll see:
- Total conversionsAcross all goals or filtered by a specific goal
- By sourceWhich UTM source (google, facebook, …) drove the most conversions
- By mediumcpc, email, social, organic, etc.
- By campaignIndividual campaign performance
- By custom paramConversions from your custom attribution params like ?ref=META_ADS_1
Use the goal filter buttons at the top to drill into a single conversion type — e.g. see only which sources drove Money Deposit conversions.
Attribution
Conversions are automatically linked to the session's traffic source. If a user arrived via ?utm_source=google&utm_medium=cpc and later triggered a conversion in the same session, that conversion is attributed to Google CPC — no extra code needed.
Attribution is first-touch per session: it reflects the channel that brought the user into the session where the conversion happened.