Comment PLAN on a Reel and the program link arrives by DM.
Reply to a story, leave an email, get the routine guide.
Send BOOK and pick a free time without leaving the chat.
An ad opens the DM, two quick questions pick the right course.
Comment AUDIT on a Page post, answer two questions, reach the team.
AI answers product questions in DMs and hands off to a person on request.
Send MENU and get the menu and a reservation link on one card.
The bio link opens a DM that asks which day and sends that ticket link.
Attribution answers one question: which message from ChatinFlow reached a customer before they bought. Your store tells ChatinFlow when an order happens, and ChatinFlow looks back through that customer's history for the last AI reply or broadcast they received. It replaces guessing from a busy inbox, or asking every buyer where they heard about you.
Last touch
Model
30 days
Window
Reported
Amount
Credited to
AI reply
ChatinFlow writes down every touch.
Each AI reply that goes out and each broadcast that is delivered is recorded against the contact who received it, with the name of the flow or broadcast.
Your store reports the sale.
When an order is placed, your checkout or a small script of your own sends the order id, the amount if you want to share it, and the buyer's email or phone number to the ChatinFlow API.
ChatinFlow matches the buyer to a contact.
The email, phone number, or channel id is looked up in your workspace only. A buyer who never messaged you is still recorded, as an unattributed sale.
ChatinFlow credits the last touch.
The most recent AI reply or delivered broadcast in the 30 days before the order gets the credit, and the earlier touches in that window are saved next to it.
You read the summary from the API.
It returns the sales in the date range you ask for, attributed and unattributed, grouped by AI reply and broadcast, with every amount marked as reported by you.
From the order back to the last touch
30 days
Look-back window
Fixed server setting, the same for every workspace
Newest first, saved on the sale
25
Touches kept per sale
Snapshot limit in the attribution service
A retried request never counts twice
1
Sale per order id
The order id you send is the duplicate key
Your checkout sends each sale to one API endpoint with the order id and, if you want, the amount. ChatinFlow never sees your payments, so every sale comes from you.
The buyer is matched to a contact by email, phone number, the channel id they messaged you from, or a ChatinFlow contact id. Matching never leaves your workspace.
The most recent AI reply or delivered broadcast in the 30 days before the order gets the credit, so each sale points to one message you can repeat.
Each sale also keeps up to 25 touches that came before it. If the credit rule changes later, it can be recomputed from that history instead of starting over.
Stores retry when a request times out. Sending the same order id again returns the sale already recorded, so one order never shows up as two.
The summary lists attributed and unattributed sales side by side, grouped by touch type, and marks every amount as reported by your workspace rather than measured.
Business plan or higher
Your store calls the API with a personal access token, and creating one needs a plan that includes API access: Business and above.
A token with write access
Reporting a sale needs a token with the write ability, created by a teammate who is allowed to change workspace settings.
A way to send each order
An order webhook, an automation inside your store, or a script of your own that posts to the conversions endpoint when a sale completes.
Contacts you can match
A sale only gets credit when the buyer's email, phone number, or channel id is already saved on a contact in your workspace.
Send each order to the ChatinFlow API and see which AI reply
or broadcast reached that customer last.
More messages, less mess.
Everything you need to know before your first automation goes live.