SW Manager 功能說明SW Manager features
Conversions:怎樣算一次轉換Conversions: what counts as one
定義「一通電話要多長才算一次轉換」。目前唯一能用的方式是 Call duration:通話秒數 ≥ 門檻就算一次。可以設定每次轉換值多少錢,用來算營收。Defines how long a call must last to count as one conversion. The only method available today is Call duration: a call at or above your threshold counts once. You can attach a dollar value to compute revenue.
整個功能在 feature flag CONVERSION_TRACKING 後面。flag 沒開時左側選單會隱藏,頁面會 404。The whole feature sits behind the CONVERSION_TRACKING feature flag. With the flag off the sidebar entry is hidden and the page 404s.
兩個分頁Two tabs
- Define Conversions —— 定義要計算哪些轉換,看次數。Define Conversions — define what to count, and see the counts.
- Received Events —— 看系統收到哪些事件,把還沒定義的變成 conversion。Received Events — see which events arrived, and turn undefined ones into conversions.
網址用 ?tab=define / ?tab=received 切換,打錯的 tab 值會回到 Define。The URL switches with ?tab=define / ?tab=received; an unrecognised value falls back to Define.
Conversions 列表The conversions table
| 欄位Column | 意思Meaning |
|---|---|
| Trigger | 門檻,例如 call ≥ 60s。The threshold, e.g. call ≥ 60s. |
| Value | 每次轉換的金額。顯示「—」代表只計次、不算營收。Dollar value per conversion. An em dash means counted but not valued. |
| Today / Yesterday | 太平洋時間的今天和昨天。Today and yesterday in Pacific time. |
| Last 7 days | 含今天在內的 7 個日曆天。Seven calendar days including today. |
| Status | 一律顯示 Activated。目前沒有刪除或停用的功能(產品已確認)。Always Activated. There is no delete or disable yet (confirmed by product). |
| Edit | 打開精靈,從第 2 步開始。Opens the wizard at step 2. |
可以排序的欄位:Conversion、Today、Yesterday、Last 7 days。點擊順序是升冪 → 降冪 → 取消。每頁 20 筆。Sortable columns: Conversion, Today, Yesterday, Last 7 days. Clicking cycles ascending → descending → off. 20 rows per page.
每日轉換圖表The daily chart
每個 conversion 最近 30 天每天的轉換次數,一條線代表一個 conversion。用太平洋時間切日,沒資料的天畫成 0。圖表載入失敗時,下面的列表還是會顯示,並提供重試。Daily counts for the last 30 days, one line per conversion. Days are cut in Pacific time; days with no data are drawn as 0. If the chart fails to load the table below still renders, with a retry.
夏令時間切換那天(23 或 25 小時)的計算會差一小時。On a daylight-saving changeover day (23 or 25 hours) the maths is off by an hour.
精靈的三個步驟The three wizard steps
Method → Details → Review。上面的步驟圓圈不能點,鍵盤 Enter 會進到下一步。進入點不同,起點也不同:Method → Details → Review. The step circles are not clickable; Enter moves to the next step. Where you start depends on how you got in:
| 從哪裡進來Entry point | 從第幾步開始Starts at |
|---|---|
| 新增(Create conversion action)New (Create conversion action) | 第 1 步 MethodStep 1, Method |
| Edit | 第 2 步 Details。可以按 Back 回到 Method,但 Method 是鎖住的,不能改。Step 2, Details. Back returns to Method, but Method is locked. |
| 從 Received 按 DeclareFrom Received, via Declare | 第 2 步 Details。名稱已預填而且不能改。Step 2, Details. The name is pre-filled and locked. |
第 1 步 — MethodStep 1 — Method
只有 Call duration 能選(有 Live 標籤)。Link clicks、Pixel / JS tag、Server API / Webhook、CSV / manual upload 都是 Coming soon。Edit 時不能改 Method,會提示「create a new conversion instead」。Only Call duration is selectable (tagged Live). Link clicks, Pixel / JS tag, Server API / Webhook and CSV / manual upload are all Coming soon. Editing cannot change the method — it tells you to create a new conversion instead.
第 2 步 — DetailsStep 2 — Details
Conversion name —— 必填(只打空白不算),最多 64 個字,同一個帳號內不能重複(比對不分大小寫,也會去掉前後空白)。存檔時如果被後端判定重複(409),會回到這一步,錯誤顯示在名稱欄。Conversion name — required (whitespace alone does not count), up to 64 characters, and unique within the account (compared case-insensitively and trimmed). If the backend rejects it as duplicate (409) on save, you return to this step with the error on the name field.
如果之後也要送到 Google 或 Meta,建議用跟那邊一樣的名稱,報表比較好對。If you will also send this to Google or Meta, use the same name there — the reports line up more easily.
Call duration —— 通話秒數 ≥ 這個數字就算一次轉換(剛好等於也算)。必須是 1 以上的整數,預設 60。前端沒有上限,後端上限是 86400。跟另一個 conversion 設定一樣的秒數時,只會警告,不會擋。Call duration — a call counts when its length is at or above this number (exactly equal counts). It must be a whole number ≥ 1, default 60. The front end sets no upper bound; the backend caps at 86400. Matching another conversion's threshold warns but does not block.
只看秒數 —— 不分 inbound、主動撥出、轉接,也不看結果,所以很長的語音信箱也會算。一般撥號用 call log 的 duration;Ava 通話用整通的長度(含 AI 那段)。
同一個 contact 對同一個 conversion 只算一次,但一通電話可以同時算進好幾個 conversion。通話秒數之後被改短的話,已經算的那次不會被撤銷。Only the seconds matter — not inbound vs outbound vs transfer, and not the outcome, so a long voicemail counts too. Ordinary dialling uses the call log's duration; Ava calls use the whole call including the AI segment.
One contact counts once per conversion, but a single call can count toward several conversions. If the duration is later shortened, an already-counted conversion is not withdrawn.
Dollar value —— 選填,用來算營收。只能填整數美元:12.5 會被擋,-1 也會被擋。$0 也算有填值,跟留空(只計次、不算錢)不一樣。有填金額時幣別自動設成 USD。Dollar value — optional, used for revenue. Whole US dollars only: 12.5 is rejected, so is -1. $0 counts as a value and is not the same as leaving it blank (counted but not valued). When a value is set, the currency is USD.
Conversion role(Primary) —— 目前是 Coming soon,預設勾選。取消勾選就變成次要的 conversion,Review 會顯示「Secondary conversion (observation only)」。現在唯一的實際效果:第一次設定 Google 匯出時,Primary 的 conversion 會預設被勾選。Conversion role (Primary) — currently Coming soon, ticked by default. Unticking makes it secondary, and Review reads "Secondary conversion (observation only)". Its only effect today: on first setup of the Google export, primary conversions are pre-selected.
第 3 步 — ReviewStep 3 — Review
存檔前最後確認 Method、Name、Trigger、Value、Role。新增時按 ✓ Create & activate,馬上開始計算,提示是「"名稱" created.」;Edit 時按 Save changes,提示是「"名稱" updated.」。存檔失敗時填好的內容不會不見,可以再試一次。A last look at Method, Name, Trigger, Value and Role. New ones use ✓ Create & activate and start counting immediately, with the toast «"name" created.»; edits use Save changes and «"name" updated.». A failed save keeps what you typed so you can retry.
改設定只影響之後的通話 —— 過去已經算的次數和金額都不會重算。Changes only affect later calls — counts and values already recorded are never recalculated.
Cancel / 放棄變更Cancel and discarding changes
- 沒改過任何東西 → 直接關掉。Nothing changed → it just closes.
- 有改過 → 跳出「Discard this conversion?」,可以選 Discard(紅色)或 Keep editing。Something changed → "Discard this conversion?" with Discard (red) or Keep editing.
- 按 Esc、切換分頁、按瀏覽器上一頁也會跳這個確認。重新整理或關掉分頁則是瀏覽器自己的提示。Esc, switching tabs and the browser Back button all raise the same prompt. Reloading or closing the tab raises the browser's own.
- 存檔進行中,Cancel 不能按。While a save is in flight, Cancel is disabled.
點左側選單離開,不會跳確認 —— 填的內容會直接不見。Leaving via the sidebar raises no prompt — what you typed is simply lost.
Received EventsReceived Events
列出系統收到的每一種事件名稱,不管有沒有定義成 conversion。還沒定義的可以在這裡直接變成 conversion,也可以忽略它。Lists every event name the system has received, defined or not. Undefined ones can be turned into a conversion here, or ignored.
目前這個階段(Phase 1)還沒有接上事件來源,所以大多只會看到已定義的 conversion。At this stage (Phase 1) no event source is connected yet, so mostly you will only see conversions you already defined.
| 欄位Column | 意思Meaning |
|---|---|
| Incoming event | 事件名稱。點 Declared 的名稱會跳到它對應的 conversion。The event name. Clicking a Declared one jumps to its conversion. |
| Count (7d) | 往回滾動 7×24 小時收到的次數。Received in the trailing 7×24 hours. |
| Last received | 所有時間裡最後一次收到,不只看 7 天。顯示 just now / N min ago / N hr ago / N days ago,滑過去看實際時間。從沒收過顯示「—」。The most recent arrival ever, not just within 7 days. Shows just now / N min ago / N hr ago / N days ago; hover for the exact time. Never received shows an em dash. |
Count (7d) 跟 Define 頁的「Last 7 days」算法不同 —— 一個是滾動 7×24 小時,一個是 7 個日曆天。兩邊數字可能對不起來,這是正常的。Count (7d) and Define's "Last 7 days" are computed differently — a trailing 7×24 hours versus seven calendar days. They can disagree, and that is expected.
Status 三種狀態The three statuses
- Declared(綠):已經有同名的 conversion。Declared (green): a conversion with the same name already exists.
- Undeclared(橘,整列黃底):有收到,但還沒有定義。Undeclared (amber, row highlighted): received but not yet defined.
- Ignored(灰):有人手動按了 Ignore。Ignored (grey): someone pressed Ignore by hand.
Ignored 不是「通話秒數不夠」的意思。秒數不夠的通話根本不會產生事件,也不會出現在這裡。(Details 頁的說明文字這點寫錯了。)Ignored does not mean "the call was too short". A call below the threshold produces no event at all and never appears here. (The Details page's help text gets this wrong.)
操作:Declare → 和 Ignore 只有 Undeclared 有;Un-ignore 只有 Ignored 有。Ignore 沒有確認視窗,按下去就變了。Declared 的事件沒有任何操作,也不能 Ignore。Actions: Declare → and Ignore appear only on Undeclared rows; Un-ignore only on Ignored ones. Ignore has no confirmation — one click and it is done. Declared rows have no actions and cannot be ignored.
搜尋與 Refresh:搜尋只在已經抓下來的資料裡篩選,不分大小寫、部分符合就算。Refresh 重新抓資料並更新「Updated …」時間。最多顯示 200 個事件名稱,超過會出現提示,而且搜尋和排序也只作用在這 200 個裡。Search and Refresh: search filters what has already been fetched, case-insensitively, on partial matches. Refresh re-fetches and updates the "Updated …" time. At most 200 event names are shown; beyond that a notice appears, and search and sorting only act on those 200.
來源:同事提供的 Conversion Tracking 說明(2026-10-06),逐條對照後整理。相關畫面見介面導覽的 Conversions 面板;把轉換送到 Google 見Google Offline Conversions。Source: a colleague's Conversion Tracking write-up (2026-10-06), reorganised point by point. For the screens see the Conversions panel in the interface tour; for sending conversions to Google see Google Offline Conversions.