End-to-end workflow walkthrough
How a single inquiry moves from ad click to recorded sale and CAPI feedback
Instead of abstract claims, trace how a single furniture inquiry progresses through 6 verifiable steps—from source capture and missing-field completion to proposal tracking and ad feedback.
-
01
Source
Meta CTWA / Instagram Ad
Ref: ctwa_clid · Campaign: Modular Sofa – Spring
When a buyer taps the Instagram ad and starts a WhatsApp thread, the click reference (Ref / ctwa_clid) and campaign metadata are captured alongside the opening message.
Output: Source campaign and click reference attached to CRM record
-
02
Conversation
WhatsApp Inbox
Lead: Elif Demir · Owner: Mert (Showroom Sales)
The incoming message lands in the shared WhatsApp inbox; a sales rep is assigned and replies from the same view with full campaign context intact.
Output: Thread history and rep assignment unified on one record
-
03
Profile & Missing Info
ICP Evaluation
buyer_type: B2C · product_category: Living Room · Istanbul · EUR 4,200
The buyer_type and product_category signals match the target profile while missing location and budget fields surface in the missing-info queue. Confirming Istanbul and EUR 4,200 brings information coverage to 100% (Suitable).
Output: Coverage 100% · Status: Suitable
-
04
Proposal & Follow-Up
Proposal & Task Queue
Custom Quote #1084 · Amount: EUR 4,200 · 48h Follow-Up
A custom-dimension quote is shared via trackable link; customer views are recorded and a 48-hour follow-up task surfaces inside the daily 3-item priority workqueue.
Output: Proposal viewed · Surfaced in daily workqueue
-
05
Recorded Sale
Won Stamp
Status: Won · Recorded Value: EUR 4,200 · Close Timestamp
Following the showroom visit and confirmed order, the lead record is stamped Won with the verified deal value (EUR 4,200) and close timestamp.
Output: Verified deal value and close timestamp recorded
-
06
Qualified Ad Feedback
Meta CAPI & Google Ads
Events: QualifiedLead & Purchase · SHA-256 + event_id
Only verified QualifiedLead and Purchase events are dispatched server-side back to the source campaign with SHA-256 identifier hashing and event_id deduplication.
Output: Deduplicated conversion signal dispatched to ad platform