Example: Marketplace (Jiji)
A complete autopilot integration for a two-sided marketplace like Jiji — events, mapping, stages, and campaigns.
A classifieds marketplace like Jiji connects buyers and sellers: people sign up, browse, contact a seller, then complete their first transaction — and the best users transact again and again. The Marketplace model captures this two-sided, high-frequency journey, and it unlocks every opportunity kind the autopilot offers.
1. Events to instrument
Emit these from your marketplace backend, keyed by the user's external_id. (This example engages the buyer side; you can run a second workspace or contact set for sellers.)
Your event Fires when… Useful properties
------------------- ------------------------------- -------------------------
account_created a user signs up signup_source, category
seller_contacted a buyer messages a seller listing_id, category
about a listing
first_transaction they complete their first deal listing_id, amount
transaction any completed deal (incl. first) listing_id, amount, category
curl https://api.engageapp.xyz/api/v1/public/events \
-H "X-API-Key: df_your_secret_key" \
-H "Content-Type: application/json" \
-d '{
"events": [
{ "external_id": "user_3390", "event_name": "seller_contacted",
"properties": { "listing_id": "L-99213", "category": "electronics" } }
]
}'
2. Choose the model & map events
Pick Marketplace and map:
Canonical behavior Role Your event Required?
------------------ ----------- ----------------- ---------
signed_up acquisition account_created required
first_transaction conversion first_transaction required
transacted activity transaction required
contacted_seller intent seller_contacted optional (unlocks abandon)
Transaction count tiers up active traders and power users automatically.
3. Resulting lifecycle stages
Users are classified as visitor → buyer → active trader → power user → lapsing → churned. Three transactions make an active trader; ten make a power user, while recently active.
4. Opportunities & campaigns
- Onboarding stall — signed up but never transacted. Campaign: trending listings in their category and a "how it works" nudge.
- Abandon — contacted a seller recently but didn't transact. Campaign: "still interested?" with the listing and similar options.
- Post-conversion — just completed their first deal. Campaign: rate-your-experience plus recommendations for the next purchase.
- Re-engage dormant — traded before, now quiet. Campaign: fresh listings in categories they've browsed.
- High-value nurture — power users (10+ transactions). Campaign: seller tools, priority support, or category perks.
- Win back — lapsed traders. Campaign: what's new in the marketplace and a reason to return.
Because it maps every role except churn, the marketplace model runs the full opportunity catalog.
5. Channels, autonomy & real-time
Connect push and email for listing-driven nudges; WhatsApp works well for high-intent follow-ups. Start in review required. Both seller_contacted (intent) and first_transaction (conversion) trigger real-time detection, so a stalled high-intent buyer is followed up quickly.
Next steps
- Start from the general integration guide.
- Selling your own inventory instead of hosting sellers? See the e-commerce example.
Related
Integration guide
Everything you instrument on your side to power the Engagement Autopilot — contacts, events, the canonical behaviors, channels, and verification.
Example: E-commerce (Konga)
A complete autopilot integration for an online retailer like Konga — events, mapping, stages, and campaigns.
Events
Send behavioral events about your contacts to trigger campaigns, gate waits, and power segments.
Opportunities & the review queue
The micro-segments the autopilot detects, how it drafts a campaign for each, and how you approve or dismiss them.