SW Manager
SW Manager 介面導覽SW Manager interface tour
下面是 SW Manager(ContactLoop Manager)登入後的畫面。點左邊的選單或上方的組織 / 帳號切換器,右邊會換成那一項的說明。SW 的左側選單會依「目前的範圍」不同 —— 可以用上方三個按鈕切換看看。畫面以內部人員(系統管理員)的視角呈現:🚩 是功能旗標控制的項目(旗標沒開時客戶看不到),🔒 是只有系統管理員看得到。Below is SW Manager (ContactLoop Manager) after sign-in. Click the left menu or the organization / account switcher at the top and the right side switches to that item's explanation. SW's left menu depends on the current scope — try the three buttons above it. The view is what internal staff (system admins) see: 🚩 marks feature-flag gated items (customers don't see them while the flag is off), 🔒 marks system-admin-only items.
組織 / 帳號切換器(頂部)Organization / account switcher (top bar)
SW 最重要的開關。它是兩行字:上面小字是組織,下面大字是帳號(或「All Accounts」)。點上面的切換器試試看(假資料)。SW's most important switch. Two lines: the small top line is the organization, the big line is the account (or "All Accounts"). Try the switcher above (sample data).
| 操作Action | 會發生什麼What happens |
|---|---|
| 點下面那行 → 選一個帳號Click the big line → pick an account | 範圍變成單一帳號,左側是完整的帳號選單。會留在目前這頁(詳細頁或組織彙總頁除外,那兩種會回首頁)。清單只列啟用中與範本帳號(綠點 = 啟用、橘點 = 範本)。Scope becomes one account with the full account menu. You stay on the current page (except detail pages and org roll-ups, which go home). Only enabled and template accounts are listed (green dot = enabled, amber = template). |
| All {Org} Accounts | 範圍變成組織(All Accounts),回到首頁;Contacts、Actions 只剩組織彙總那一項。Scope becomes organization (All Accounts) and you go home; Contacts and Actions keep only their org roll-up. |
| 點上面那行 → 換組織Click the top line → switch organization | 只有屬於多個組織的人才點得開。換組織後會停在那個組織的 All Accounts。Only clickable for people in more than one organization. Switching lands on that organization's All Accounts. |
「所有組織」不在這個切換器裡:系統管理員要點左側的 Admin 群組才會進到 Admin(所有組織)範圍,這時切換器會變成不能點的「Admin — All Organizations」。一般客戶沒選組織時,系統會自動幫他選一個。
「我的選單比同事少幾項」通常是範圍或角色不同,不是 bug:左側選單會依目前的範圍、角色和功能旗標變動。"All organizations" isn't in this switcher: system admins reach the Admin (All Organizations) scope through the left Admin group, and the switcher then becomes a static "Admin — All Organizations". A regular customer without an organization selected gets one picked automatically.
"My menu has fewer items than my colleague's" is usually a scope or role difference, not a bug: the left menu changes with the scope, roles and feature flags.
使用者選單(右上)User menu (top right)
點頭像會打開帳號選單:上方是名字與 email,中間列出「Your organization(s)」—— 點一個就換組織,目前的那個有打勾;最下面是紅色的 Sign out。Profile 不在這裡,在左側選單。頭像旁邊的 ⚙ 可以切換「收合側欄」「深色側欄」「深色模式」。🔔 通知目前永遠是空的。Clicking the avatar opens the account menu: name and email at the top, "Your organization(s)" in the middle — click one to switch, the current one is checked — and a red Sign out at the bottom. Profile isn't here; it's in the left menu. The ⚙ next to it toggles "Collapsed sidebar", "Dark sidebar" and "Dark mode". 🔔 notifications are currently always empty.
Home(單一帳號)Home (one account)
/● Acme - Auto Insurance
in Acme09/30/2026 · ● Updated just now1Contacts received
7D14D30DNewest Contacts
Sam Sample
Segment Report · Acme - Auto Insurance (ID: 101) 2
Status:Enabled| Segment Name | Status | Type | Delay Value | Delay Unit | Business Hour | TCPA | Holiday |
|---|---|---|---|---|---|---|---|
| New lead SMS | Enabled | SMS | 0 | minutes | ✓ | ✓ | ✓ |
▲ 模擬畫面(假資料)▲ Mock screen (sample data)
- 1
首頁的標題會跟著範圍變:單一帳號時顯示帳號名稱與所屬組織(點組織名稱可以回到 All Accounts)。下面是今天的三個數字(新聯絡人、簡訊送出、主動撥號)、近 14 天收到的聯絡人(可切 7D / 30D)與最新聯絡人,還有各帳號的活動與互動漏斗。還沒有任何聯絡人時,會改成「No contacts yet」的引導畫面(手動匯入或設定 API 匯入)。The home title follows the scope: with one account it shows the account and its organization (click the org to return to All Accounts). Below: today's three numbers (new contacts, SMS sent, active dials), contacts received over 14 days (7D / 30D toggle) and the newest contacts, plus account activity and the engagement funnel. With no contacts yet it becomes a "No contacts yet" guide (import manually or set up API import).
- 2
Segment Report 只在單一帳號時出現:列出這個帳號的每個 Segment 會在什麼延遲後觸發、是否遵守營業時間 / TCPA / 假日。可以用 Status 篩選,點進去直接編輯 Segment。The Segment Report only appears for a single account: each segment's trigger delay and whether it honors business hours / TCPA / holidays. Filter by Status and edit a segment in place.
這是新版首頁。還在舊版的環境會看到 Actions / Customers / Segments / Opens 四張數字卡(數字是示意用)。This is the new home page. Environments still on the old version show four stat cards — Actions / Customers / Segments / Opens (placeholder numbers).
Home(組織 / All Accounts)Home (organization / All Accounts)
/?organization_id=…All Accounts
3 accounts in AcmeAccount activity 1
TodayYesterdayLast 7d| Account | Contacts | SMS sent | Active dials |
|---|---|---|---|
| Acme - Auto Insurance | 124 | 980 | 310 |
| Acme - Home Insurance | 177 | 1,430 | 410 |
| All accounts | 301 | 2,410 | 720 |
▲ 模擬畫面(假資料)▲ Mock screen (sample data)
- 1
組織範圍的首頁把底下所有帳號加總,Account activity 會多一列「All accounts」總計。沒有 Segment Report(那只在單一帳號時才有)。一般客戶第一次登入時,預設就是第一個組織的這個畫面。At organization scope the home page totals every account, and Account activity gains an "All accounts" total row. There's no Segment Report (single-account only). A customer's first sign-in defaults to this view of their first organization.
Dashboard(Admin — 所有組織)Dashboard (Admin — All Organizations)
/adminAll organizations
2 organizations| Organization ↕ | Accounts ↕ | New contacts ▼ | SMS sent ↕ | Active dials ↕ |
|---|---|---|---|---|
| Acme | 3 | 301 | 2,410 | 720 |
| Sunrise | 1 | 219 | 1,690 | 460 |
▲ 模擬畫面(假資料)。Card / List 可以切換。▲ Mock screen (sample data). Card / List are switchable.
- 1
系統管理員看全平台的首頁:每個組織一張卡(或切成清單,會記住你的選擇),點「Open organization →」就進到那個組織的 All Accounts。只有系統管理員進得來,其他人打這個網址會看到「只有系統管理員能看這頁」。The platform-wide home for system admins: one card per organization (or a list — your choice is remembered); "Open organization →" jumps into that organization's All Accounts. Only system admins can open it; anyone else visiting the URL sees "only system administrators can view this page".
要離開 Admin 範圍,點左上角的 logo 回首頁(會重新載入並回到你原本的範圍)。To leave the Admin scope, click the logo at top left (it reloads and returns you to your previous scope).
Messenger
/messengerCL Messenger — conversation history
在新分頁開啟 CL Messenger(SSO 自動登入),直接跳到這個帳號的 Conversations。Opens CL Messenger in a new tab (SSO sign-in), jumping to this account's Conversations.
Open CL Messenger ↗1▲ 模擬畫面▲ Mock screen
- 1
這頁不會在 SW 裡顯示對話,只是一個按鈕:另開分頁到 Ava Messenger。帳號有 Ava 的 App Integration 時會直接到這個帳號的對話列表,沒有就到 Messenger 首頁。要在 SW 裡直接看對話,用 Unified Activity。對話頁本身的說明見 Ava → Conversations。This page doesn't show conversations inside SW — it's just a button that opens Ava Messenger in a new tab: the account's conversation list if it has an Ava App Integration, otherwise the Messenger home. To read conversations inside SW, use Unified Activity. For the conversation page itself see Ava → Conversations.
這個環境要有設定 Messenger 連線、而且旗標開了(或你是內部人員)才會出現;沒設定時頁面會顯示「CL Messenger link is not configured for this environment」。Only appears when the environment has Messenger configured and the flag is on (or you're internal staff); without configuration the page says "CL Messenger link is not configured for this environment".
Unified Activity
/unified-activityUnified Activity
▲ 模擬畫面▲ Mock screen
- 1
把 Ava Messenger 的 Conversations 用內嵌模式放進 SW,不用切換系統就能看對話(內容同 Ava 的 Conversations,內嵌方式見 Chromeless 內嵌與 SSO)。所有登入者都看得到。打不開時會顯示原因:環境沒設定 Messenger、讀不到這個帳號的 Messenger 設定、你的使用者沒有 email,或這個帳號還沒有 Ava 的 App Integration(要到 Settings / Admin → App Integrations 新增)。Embeds Ava Messenger's Conversations inside SW so you can read conversations without switching systems (same content as Ava's Conversations; embedding: Chromeless embed & SSO). Every signed-in user sees it. When it can't open it says why: Messenger not configured for the environment, the account's Messenger integration couldn't load, your user has no email, or the account has no Ava App Integration yet (add one under Settings / Admin → App Integrations).
Contacts NEW
/contacts-27Contacts
Last 7 daysSep 24, 2026 - Sep 30, 2026 ▾1| ID | First Name | Last Name | Phone Number | Zip Code | State | Created At | Sub ID 01 | Opt Out 6 | |
|---|---|---|---|---|---|---|---|---|---|
| 50215 | Alex | Demo | alex@example.test | +15550100001 | 90001 | CA | 09/30/2026 09:12 | fb-spring | OFF |
| 5020 | Sam | Sample | — | +15550100002 | 73301 | TX | 09/29/2026 16:48 | google-q3 | ON |
👆 上方的日期區間、Segment、Columns、Download 都可以點開,看看面板長什麼樣子(日期快選、分組樹、欄位清單、匯出選單)。The date range, Segment, Columns and Download above can all be opened to see their panels (date presets, group-by tree, column list, export menu).
▲ 模擬畫面(假資料)▲ Mock screen (sample data)
- 1
現在主要的聯絡人頁面。右上的日期區間只看「建立時間」落在區間內的聯絡人:有 Today、Last 7 days、This month 等快選,也可以自己點日期再按 Apply;會記住上次的選擇,沒有記錄時預設 Today。The main contacts page now. The date range at top right only shows contacts created within it: presets such as Today, Last 7 days, This month, or pick dates and press Apply; your last choice is remembered, defaulting to Today.
- 2
分頁就是存好的「檢視」(View):點一下就套用那個檢視的分組和欄位。最多顯示 3 個,其他收在 More。Tabs are saved views: click one to apply its grouping and columns. Up to 3 show; the rest go under More.
- 3
Filter contacts 打開篩選列:Phone、Email、Name、External Lead ID、Traffic Source、Publisher Name、Created / Returned Date。用 Email、Phone、External Lead ID 找人時會忽略日期區間(會提示「searching all dates」);其他欄位找不到時,注意畫面會提醒「區間外建立的聯絡人不會出現」,可以按 Search all dates。Loaded X / Y 是已載入 / 總數;Y 剛好是 10,000 時表示可能被截斷,可以調大 Rows。Filter contacts opens the filter row: Phone, Email, Name, External Lead ID, Traffic Source, Publisher Name, Created / Returned Date. Searching by Email, Phone or External Lead ID ignores the date range ("searching all dates"); for other fields, a notice warns that contacts created outside the range won't appear — press Search all dates. Loaded X / Y is loaded / total; a Y of exactly 10,000 may be capped — raise Rows.
- 4
Segment = 分組(不是 Configuration 裡的 Segments):勾選的順序就是分組層級(G1、G2…),可以依時間、行銷來源(UTM、Sub ID、Vendor)、端點屬性(電信商、線路類型)、裝置、地區分組。Download 可以匯出摘要(要先分組)或明細。帳號沒開 Phone Verification 時,電信商、線路類型會都變成 Unspecified。Segment = group by (not the Segments under Configuration): the order you tick sets the levels (G1, G2…) — by time, marketing source (UTM, Sub ID, Vendor), endpoint attributes (carrier, line type), device, or geography. Download exports a summary (needs grouping) or detail. Without Phone Verification on the account, carrier and line type all show as Unspecified.
- 5
點 ID 開啟聯絡人詳細資料(基本資料與 Custom Data)。Click an ID for the contact's details (general info and Custom Data).
- 6
Opt Out 可以直接切換(部分人才有權限),會先確認;opt out 之後就不會再發任何訊息給這個聯絡人。注意 opt out 是蓋在「這一筆聯絡人」上,同一支電話重新匯入會是新的一筆。Opt Out can be toggled here (some people only) after confirming; once opted out, nothing more is sent to the contact. Note it's stamped on this contact record — the same phone imported again becomes a new record.
- 7
View Configurator:選一個存好的檢視套用,或把目前的分組和欄位存成檢視(存檔、刪除、匯入只有系統管理員能做;存的檢視整個帳號共用)。Tabs ▾ 決定哪些檢視顯示成上方分頁。View Configurator: apply a saved view, or save the current grouping and columns as one (saving, deleting and importing are system-admin only; saved views are shared across the account). Tabs ▾ chooses which views appear as tabs.
🔎 上面那行 Loaded N / N 與 Refresh 不是每次都在 —— 什麼時候會消失見功能說明:表格的載入模式The Loaded N / N and Refresh strip is not always present — when it disappears: How the grids load their rows
開了伺服器端載入的旗標時,表格改成捲動時分段載入,Loaded / Rows 這兩個控制會消失。With the server-side loading flag on, the grid loads in blocks as you scroll and the Loaded / Rows controls disappear.
Marketing Sources
/contacts-marketing-sourcesMarketing Sources
Last 7 daysSep 24, 2026 - Sep 30, 2026 ▾| Sub ID 01 | ID | First Name | Last Name | Phone Number | Created At | Opt Out | |
|---|---|---|---|---|---|---|---|
| ▸ fb-spring (120) | |||||||
| ▸ google-q3 (85) |
▲ 模擬畫面(假資料)▲ Mock screen (sample data)
- 1
跟 Contacts 是同一張表格,但一開始就帶好 7 個分頁,每個分頁依一種行銷來源分組:Sub ID 01、Vendor、Site Placement、UTM Medium / Source / Campaign / Term(前 3 個直接顯示,其他在 More)。分組預設收合,依數量由多到少排。The same grid as Contacts, but it starts with 7 tabs, each grouping by one marketing source: Sub ID 01, Vendor, Site Placement, UTM Medium / Source / Campaign / Term (first 3 shown, the rest under More). Groups start collapsed, sorted by count.
- 2
View Configurator 的頁面標籤是「Marketing Sources」:這頁的檢視跟 Contacts 分開存。The View Configurator page tag reads "Marketing Sources": this page keeps its own saved views, separate from Contacts.
Endpoint Attributes
/contacts-endpoint-attributesEndpoint Attributes
Last 7 daysSep 24, 2026 - Sep 30, 2026 ▾| ID | First Name | Last Name | Phone Number | Created At | Opt Out | |
|---|---|---|---|---|---|---|
| 5021 | Alex | Demo | alex@example.test | +15550100001 | 09/30/2026 09:12 | OFF |
| 5020 | Sam | Sample | — | +15550100002 | 09/29/2026 16:48 | OFF |
▲ 模擬畫面(假資料)▲ Mock screen (sample data)
- 1
跟 Contacts 是同一張表格,沒有預設分頁也沒有預設分組:一打開就是一般的聯絡人清單。要按右邊的 Segment,選電信商(Carrier)、線路類型、Litigator Risk、Email 服務商、Email 驗證來分組。專屬欄位還在開發中,目前欄位跟 Contacts 一樣。The same grid as Contacts with no starter tabs and no default grouping: it opens as a plain contact list. Press Segment on the right and pick Carrier, Phone Line Type, Litigator Risk, Email Provider, Email Verification to group. Dedicated columns are still in development, so the columns match Contacts for now. 分組怎麼選見 Contacts 的 ④ Segment 說明。For how to pick groupings see ④ Segment on Contacts.
- 2
View Configurator 的頁面標籤是「Endpoint Attributes」,檢視分開存。分好組之後可以存成檢視,再用 Tabs ▾ 讓它出現在上方分頁。The View Configurator page tag reads "Endpoint Attributes" and views are stored separately. Save a grouping as a view, then use Tabs ▾ to show it as a tab.
Technographics
/contacts-technographicsTechnographics
Last 7 daysSep 24, 2026 - Sep 30, 2026 ▾| ID | First Name | Last Name | Phone Number | Created At | Opt Out | |
|---|---|---|---|---|---|---|
| 5021 | Alex | Demo | alex@example.test | +15550100001 | 09/30/2026 09:12 | OFF |
| 5020 | Sam | Sample | — | +15550100002 | 09/29/2026 16:48 | OFF |
▲ 模擬畫面(假資料)▲ Mock screen (sample data)
- 1
跟 Contacts 是同一張表格,沒有預設分頁也沒有預設分組:一打開就是一般的聯絡人清單。要按右邊的 Segment,選裝置類型、作業系統、瀏覽器、裝置品牌、版本來分組。專屬欄位還在開發中,目前欄位跟 Contacts 一樣。The same grid as Contacts with no starter tabs and no default grouping: it opens as a plain contact list. Press Segment on the right and pick device type, OS, browser, device brand, versions to group. Dedicated columns are still in development, so the columns match Contacts for now. 分組怎麼選見 Contacts 的 ④ Segment 說明。For how to pick groupings see ④ Segment on Contacts.
- 2
View Configurator 的頁面標籤是「Technographics」,檢視分開存。分好組之後可以存成檢視,再用 Tabs ▾ 讓它出現在上方分頁。The View Configurator page tag reads "Technographics" and views are stored separately. Save a grouping as a view, then use Tabs ▾ to show it as a tab.
Import Contact ↗
/contacts/importImport Contact ⓘ
alex@example.test 5550100001 Alex Demo
▲ 模擬畫面(假資料)▲ Mock screen (sample data)
- 1
另開分頁。不是上傳檔案,是把資料「貼」進文字框:第一列是欄位名稱,之後一列一筆。可以匯入的欄位按這顆看(email 或 phone 至少要有一個;還有姓名、地址、opt out、UTM 等)。Opens in a new tab. It's not a file upload — you paste data into the text box: the first line is the column names, then one contact per line. This button lists the importable fields (email or phone is required; also names, address, opt out, UTM, etc.).
- 2
選欄位之間用什麼分隔:Tab(預設)、逗號、空白,或 More... 自訂。Pick the separator: Tab (default), comma, space, or a custom one via More....
- 3
會匯入到目前選的帳號。成功顯示「imported N contacts」;有錯會列出「Line N: 原因」。範本帳號在某些設定下看不到這一項。Imports into the currently selected account. Success shows "imported N contacts"; errors list "Line N: reason". Template accounts may not see this item under some settings.
🔎 畫面匯入和客戶走的 API 不一樣 —— 完整比較見功能說明:聯絡人怎麼進到系統The import screen and the customer-facing API behave differently — full comparison: How contacts get into the system
API ↗
/doc/contacts-v2另開分頁到「新增聯絡人」的 API 文件,跟 Documentation → Contact 是同一頁。Opens the "add contact" API documentation in a new tab — the same page as Documentation → Contact.
Contacts (old) LEGACY
/contacts| ID | First Name | Phone | Opt Out | Publisher | Created At | Operations | |
|---|---|---|---|---|---|---|---|
| 5021 | Alex | alex@example.test | +15550100001 | OFF | N/A | 09/30/2026 9:12 AM | DetailsDelete |
▲ 模擬畫面(假資料)▲ Mock screen (sample data)
- 1
舊版聯絡人頁,新人請用上面的 Contacts。還有新版頁時才會叫「(old)」;沒開新版的客戶看到的「Contacts」就是這頁。這裡可以依 SMS 事件(送達、點擊、回覆)進階搜尋、刪除聯絡人。匯出 CSV 資料量大時會改成背景產生,要到 Batch Jobs 下載。The old contacts page — new hires should use Contacts. It's called "(old)" only while the new page exists; customers without the new page see this as "Contacts". It supports advanced search by SMS events (delivered, clicked, replied) and deleting contacts. Large CSV exports are generated in the background — download them from Batch Jobs.
Contacts (All Account)
/contacts-orgContacts · All accounts
3 accounts in Acme · as of 10:05Refresh▲ 模擬畫面(假資料)▲ Mock screen (sample data)
- 1
組織範圍下 Contacts 只剩這一項:內部用的彙總頁,每個帳號一張卡,顯示新聯絡人數與 30 天趨勢。點圖上的某一天或「View contacts →」會跳到那個帳號的 Contacts。只有系統管理員看得到。沒有選組織時叫「Contacts (All Orgs)」,會涵蓋你看得到的所有帳號。At organization scope Contacts has only this item: an internal roll-up with one card per account showing new contacts and a 30-day trend. Click a day on the chart or "View contacts →" to jump to that account's Contacts. System admins only. Without an organization selected it's called "Contacts (All Orgs)" and covers every account you can see.
Actions
/actionsActions
TodaySep 30, 2026 - Sep 30, 2026 ▾1| DateChannel / AssetHour | Action Started | First SMS Sent | Delivered % | Responses % | CTR % 4 | Transfers |
|---|---|---|---|---|---|---|
| ▸ 2026-09-30▸ SMS · Ava▸ 09:00 | 1,240 | 1,180 | 96.10 % | 18.20 % | 11.40 % | 62 |
| Total: Filtered ⓘ 5 | 1,240 | 1,180 | 96.10 % | 18.20 % | 11.40 % | 62 |
| Total: Date range ⓘ | 1,310 | 1,240 | 95.80 % | 17.90 % | 11.10 % | 65 |
👆 上方的日期區間、Segment、Columns、Download 都可以點開看面板;Segment 勾選後按鈕會顯示 Segment (N),Download 的 Export summary 要有分組才能按。The date range, Segment, Columns and Download above can be opened; ticking Segment shows Segment (N), and Export summary under Download needs a grouping.
▲ 模擬畫面(假資料)。上方分頁可以切換。▲ Mock screen (sample data). The tabs above are switchable.
- 1
每個 Action / Asset 的簡訊與通話成效報表。日期區間預設是 Today(會記住上次的選擇)。An SMS and call performance report per action / asset. The date range defaults to Today (your last choice is remembered).
- 2
分頁是預設好的分組:All Actions(依日期)、By Channel(依頻道再依 Asset)、By Day of Week、By Hour、By Site Placement、By SubID。組織範圍會多一個 By Account(點帳號就進到那個帳號)。Tabs are preset groupings: All Actions (by date), By Channel (channel then asset), By Day of Week, By Hour, By Site Placement, By SubID. Organization scope adds By Account (click an account to drill in).
- 3
Segment = 自己選分組(時間、Action、頻道、行銷來源、端點、裝置),Actions 一定會有分組,Reset 回到預設。Download 可匯出摘要或明細;在伺服器端載入模式下 Download 會是灰的。Segment = choose your own grouping (time, action, channel, marketing source, endpoint, device); Actions is always grouped, and Reset restores the default. Download exports summary or detail; it's grayed out in server-side loading mode.
- 4
欄位分組:General、SMS(送出、送達、回覆、連結、轉接、各種錯誤)、Total Call、Active Dial、Scheduled Call、Inbound Call…。欄位標題滑過去有定義,例如 CTR % = 點擊 ÷ 連結送達。轉接相關數字怎麼來,見 Ava 的 Transfer。Column groups: General, SMS (sent, delivered, responses, links, transfers, error types), Total Call, Active Dial, Scheduled Call, Inbound Call…. Hover a header for its definition, e.g. CTR % = clicked ÷ link delivered. For where transfer numbers come from, see Ava Transfer.
- 5
Total: Filtered 只算目前啟用中的 Action;Total: Date range 算區間內所有 Action(含已停用)。所以 Filtered 通常比較小,差的是停用的 Action,不是資料不見。日期區間太大時表格會被截斷(會有不能關的警告):每列的數字是「至少」,百分比可能偏高或偏低,但這兩列總計是準確的 —— 要看完整的就縮小區間。Total: Filtered counts only active actions; Total: Date range counts every action in the range (including disabled). Filtered is usually lower — the gap is disabled actions, not missing data. Large date ranges truncate the table (with a warning you can't close): row counts are lower bounds and percentages can be off, but these two totals stay exact — narrow the range to see everything.
- 6
View Configurator:選存好的檢視套用,或把目前的分組和欄位存成檢視(存檔、刪除、匯入只有系統管理員能做);Tabs ▾ 決定哪些檢視顯示成上方分頁。每個 Actions 系列頁面的檢視都分開存。View Configurator: apply a saved view or save the current grouping and columns as one (saving, deleting and importing are system-admin only); Tabs ▾ chooses which views appear as tabs. Each page in the Actions family keeps its own views.
🔎 Actions 系列的報表頁沒有 Loaded N / N 與 Refresh,那是刻意的 —— 原因見功能說明:表格的載入模式Actions report pages deliberately have no Loaded N / N or Refresh — why: How the grids load their rows
組織範圍下這一項叫「Actions (All Account)」,標題變成「Actions · All accounts」。At organization scope this item is called "Actions (All Account)" and the heading reads "Actions · All accounts".
Marketing Sources
/actions-marketing-sourcesMarketing Sources
TodaySep 30, 2026 - Sep 30, 2026 ▾| Sub ID 01 | Action Started | First SMS Sent | Delivered % | Responses % | CTR % | Transfers |
|---|---|---|---|---|---|---|
| ▸ fb-spring | 720 | 690 | 96.50 % | 19.10 % | 12.30 % | 38 |
| ▸ google-q3 | 520 | 490 | 95.60 % | 17.00 % | 10.20 % | 24 |
| Total: Filtered ⓘ | 1,240 | 1,180 | 96.10 % | 18.20 % | 11.40 % | 62 |
| Total: Date range ⓘ | 1,240 | 1,180 | 96.10 % | 18.20 % | 11.40 % | 62 |
▲ 模擬畫面(假資料)▲ Mock screen (sample data)
- 1
跟 Actions 同一張報表,但一開始就帶好 7 個分頁,每個依一種行銷來源分組:Sub ID 01、Vendor、Site Placement、UTM Medium / Source / Campaign / Term。日期區間一樣預設 Today。The same report as Actions, but it starts with 7 tabs, each grouping by one marketing source: Sub ID 01, Vendor, Site Placement, UTM Medium / Source / Campaign / Term. The date range still defaults to Today.
- 2
下方的 Total: Filtered / Total: Date range 跟 Actions 一樣是準確的總計;檢視跟 Actions 分開存。Total: Filtered / Total: Date range are exact totals as on Actions; views are stored separately from Actions.
Endpoint Breakdowns
/actions-endpoint-attributesEndpoint Breakdowns
TodaySep 30, 2026 - Sep 30, 2026 ▾| Carrier | Action Started | First SMS Sent | Delivered % | Responses % | CTR % | Transfers |
|---|---|---|---|---|---|---|
| ▸ Verizon | 610 | 590 | 97.00 % | 18.60 % | 11.90 % | 31 |
| ▸ Unspecified | 630 | 590 | 95.20 % | 17.80 % | 10.90 % | 31 |
| Total: Filtered ⓘ | 1,240 | 1,180 | 96.10 % | 18.20 % | 11.40 % | 62 |
| Total: Date range ⓘ | 1,240 | 1,180 | 96.10 % | 18.20 % | 11.40 % | 62 |
▲ 模擬畫面(假資料)▲ Mock screen (sample data)
- 1
跟 Actions 同一張報表,沒有預設好的分頁,用右邊的 Segment 選要依哪個維度分組:電信商、線路類型、Litigator Risk、Email 服務商、Email 驗證。Litigator Risk 與兩個 Email 欄位在後端建好索引前會顯示 Unspecified;沒開 Phone Verification 時,電信商與線路類型也會是 Unspecified。The same report as Actions with no starter tabs; use Segment on the right to choose the dimension: carrier, line type, Litigator Risk, email provider, email verification. Litigator Risk and the two email dimensions show Unspecified until the backend indexes them; without Phone Verification, carrier and line type are Unspecified too. 分組怎麼選見 Actions 的 ③ Segment 說明。For how to pick groupings see ③ Segment on Actions.
- 2
View Configurator 的頁面標籤是「Endpoint Breakdowns」,檢視分開存;分好組之後可以存成檢視、設成分頁。The View Configurator page tag reads "Endpoint Breakdowns"; save a grouping as a view and show it as a tab.
Technographics
/actions-technographicsTechnographics
TodaySep 30, 2026 - Sep 30, 2026 ▾| Device Type | Action Started | First SMS Sent | Delivered % | Responses % | CTR % | Transfers |
|---|---|---|---|---|---|---|
| ▸ Mobile | 880 | 840 | 96.40 % | 18.90 % | 12.00 % | 45 |
| ▸ Unspecified | 360 | 340 | 95.30 % | 16.80 % | 9.80 % | 17 |
| Total: Filtered ⓘ | 1,240 | 1,180 | 96.10 % | 18.20 % | 11.40 % | 62 |
| Total: Date range ⓘ | 1,240 | 1,180 | 96.10 % | 18.20 % | 11.40 % | 62 |
▲ 模擬畫面(假資料)▲ Mock screen (sample data)
- 1
跟 Actions 同一張報表,沒有預設好的分頁,用右邊的 Segment 選要依哪個維度分組:裝置類型、作業系統、瀏覽器與版本、裝置品牌。資料來自瀏覽器的 User-Agent,只會從開始收集之後才有,以前的 Action 會一直是 Unspecified。The same report as Actions with no starter tabs; use Segment on the right to choose the dimension: device type, OS, browser and versions, device brand. Data comes from the browser User-Agent and is only captured going forward — older actions stay Unspecified. 分組怎麼選見 Actions 的 ③ Segment 說明。For how to pick groupings see ③ Segment on Actions.
- 2
View Configurator 的頁面標籤是「Technographics」,檢視分開存;分好組之後可以存成檢視、設成分頁。The View Configurator page tag reads "Technographics"; save a grouping as a view and show it as a tab.
Action Deep Dive
/actions-deep-diveAction Deep Dive
TodaySep 30, 2026 - Sep 30, 2026 ▾| Date | action_id 1 | asset_id | Asset Name | Action Started | First SMS Sent | Delivered % | Responses % | CTR % | Transfers |
|---|---|---|---|---|---|---|---|---|---|
| ▸ 2026-09-30 | — | — | — | 1,240 | 1,180 | 96.10 % | 18.20 % | 11.40 % | 62 |
| Total: Filtered ⓘ | — | — | — | 1,240 | 1,180 | 96.10 % | 18.20 % | 11.40 % | 62 |
| Total: Date range ⓘ | — | — | — | 1,240 | 1,180 | 96.10 % | 18.20 % | 11.40 % | 62 |
▲ 模擬畫面(假資料)▲ Mock screen (sample data)
- 1
跟 Actions 完全一樣(同樣的分頁、日期預設 Today),只差所有欄位預設全部打開,連 action_id、asset_id 這類 ID 欄位都會顯示,適合要一次看全部數字或對資料的時候。Identical to Actions (same tabs, date defaults to Today) except every column is shown by default, including ID columns such as action_id and asset_id — for when you want all the numbers or need to match data.
- 2
檢視跟 Actions 分開存。Saved views are kept separately from Actions.
Action Report
/reports/actionAction Report ⓘ
| Date / Action / Asset | First SMS Sent | Delivered % | CTR % |
|---|---|---|---|
| ▸ 2026-09-30 / New lead SMS / Asset: Welcome A ▾ 3 | 640 | 96.40 % | 12.10 % |
▲ 模擬畫面(假資料)。Hourly / Daily / Weekly / Monthly 可以切換。▲ Mock screen (sample data). Hourly / Daily / Weekly / Monthly are switchable.
- 1
舊式的 Action 報表(新版請用 Actions)。先選時間單位,每種單位有自己的快選區間(預設 Daily / Today);+ 可以存自己的區間。The older action report (the new one is Actions). Pick an interval first; each has its own range shortcuts (default Daily / Today); + saves your own range.
- 2
Group by 預設 Asset(依日期 → Action → Asset),也可以依 Action、Publisher、Tags、電信商、線路類型、Sub ID 01。預設只看啟用中的。Group by defaults to Asset (date → action → asset), or Action, Publisher, Tags, carrier, line type, Sub ID 01. Active only by default.
- 3
跟新版不同,這裡點 Action / Asset 名稱的下拉,可以直接 Edit Action / Edit Asset / Edit Segment。Unlike the new report, the dropdown on an action / asset name lets you Edit Action / Edit Asset / Edit Segment directly.
Contact Report
/reports/contact| Date | Counts |
|---|---|
| Tag | Counts |
| Date / Tag | Counts |
| 2026-09-30 | 301 |
▲ 模擬畫面(假資料)▲ Mock screen (sample data)
- 1
每天(或每週、每月)進來多少聯絡人,可以依 Tag 分組,也可以用自訂欄位設條件。日期區間預設是「Custom:近 7 天」。依 Date 時,點數字會另開分頁到那一天的 Contacts。How many contacts came in per day (or week / month), optionally grouped by tag and filtered by custom-field rules. The range defaults to "Custom: last 7 days". Grouped by Date, clicking a count opens that day's Contacts in a new tab.
Visitor Report
/reports/visitor畫面跟 Contact Report 一樣(Group by、Interval、Date Range),統計的是訪客數。注意:這頁的 Search Rules 條件不會被套用到查詢裡。The same screen as Contact Report (Group by, Interval, Date Range), counting visitors. Note: this page's Search Rules are not applied to the query.
Actions (All Account)
/actions組織範圍下 Actions 群組只剩這一項。報表跟 Actions 一樣,但標題是「Actions · All accounts」,而且最前面多一個 By Account 分頁:每個帳號一列,點帳號就切換到那個帳號的 Actions。New Contacts 這類「帳號 / 日期總數」欄位在跨帳號時會顯示「—」,要看請改用 By Account。At organization scope the Actions group has only this item. Same report as Actions, headed "Actions · All accounts", with an extra By Account tab first: one row per account; click to switch into that account's Actions. Account/date totals such as New Contacts show "—" across accounts — use By Account to see them.
Contacts by Org
/admin/contactsContacts by organization
Contacts — All organizations · Admin view · 2 organizations
▲ 模擬畫面(假資料)▲ Mock screen (sample data)
- 1
全平台各組織的新聯絡人趨勢,一個組織一張卡,依近 30 天由多到少排(不能改排序)。點「View this org's contacts →」進到那個組織的聯絡人彙總。New-contact trends for every organization, one card each, sorted by the last 30 days (fixed). "View this org's contacts →" opens that organization's contacts roll-up.
Actions by Org
/admin/actions跟 Actions 同一張報表(標題「Actions by organization」),預設分頁是 By Organization:一個組織一列,點組織名稱就進到那個組織。下方一樣有 Total: Filtered / Total: Date range 兩列總計。The same report as Actions (titled "Actions by organization"), opening on the By Organization tab: one row per organization; click a name to drill in. The Total: Filtered / Total: Date range footers are there too.
Organizations
/organizationsOrganizations
Create| ID | Name | Description | Accounts | Operations |
|---|---|---|---|---|
| 3 | Acme | Insurance group | 3 | EditAdd AccountDelete1 |
▲ 模擬畫面(假資料)▲ Mock screen (sample data)
- 1
管理組織與它底下有哪些帳號。一個帳號只能屬於一個組織:要把帳號搬到別的組織,要先到原本的組織把它移掉。Add Account 可以直接加帳號進來。Manage organizations and their accounts. An account can belong to only one organization: to move one, remove it from its current organization first. Add Account attaches accounts directly.
Feature Flags
/feature-flagsFeature Flags
| Name | Description | Enabled | Source | Operations |
|---|---|---|---|---|
example_feature_a | Example feature | ON1 | Stored | History |
example_feature_b | Example feature | OFF | Default2 | History |
▲ 模擬畫面(旗標名稱為示意)▲ Mock screen (flag names are placeholders)
- 1
切換會立刻影響所有使用者的實際行為。打開時會先跳出確認(關掉不會問)。History 看誰在什麼時候改過。Toggling changes live behavior for every user immediately. Turning one on asks for confirmation (turning off doesn't). History shows who changed it and when.
- 2
Source:Stored = 有存過值;Default = 還沒存過、用預設值;Unused = 程式已經沒在用。左側選單裡的 🚩 項目就是被這些旗標控制。Source: Stored = a value has been saved; Default = never saved, using the default; Unused = no longer used by the code. The 🚩 items in the left menu are controlled by these flags.
Org Maintenance
/organization-maintenanceOrganization Maintenance
Reconcile (preview)Reconcile (apply)Verify1| ID | Command | Status | Triggered by | Started | Finished | Output |
|---|---|---|---|---|---|---|
| 12 | reconcile dry run | ● Completed | User #4 | 2026-09-30 09:00 | 2026-09-30 09:01 | View |
▲ 模擬畫面(假資料)▲ Mock screen (sample data)
- 1
在伺服器上跑組織資料的整理 / 檢查。先跑 preview(只模擬、不寫入)看結果,再跑 apply;apply 會真的改資料而且無法從這裡復原,所以會再確認一次。執行中狀態每 2 秒更新,View 看輸出。Runs organization-data reconcile / verify jobs on the server. Run preview (dry run, no writes) first, then apply; apply really changes data and can't be undone from here, so it asks again. Running jobs refresh every 2 seconds; View shows the output.
Users
/usersUsers ⓘ
Create| ID | Name | Roles | Accounts 1 | Operations | |
|---|---|---|---|---|---|
| 4 | Demo Admin | admin@example.test | System Admin | 101 | Acme - Auto Insurance 102 | Acme - Home Insurance | Edit | Delete |
| 7 | Demo Viewer | viewer@example.test | User | No accounts | Edit | Delete |
▲ 模擬畫面(假資料)▲ Mock screen (sample data)
- 1
SW 的使用者(跟 Ava 的 Users 是分開的兩套)。建立時填姓名、Email、密碼、角色,再指定能看哪些帳號。有些帳號設定成「依組織指派」時,這裡改成選組織,帳號會自動繼承(唯讀)。SW users (separate from Ava's Users). Create with name, email, password and roles, then choose which accounts they can see. When the account is set up for organization assignment, you pick organizations instead and the accounts are inherited (read-only).
User Circles
/user-circlesUser Circles ⓘ
Create User Circle| ID | Name | Users Count | Users | Created At | Operations |
|---|---|---|---|---|---|
| 1 | QA team | 2 users | Demo Admin Demo Viewer | 09/01/2026 | EditDelete |
▲ 模擬畫面(假資料)▲ Mock screen (sample data)
把使用者分組的畫面工具,不帶任何系統權限 —— 加進某個 Circle 不會讓人多看到任何東西。建立時至少要選一位使用者。A UI tool for grouping users that carries no system permissions — joining a circle doesn't let anyone see more. At least one user is required.
Segments
/segmentsStandard Segments ⓘ 1
Create CampaignsImport Preset SegmentsBulk Import/Update SegmentsCreate| Actived | App | Segment Name | # Contacts | Rules 2 | Action | Operations |
|---|---|---|---|---|---|---|
| ON | Ava | New lead SMS | 1,204 | Must Include · Contact Field · Created At · Between 0 & 1 days ago | Welcome SMS | Options ▾3 |
Create Segment
▲ 模擬畫面(假資料)。可以切換「清單 / 建立」,建立畫面的 Type 也可以切換。▲ Mock screen (sample data). Switch between the list and Create; Type is switchable too.
- 1
Segment = 一組篩選聯絡人的規則 + 一個觸發設定 + 一個 Action:符合規則的聯絡人在設定的時間觸發 Action(例如發 Ava 簡訊)。頁面上方原本還有一張「Default Segment Trigger」,目前已經沒有在用,看到可以略過。A Segment = contact-matching rules + trigger settings + an Action: matching contacts fire the Action (e.g. an Ava SMS) at the configured time. The "Default Segment Trigger" card above it is no longer used — you can ignore it.
- 2
清單預設只顯示 Enabled;# Contacts 是目前符合規則的人數。Rules 欄用一行字寫出每條規則。The list shows Enabled only by default; # Contacts is how many currently match. The Rules column spells out each rule in one line.
- 3
點 Options ▾ 可以展開(滑過每一項有簡短說明):Edit Search(改篩選規則)、Edit Action(換要觸發的 Action)、Contact History(哪些聯絡人符合過)、Contact Export(匯出符合的聯絡人,量大時到 Batch Jobs 下載)、Preview Assets(實際會發出的訊息與字數,只有 SMS / Ava 的 Action 才有)、Copy Segment(複製成「名稱 - copy」)、Delete Segment(會先確認)。Copy 與 Delete 只有部分角色有。Click Options ▾ to open it (hover each item for a short hint): Edit Search (matching rules), Edit Action (which Action fires), Contact History (who matched), Contact Export (export matches; large ones download from Batch Jobs), Preview Assets (the real messages and length — SMS / Ava actions only), Copy Segment ("<name> - copy"), Delete Segment (asks first). Copy and Delete are limited to some roles.
- 4
每條規則:Exclude / Must Include / Or Include → 條件來源(Contact Field、Custom Field、Ava Event / Log、Call Log、SMS / Email Event)→ 欄位 → 比較方式與值。日期可以用「幾天前」(依聯絡人時區)或固定日期(依帳號時區)。Each rule: Exclude / Must Include / Or Include → source (Contact Field, Custom Field, Ava Event / Log, Call Log, SMS / Email Event) → field → operator and value. Dates can be "N days ago" (contact's time zone) or an absolute date (account's time zone).
- 5
Type:Immediate = 符合就觸發(可設延遲、一次或每天一次);Dependency = 等其他觸發跑完才跑;Scheduled(預設)= 在指定日期或星期幾跑。多個 Segment 同時符合時,Priority 高的勝出。Type: Immediate = fire on match (with delay, once or once a day); Dependency = run after other triggers; Scheduled (default) = run on a date or days of the week. When several segments match, the higher Priority wins.
- 6
是否遵守營業時間、TCPA(各州可撥打時段)、假日,預設都是 Follow。改成 Ignore 就會在這些時段照樣發送。Whether to honor business hours, TCPA (state calling hours) and holidays — all Follow by default. Ignore sends during those times anyway.
Assets
/assetsAssets ⓘ
ImportCreate| ID | Name | Type | Operations |
|---|---|---|---|
| 31 | Welcome A | Message | Edit2CopyAudit LogsDelete |
| 32 | Call now | Call | EditCopyAudit LogsDelete |
Edit Asset
✕Reply YES to get your quote.
▲ 模擬畫面(假資料)。可以切換「清單 / 按 Edit 之後」,Interaction Type 也可以切換。▲ Mock screen (sample data). Switch between the list and the Edit window; Interaction Type is switchable too.
- 1
Asset 是 Action 實際要發出去的內容。一個分頁 = 帳號的一個 App Integration,分頁名稱就是整合的名字;不同類型的整合,Edit 視窗裡的欄位也不同(SMS 要選發送號碼、Email 要主旨與範本編輯器…)。下面以 Ava 為例。An Asset is what an Action actually sends. Each tab = one of the account's App Integrations, named after it; the fields in the Edit window differ by integration type (SMS needs a source number, Email a subject and template editor…). Ava is shown below.
- 2
設定是在按 Edit(或 Create)後跳出的「Edit Asset」視窗裡做的,不是在清單頁上。點這個 Edit 或上方的「按 Edit 之後」可以看視窗。App Integration 在視窗裡是灰的,固定是目前這個分頁。Settings live in the "Edit Asset" window that opens from Edit (or Create), not on the list page. Click this Edit or "After pressing Edit" above to see it. App Integration is grayed out in the window — it's fixed to the current tab.
- 3
Interaction Type 決定這個 Asset 是發訊息還是打電話:Message = 發一則簡訊,要寫 Template,也可以看 Available Variables;Call = 讓 Ava 打電話,Template 和 Available Variables 都會消失,不用寫內容。從某個 Action 的頻道開啟時,Interaction Type 會被固定住、不能改。Interaction Type decides whether the Asset sends a message or makes a call: Message = send a text, with a Template and Available Variables; Call = have Ava place a call — Template and Available Variables disappear. When opened from an Action's channel, Interaction Type is locked.
- 4
Campaign 選單是即時向 Ava 查的:列出這個 App Integration 填的那個 Ava Account ID 底下、啟用中的 Campaign(有勾 Sandbox 就查 Sandbox),格式是「名稱 (ID: n)」,ID 是 Ava 那邊的 Campaign ID。所以:選單是空的,先檢查 App Integration 的 Account ID 填對沒、Ava 那邊有沒有啟用中的 Campaign;在 Ava 停用的 Campaign 不會出現在這裡。換了 App Integration,Campaign 會被清空要重選。The Campaign list is fetched live from Ava: the enabled campaigns under the Ava Account ID set on this App Integration (from Sandbox if Sandbox is ticked), shown as "name (ID: n)" with Ava's campaign ID. So if the list is empty, check the integration's Account ID and whether Ava has enabled campaigns; campaigns disabled in Ava don't appear. Changing the App Integration clears Campaign.
- 5
Template 裡可以用
{{first_name}}這類變數(按 Show Available Variables 看有哪些);下方即時顯示會拆成幾則簡訊、大約幾個字。Templates can use variables such as{{first_name}}(see Show Available Variables); below it shows how many SMS segments and roughly how many characters.
RCS Assets
/rcs-assetsRCS(富媒體簡訊)內容的編輯器,還在試作階段:要開 RCS 旗標才看得到,部分功能(例如 Send test)用的是模擬服務。可以做 Text + Quick Reply、Media、Rich Card、Carousel 四種,右邊有手機預覽;每則都必須手寫一個 SMS 備援內容,純文字的還要保留一個 Stop 按鈕,不然不能存。An editor for RCS (rich messaging) content, still a prototype: visible only with the RCS flag, and some parts (e.g. Send test) use a mock service. It supports Text + Quick Reply, Media, Rich Card and Carousel with a phone preview; every asset needs a hand-written SMS fallback, and text ones must keep a Stop chip, or it won't save.
App Integrations
/app-integrationsApp Integrations ⓘ
Create| ID | Name | Type | Operations 3 |
|---|---|---|---|
| 8 | Acme Ava | Ava | Edit4Delete |
| 9 | Acme SMS | Twilio | EditPhone NumbersDelete |
Create App Integration / Update App Integration
✕▲ 模擬畫面(假資料,憑證一律遮起來)。可以切換「清單 / 按 Create、Edit 之後」,Type 也可以切換。▲ Mock screen (sample data; credentials always masked). Switch between the list and the Create / Edit window; Type is switchable too.
- 1
把帳號接上外部服務(Ava、簡訊、Email、撥號、廣告名單、HTTP…)。Type 決定要填哪些欄位,建好後 Type 不能改。每個整合會在 Assets 成為一個分頁。Connects the account to outside services (Ava, SMS, email, dialers, ad audiences, HTTP…). Type decides which fields to fill, and can't be changed after creation. Each integration becomes a tab in Assets.
- 2
接 Ava 只要填 Ava 那邊的 Account ID(和要不要用 Sandbox),沒有 Campaign 對應的欄位 —— Campaign 是在建 Asset 時選。完整流程見 Ava → SW 建帳號流程。Connecting Ava only needs the Ava-side Account ID (and whether to use Sandbox); there's no campaign mapping field — the campaign is chosen when creating an Asset. Full walkthrough: Ava → SW setup.
- 3
有歷史資料的整合不能刪,按 Delete 會改成問你要不要「停用」(保留過去的報表,停止之後的執行)。Twilio / Plivo 有 Phone Numbers 可以看號碼與買號碼,Sendgrid 有 Settings 設定退訂。Integrations with history can't be deleted — Delete offers to disable it instead (keeping past reporting, stopping future runs). Twilio / Plivo have Phone Numbers to view and buy numbers; Sendgrid has Settings for unsubscribes.
- 4
設定是在按 Create 或 Edit 後跳出的視窗裡做的,不在清單頁上(點這個 Edit 或上方的切換鈕可以看)。編輯時 Type 是灰的不能改。Settings live in the window that opens from Create or Edit, not on the list page (click this Edit or the switch above). When editing, Type is grayed out.
AI Variables
/ai-variablesAI Variables
Search by variable name...Create| ID | Variable Name | Prompt | Used In | Created At | Operations |
|---|---|---|---|---|---|
| 2 | ai_customer_greeting | Write a one-line friendly greeting for… | 2 Asset(s) | 09/01/2026 | EditDelete |
▲ 模擬畫面(假資料)▲ Mock screen (sample data)
用 AI 產生訊息內容的變數:名稱一定要 ai_ 開頭,寫好 Prompt 和失敗時的備用文字(Fallback),就能在 Asset 範本裡用。Used In 顯示被哪些 Asset 用到。Test Render 可以挑帳號試跑看結果。Prompt 裡不能再放別的 AI 變數。Variables whose text is generated by AI: names must start with ai_; write a Prompt and a Fallback value, then use it in Asset templates. Used In shows which Assets use it. Test Render tries it against an account. A prompt can't contain other AI variables.
Custom Fields
/custom-fieldsCustom Fields
Create| ID | Name | Key | Data Type | Required 1 | Updated At | Operations |
|---|---|---|---|---|---|---|
| 4 | Sub ID 01 | sub_id_01 | Text | OFF | 09/01/2026 | EditDelete |
▲ 模擬畫面(假資料)▲ Mock screen (sample data)
- 1
聯絡人的額外欄位(會出現在 Contacts 的 Custom Data)。類型有 Text / Integer / Float / Date Time / Select。Required 打開的欄位,API 送聯絡人時沒帶就會失敗;Select 只接受事先定義的值(有設預設值時例外)。Key 和類型建好後都不能改。Extra contact fields (shown under Custom Data in Contacts). Types: Text / Integer / Float / Date Time / Select. With Required on, API contact posts without it fail; Select only accepts predefined values (unless a default is set). Key and type can't be changed later.
Holiday Settings
/holiday-settingsManage Global Holiday Settings
Holidays ReferenceCreate| ID | Name | Definition | Date | Type | Operations |
|---|---|---|---|---|---|
| 1 | Labor Day | First Monday of September, on Every Year | 2026-09-07 | Federal | EditDelete |
| 2 | Christmas | 25 December, on Every Year | 2026-12-25 | Federal | EditDelete |
▲ 模擬畫面(假資料)▲ Mock screen (sample data)
SW 全域的假日清單(跟 Ava Admin 的 Holiday Settings 是分開的)。每個假日用「每年固定日期」或「每年第幾個星期幾」定義,類型是全國(Federal)或指定州。SW's global holiday list (separate from Ava Admin's Holiday Settings). Each holiday is "a fixed date every year" or "the Nth weekday of a month", nationwide (Federal) or for chosen states.
TCPA Restrictions
/tcpa-restrictionsTCPA Restrictions
| ID | State | MON-FRI | SAT | SUN | Observed Holiday ⓘ |
|---|---|---|---|---|---|
| 1 | Example State | 8:00 am - 9:00 pm | 9:00 am - 8:00 pm | Calls Prohibited | Based on Call Restriction Rules |
▲ 模擬畫面(示意資料,不是實際規則)▲ Mock screen (illustrative, not the real rules)
各州可以撥打電話的時段,唯讀參考,不能在這裡改。週末或國定假日禁止撥打的州會標「Calls Prohibited」。Allowed calling hours by state — a read-only reference, not editable here. States that forbid calls on a day or on observed holidays show "Calls Prohibited".
Business Hours
/business-hour-settingsBusiness Hours
▲ 模擬畫面(假資料)▲ Mock screen (sample data)
SW 這邊帳號的時區與每天營業時間(每天可設開 / 關與時段)。跟 Ava 帳號的 Office Hour 是兩套設定。注意 Submit 在卡片外面下方。The SW account's time zone and daily open hours (open / closed and a time range per day). A separate setting from the Ava account's Office Hour. Note Submit sits below the card.
Accounts
/accountsAccounts ⓘ
Assign UsersCreate Account| ID | Name | Email Verification | Phone Verification 1 | TCPA Rule Enabled | Redirect Domain | Enabled 2 | Operations |
|---|---|---|---|---|---|---|---|
| 101 | Acme - Auto Insurance | ON | ON | ON | links.example.test | ON | EditDelete |
▲ 模擬畫面(假資料)▲ Mock screen (sample data)
- 1
SW 帳號的建立與設定:Email / Phone Verification、Lead Cert Required、TCPA Rule、Blacklist Check、Redirect Domain、Email 簽名等。Phone Verification 沒開時,Contacts / Actions 依電信商、線路類型分組都會是 Unspecified。Create and configure SW accounts: Email / Phone Verification, Lead Cert Required, TCPA Rule, Blacklist Check, Redirect Domain, email signature, etc. Without Phone Verification, Contacts / Actions groupings by carrier and line type are all Unspecified.
- 2
關掉 Enabled 會停止這個帳號所有 Segment 的 Action。Turning Enabled off stops every segment action for the account.
API Key
/apikeysAPI Keys
Create| Account ID | Token ID | API Token | Create at | Operations |
|---|---|---|---|---|
| 101 | 12 | •••••••••••••••• | 09/01/2026 | Delete1 |
▲ 模擬畫面(Token 一律遮起來)▲ Mock screen (tokens always masked)
- 1
客戶用來把聯絡人 POST 進這個帳號的 API Token。要先選一個帳號才有 Create。刪掉之後,所有用這把 Key 的系統就不能再送聯絡人進來。The API tokens customers use to POST contacts into this account. Create appears only with an account selected. Deleting one stops every app using that key from posting contacts.
Batch Jobs
/batch-jobsBatch Jobs
| Type | Name | User | Created at | Status | Operations |
|---|---|---|---|---|---|
| Export | contacts-2026-09-30 | QA Tester | 09/30/2026 10:00 | ● Processed | DownloadDelete |
| Import | segments.csv | QA Tester | 09/30/2026 10:05 | ● Processing |
▲ 模擬畫面(假資料)▲ Mock screen (sample data)
背景匯入 / 匯出工作的狀態(Pending → Processing → Processed / Failed)。資料量大的聯絡人匯出會在這裡產生,Processed 之後才能 Download;完成或失敗的工作可以刪掉。Status of background imports / exports (Pending → Processing → Processed / Failed). Large contact exports are produced here; Download appears once Processed, and finished or failed jobs can be deleted.
Documentation · Contact
/doc/contacts-v2「新增聯絡人(V2)」的 API 文件:驗證方式、Headers、欄位表、自訂欄位、Sub ID、回應與錯誤,下方有 JSON / cURL 範例。上方會顯示這個帳號的 API Header,可以下載 API 說明(帳號沒有 Key 時不能下載)。The "Add Contact (V2)" API doc: authentication, headers, fields, custom payload, Sub IDs, responses and errors, with JSON / cURL examples. The account's API header is shown at the top, with a download of the API instructions (disabled if the account has no key).
Documentation · Contact Deletion
/doc/contact-deletionCCPA 刪除聯絡人的 API 文件,下面有「Try it」可以直接送刪除請求或查狀態。Send deletion request 會真的刪掉這個帳號裡符合的聯絡人,測試時要確認帳號和電話。這頁有自己的功能旗標(合規功能,各環境都開著)。The CCPA contact-deletion API doc, with a "Try it" panel to send a deletion request or check status. Send deletion request really deletes matching contacts in this account — double-check the account and phone when testing. The page has its own feature flag (a compliance feature, on in every environment).
Documentation · User Guide
/doc/user-guide一頁簡短的中文說明,連到舊的外部文件與產品指南。A short page (in Chinese) linking to the old external docs and the product guide.
Profile
/profile「My Profile」:一列顯示你的 ID、姓名、Email、角色、能看的帳號。Update Profile 會跳到外部的單一登入(SSO)個人資料頁去改。"My Profile": one row with your ID, name, email, roles and accounts. Update Profile jumps to the external single-sign-on profile page.
Conversions
/conversionsConversions per day — last 30 days 3
QAwooktestAll your conversions 4
| Conversion | Method | Trigger | Value | Today | Yesterday | Last 7 days | Status | |
|---|---|---|---|---|---|---|---|---|
| QA | Call duration | call ≥ 60s | $25 | 12 | 18 | 96 | Activated | Edit |
| wooktest | Call duration | call ≥ 180s | — | 3 | 5 | 21 | Activated | Edit |
沒有任何 conversion 時顯示「No conversions yet」,並多一個「Declare one from Received Events →」按鈕。With none defined it reads "No conversions yet" and adds a "Declare one from Received Events →" button.
| Incoming event | Count (7d) | Last received | Method | Status | |
|---|---|---|---|---|---|
| QA | 1,204 | 2 hr ago | Call duration | Declared | |
| sms.replied | 318 | just now | — | Undeclared | Declare → Ignore |
| link.clicked | 52 | 3 days ago | — | Ignored | Un-ignore |
Define a conversion
CancelChoose a conversion method
| 方法Method | 狀態State | 什麼時候觸發Fires when |
|---|---|---|
| Call duration | Live | Fires when a call lasts at least a duration you set. |
| Link clicks | Coming soon | A recipient clicks a link your system sent. |
| Pixel / JS tag | Coming soon | — |
| Server API / Webhook | Coming soon | — |
| CSV / manual upload | Coming soon | — |
Call duration — details
Review & activate
▲ 模擬畫面(假資料)。版面與欄位照同事提供的 Conversion Tracking 詳細版(2026-10-06)校正。▲ Mock screen (sample data). Layout and columns corrected against a colleague's detailed Conversion Tracking write-up (2026-10-06).
- 1
兩個分頁:Define Conversions(定義要算哪些、看次數)與 Received Events(看收到哪些事件)。網址用
?tab=define/?tab=received切換。Two tabs: Define Conversions (what to count, and the counts) and Received Events (what arrived). The URL switches with?tab=define/?tab=received. - 2
打開精靈,從第 1 步開始。預設值:秒數 60、金額空白、Primary 勾選。Opens the wizard at step 1. Defaults: 60 seconds, blank value, Primary ticked.
- 3
最近 30 天每天的次數,用太平洋時間切日,沒資料的天畫成 0。Daily counts for the last 30 days, cut in Pacific time; empty days drawn as 0.
- 4
Status 一律是 Activated —— 目前沒有刪除或停用的功能。Edit 會打開精靈的第 2 步。可排序:Conversion、Today、Yesterday、Last 7 days。Status is always Activated — there is no delete or disable yet. Edit opens the wizard at step 2. Sortable: Conversion, Today, Yesterday, Last 7 days.
- 5
搜尋只在已經抓下來的資料裡篩選;Refresh 重新抓並更新時間。最多顯示 200 個事件名稱。Search filters what has already been fetched; Refresh re-fetches and updates the timestamp. At most 200 event names.
- 6
三種狀態:Declared(已有同名 conversion)、Undeclared(整列黃底,可 Declare 或 Ignore)、Ignored(有人手動按過)。Ignore 沒有確認視窗。Three statuses: Declared, Undeclared (row highlighted; Declare or Ignore) and Ignored (pressed by hand). Ignore has no confirmation.
- 7
步驟圓圈不能點,Enter 進下一步。新增從第 1 步開始;Edit 從第 2 步開始且 Method 鎖住;從 Received 按 Declare 進來也是第 2 步,名稱已預填且不能改。The step circles are not clickable; Enter advances. New starts at step 1; Edit starts at step 2 with Method locked; arriving via Declare also starts at step 2 with the name pre-filled and locked.
- 8
通話秒數 ≥ 這個數字就算(剛好等於也算)。只看秒數 —— 不分 inbound / 撥出 / 轉接,也不看結果,所以很長的語音信箱也會算。A call counts at or above this number (equal counts). Only the seconds matter — not direction, not outcome — so a long voicemail counts too.
- 9
Primary 目前是 Coming soon,預設勾選。現在唯一的實際效果:第一次設定 Google 匯出時,Primary 的會預設被勾選。Primary is Coming soon and ticked by default. Its only effect today: primary conversions are pre-selected on first Google-export setup.
🔎 完整規則(名稱與金額的限制、Cancel 的行為、兩個頁面算法不同…)見功能說明:Conversions:怎樣算一次轉換Full rules (name and value constraints, Cancel behaviour, the two different 7-day calculations…) in Conversions: what counts as one
CL1.2 範圍,目前 QA 先跳過。只在單一帳號範圍、開了功能旗標時出現(在組織範圍會提示「Select an account」)。兩個分頁:Define Conversions(定義怎樣算一次轉換 —— 目前只有「通話超過幾秒」這一種上線,其他方式標 Coming soon)與 Received Events(收到的事件,可以宣告成轉換或忽略)。CL1.2 scope — skipped by QA for now. Shown only at single-account scope with the feature flag on (organization scope says "Select an account"). Two tabs: Define Conversions (what counts as a conversion — only "call lasts at least N seconds" is live; other methods say Coming soon) and Received Events (incoming events to declare as conversions or ignore).
Google Offline Conversions
/google-offline-conversionsGenerate a daily conversion file (keyed by GCLID) in Google's offline-conversion-import format and get it back into Google Ads, so ROAS is completed where spend lives.
most lead-gen ad clicks never convert online — the real signal comes later, when a lead turns into a qualifying call or sale. Sending those events back to Google Ads (matched by GCLID) lets Google optimize toward the clicks that become real leads, not just form fills. Google's guide →
| Conversions sent | 3 of 5 included Qualified call, Appointment booked, Sale closed |
|---|---|
| Rolling window | Last 90 days (cumulative)5 |
| Runs | Every morning · 6:00 AM PDT · last run Oct 5, 2026 (412 rows) · next Oct 6, 2026 6:00 AM PDT8 |
| Value & currency | Per-conversion value · USD |
| Delivery | Google Sheet — CLP — wook — offline conversions open ↗ |
| Sheet access | CLP write Granted · Google read Confirmed by you7 |
| File format | Google Click ID · GBRAID · WBRAID · Conversion Name · Phone · Conversion Time · Conversion Value · Conversion Currency11 |
| Date | File | Window | Rows | With GCLID | Delivery | Status | Download |
|---|---|---|---|---|---|---|---|
| Oct 5, 2026 Latest | google_offline_2026-10-05.csv | last 90d | 412 | 84% | Google Sheet | Delivered | Download |
| Oct 4, 2026 | google_offline_2026-10-04.csv | last 90d | 407 | 83% | Google Sheet | Failed | Download |
▲ 檔案是累積的:每天早上重新產生,往回蓋滿整個 rolling window,不是只放當天那幾筆 —— 所以列數是一路往上長的。▲ The file is cumulative: it is regenerated each morning across the whole rolling window, not just that day’s rows — which is why the row count keeps climbing.
| Date | File | Window | Rows | With GCLID | Delivery | Status | Download |
|---|---|---|---|---|---|---|---|
| Oct 6, 2026 | google_offline_2026-10-06.csv | last 90d | — | — | Google Sheet | Generating… | — |
| Oct 5, 2026 Latest | google_offline_2026-10-05.csv | last 90d | 412 | 84% | Google Sheet | Delivered | Download |
| Oct 4, 2026 | google_offline_2026-10-04.csv | last 90d | 407 | 83% | Google Sheet | Failed | Download |
▲ 跑的時候沒有列數、也沒有下載連結,而 Latest 還留在 Oct 5 —— 它標的是「最新一筆真的送達的」,不是最上面那一列。這時候 Publish now 按不動。▲ While it runs there is no row count and no download, and Latest stays on Oct 5 — it marks the newest row that actually delivered, not the top row. Publish now is disabled meanwhile.
| Date | File | Window | Rows | With GCLID | Delivery | Status | Download |
|---|---|---|---|---|---|---|---|
| Oct 6, 2026 Latest | google_offline_2026-10-06.csv | last 90d | 418 | 84% | Google Sheet | Delivered | Download |
| Oct 5, 2026 | google_offline_2026-10-05.csv | last 90d | 412 | 84% | Google Sheet | Delivered | Download |
| Oct 4, 2026 | google_offline_2026-10-04.csv | last 90d | 407 | 83% | Google Sheet | Failed | Download |
▲ 跑完了。注意列數 412 → 418 是往上長的(檔案累積),而 Latest 才跟著移到 Oct 6。沒有多出一列 —— Publish now 是把今天那一列原地换掉重跑。▲ Done. The row count climbs 412 → 418 (the file is cumulative) and Latest moves to Oct 6. No extra row appeared — Publish now regenerates today’s row in place.
A contact is covered when it contains any of GCLID, GBRAID, or WBRAID. An account is marked Investigate when more than 10% of its new contacts are missing one, but only once it has enough GCLID history to compare against and at least 20 new contacts in the window — short of that the row reads Not enough data rather than OK. An account with no GCLID history at all, sending virtually no click IDs, is asked to set up GCLID instead.12
| Account | New (24h) | With GCLID | Missing | % missing | Status |
|---|---|---|---|---|---|
| wook (ID 81) | 204 | 171 | 33 | 16.2% | Investigate |
Coverage is flagged in this grid only; it does not send an external alert.
On staging this link opens the API docs at /doc/contacts-v2#gclid. Summary:
{
"phone": "6195551234",
"email": "jane.smith@example.com",
"custom": {
"gclid": "Cj0KCQjwrKm4BhCcARIsAK9customExampleClickIdValue"
}
}
- Optional. A contact without a gclid is created exactly as before.
- Send it under
custom. A top-level gclid is kept only for accounts that already have custom fields configured; otherwise it is dropped with a 202 and no error. - Forward it as-is. Roughly 50–100 characters; do not parse, truncate, or normalize it.
Choose what to send
Pick the conversions and how far back — then continue to delivery.
Conversions to include
| Conversion | Created | Last seen | Last 7 days | |
|---|---|---|---|---|
| QA | Aug 9, 2026 | Aug 10, 2026 | 0 | |
| wooktest | Aug 10, 2026 | Aug 10, 2026 | 0 | |
| 07811test | Aug 10, 2026 | Aug 10, 2026 | 0 | |
| 2 min | Aug 19, 2026 | — | 0 |
Tick each conversion to include in the daily Google file — include whichever ones you want. Created and last seen help you tell active conversions from stale ones. 4
Rolling window
Last 90 days — the file is cumulative (keeps prior days), like your Google sheet 5
Scope
This account (wook · ID 81) 6
Include at least one conversion — an empty file would clear the sheet Google reads.
Deliver to a Google Sheet
CLP writes your daily file into a Google Sheet, and Google Ads reads it from there. Connect a sheet, then set up access.
Tab "Conversions" — CLP writes the rolling file here each morning.
Who can access this sheet 7
Granted automatically when you connected — CLP has Editor access and updates the sheet daily.Granted
Re-check access
Share the sheet as Viewer with the email Google gives you —
…@partnercontent.gserviceaccount.com — found on your Google Ads Uploads screen. See where to find it ↗ · how to share ↗Confirmed by youConfirmed by wook on Aug 11, 2026
Undo
Other delivery methods — Downloadable file and HTTPS file — are coming soon.
Runs after calling hours so each day is complete before it's written — you don't need to pick a time.
Google Click ID GBRAID WBRAID Conversion Name Phone Conversion Time Conversion Value Conversion CurrencyGoogle's offline-conversion format — the column headers are written in automatically as the first row.
Preview — the file that will generate
| Google Click ID | GBRAID | WBRAID | Conversion Name | Phone | Conversion Time | Conversion Value | Conversion Currency |
|---|---|---|---|---|---|---|---|
| Teab1QTheFAKEgclidSTRING…_0123456783 | QA | +12132746814 | 2026-08-09 19:52:42-07:00 | 1 | USD | ||
| Teab1QTheFAKEgclidSTRING…_0123456784 | QA | +12132746814 | 2026-08-10 18:41:59-07:00 | 1 | USD | ||
| Teab1QTheFAKEgclidSTRING…_0123456784 | wooktest | +12132746814 | 2026-08-10 18:41:59-07:00 | 3 | USD |
≈ 6 rows across the last 90 days. Every row is keyed by Google Click ID — conversions whose contact is missing a GCLID can't be included (that's why GCLID coverage is monitored). This is the file that will generate every day — edit anytime and it takes effect at the next morning's run. 9
▲ 模擬畫面。這一頁的版面、文案與欄位照 Lucy 2026-10-05 的實機截圖重做,假資料沿用截圖裡的測試帳號。▲ Mock screen. Layout, copy and columns rebuilt from Lucy's live screenshots (2026-10-05); the sample data follows the test accounts in those shots.
- 1
這個功能在解決什麼問題:多數廣告點擊不會在線上就完成轉換 —— 真正的訊號晚一點才出現(變成一通有效通話或一筆成交)。把這些事件用 GCLID 配回 Google Ads,Google 才能朝「會變成真客戶的點擊」最佳化,而不是只朝「填了表單」。The problem it solves: most lead-gen ad clicks never convert online — the real signal comes later. Sending those events back to Google Ads, matched by GCLID, lets Google optimize toward clicks that become real leads.
- 2
Daily files 是一天一列,不是一次匯出一列。當天那一列在早上跑完前是
Generating…,沒有下載連結;Latest標的是最新一筆真的送達成功的,所以它不一定在最上面。Failed的那一列檔案有產出、可以下載,只是沒送進 Sheet。Daily files is one row per day, not one row per export. Today’s row readsGenerating…with no download until the morning run finishes; theLatestbadge marks the newest row that actually delivered, so it is not always the top row. AFailedrow still has a file you can download — it just never reached the Sheet. - 3
首頁這條橫幅看的是「過去 24 小時新進的聯絡人」,不是檔案裡的比例。兩個數字會不一樣:橫幅是「現在進來的資料健不健康」,檔案那一欄是「過去 90 天累積下來的結果」。沒有 GCLID 的轉換 Google Ads 配不回去,進不了檔案。The banner measures contacts that arrived in the last 24 hours, not the share inside the file. The two numbers differ by design: the banner asks whether what is coming in right now is healthy, while the file’s column is the result accumulated over the last 90 days. A conversion with no GCLID cannot be matched back by Google Ads, so it never enters the file.
- 4
Created 與 Last seen 是用來分辨「還在用的」跟「放著沒動的」轉換 —— 畫面上的提示自己這樣寫。要送哪些自己勾,沒有強制規則。Created and last seen are there to tell active conversions from stale ones — the on-screen hint says so. You pick what to include; nothing is forced.
- 5
Rolling window 是「每天的檔案往回看幾天」,而且檔案是累積的(keeps prior days)—— 不是每天只放當天那幾筆。預設 90 天。The rolling window is how far back each daily file reaches, and the file is cumulative (it keeps prior days) — not just that day's rows. Default 90 days.
- 6
Scope 是單一帳號。設定綁在這個 account 上,不是整個組織。Scope is a single account — the configuration belongs to this account, not the organization.
- 7
一份 Sheet 要兩種權限,而且取得方式不同:CLP 的 Editor 是連結時自動拿到的;Google Ads 的 Viewer 要你自己去分享給 Google 給你的那個
…@partnercontent.gserviceaccount.com信箱(在 Google Ads 的 Uploads 畫面上找得到),系統只能讓你自己確認,所以標的是「Confirmed by you」而不是自動檢查。The sheet needs two different levels, obtained differently: CLP's Editor is granted automatically on connect; Google Ads' Viewer you must share yourself with the…@partnercontent.gserviceaccount.comaddress Google gives you (found on the Google Ads Uploads screen). The system can only record your confirmation — hence "Confirmed by you" rather than an automatic check. - 8
時間是自動的,不用自己挑 —— 每天早上(預設 6:00 AM PDT)在前一天的通話都結束之後才產生,這樣每一天的資料才是完整的。The schedule is automatic — each morning (default 6:00 AM PDT) after the prior day's calls have closed, so every day is complete before it is written.
- 9
沒有 GCLID 的轉換進不了這個檔案 —— 這就是為什麼要盯 GCLID coverage。另外設定可以隨時改,改完在隔天早上那一次生效。Conversions whose contact has no GCLID cannot be included — which is why GCLID coverage is monitored. Settings can be edited anytime and take effect at the next morning's run.
- 10
Publish now 是「現在重跑一次」,不是「追加一份」 —— 它把今天那一列原地換掉重新產生,不會多出一列。正在
Generating…的時候按不動。改完設定想馬上看結果、或者前一次Failed想重試,都是按這裡,不用等明天早上。Publish now regenerates today’s file in place — it does not add a second one. It is disabled while a run isGenerating…. Use it to see a settings change take effect immediately, or to retry after aFailedrun, instead of waiting for tomorrow morning. - 11
檔案固定八欄,欄位跟順序都是 Google 規定的,不能改。GBRAID / WBRAID 平常是空的 —— 它們是 iOS 隱私政策下 Google 改發的替代識別碼,有 GCLID 就不會有它們。Conversion Time 帶時區偏移(如
-07:00),沒設金額的轉換 Conversion Value 就是空格,不是 0。The file is a fixed eight columns — the names and the order are Google’s, not ours. GBRAID / WBRAID are usually empty: they are the substitute identifiers Google issues under iOS privacy rules, and a click that has a GCLID has neither. Conversion Time carries a UTC offset (e.g.-07:00), and a conversion with no value leaves Conversion Value blank rather than 0. - 12
「Investigate」有門檻,不是缺一筆就叫:要同時滿足「缺失 > 10%」、「視窗內至少 20 筆新聯絡人」、「這個帳號以前就有 GCLID 可以比對」三個條件。不夠的時候標的是
Not enough data(不是OK)—— 區別在於「沒問題」跟「還沒資格判」不一樣。從來就沒送過 GCLID 的帳號會改成叫你Set up GCLID。這支旗子只在這個表格上,不會發任何通知,要自己回來看。“Investigate” has a threshold — one missing click ID does not trigger it. All three must hold: more than 10% missing, at least 20 new contacts in the window, and enough prior GCLID history on the account to compare against. Short of that the row readsNot enough data, notOK— “nothing is wrong” and “not yet judgeable” are deliberately different. An account that has never sent click IDs is asked toSet up GCLIDinstead. The flag lives in this grid only and sends no notification; someone has to come and look. - 13
Set up GCLID 不是設定,是打開 API 文件 —— 它連到
/doc/contacts-v2#gclid,因為 click ID 是客戶那邊送進來的,不是我們這裡能開關的東西。三個重點:放在custom.gclid底下(放最外層只有已經設過自訂欄位的帳號才留得住,其他會被安靜丟掉、照樣回 202);不送也不會錯,contact 照樣建立,只是回傳不了 Google;值要原封不動轉送,大約 50–100 個字,不要截斷或正規化。Set up GCLID is not a setting — it opens the API docs at/doc/contacts-v2#gclid, because the click ID is sent in by the customer; it is not something we can switch on here. Three things matter: put it undercustom.gclid(a top-level gclid survives only for accounts that already have custom fields configured — otherwise it is dropped silently with a 202); omitting it is not an error, the contact is created as normal and simply cannot be sent back to Google; and forward the value untouched, roughly 50–100 characters — do not parse, truncate or normalize it.
還想請同事補的:為什麼是走 Google Sheet 而不是直接打 Google Ads API?Failed 的那一天有人會知道嗎,還是要自己回來看?改了 rolling window,舊檔案裡已經送出去的那些轉換會怎樣?Still to be filled in: Why a Google Sheet rather than calling the Google Ads API directly? Does anyone find out about a Failed day, or must someone come back and look? And when the rolling window changes, what happens to the conversions already sent in older files?
CL1.2 範圍,目前 QA 先跳過。CL1.2 scope — skipped by QA for now.
Partnership conduit · Sub IDs
/partnership-conduit/sub-idsPartnership conduit 整組只有特定合作夥伴帳號看得到。Sub IDs、Endpoint Attributes、Technographics 這三項目前在程式裡沒有對應的頁面,點了會是「找不到頁面」。有頁面的是 Schedule、Lead filters、Change history。The whole Partnership conduit group is shown only for a specific partner account. Sub IDs, Endpoint Attributes and Technographics currently have no page in the code — clicking them gives "page not found". Schedule, Lead filters and Change history do have pages.
Partnership conduit · Schedule
/partnership-conduit/schedule設定這個合作夥伴「什麼時段接收名單」:Accept 24/7 或自訂時段(星期、開始 / 結束時間,15 分鐘一格)與時區。左邊是依星期 × 小時的熱度圖。儲存前會確認:啟用排程後,時段外送進來的名單會被拒絕並記錄。Sets when this partner's leads are accepted: Accept 24/7 or custom windows (days, start / end in 15-minute steps) and a time zone, next to a day × hour heat map. Saving asks for confirmation: once enforced, leads arriving outside the windows are rejected and logged.
Partnership conduit · Lead filters
/partnership-conduit/lead-filters被拒絕名單的紀錄:可以依拒絕原因、Sub ID、來源、日期篩選與匯出。下方「Filter rules」是之後才會開放的設定(目前是灰的)。A log of rejected leads, filterable by reason, Sub ID, source and date, with export. The "Filter rules" section below is for a future release (grayed out).
Partnership conduit · Change history
/partnership-conduit/change-history設定的變更紀錄:什麼時候、哪個 Sub ID / 帳號、改了什麼(舊值 → 新值)、誰改的,可以篩選與匯出。A history of setting changes: when, which Sub ID / account, what changed (old → new) and who, with filters and export.
Lite Campaigns
/lite-campaign-requests在「To be removed(即將移除)」群組裡。Lite Campaign 的申請清單:建立時填商家名稱與轉接號碼。要另外開功能旗標,而且只有部分角色看得到。In the "To be removed" group. A list of Lite Campaign requests: creating one asks for a business name and transfer number. Needs its own feature flag and is limited to some roles.
Triggers
/triggersEvent Triggers ⓘ
Create| ID | Name | Next Action | Operations |
|---|---|---|---|
| 3 | On contact created | Welcome SMS | Edit TriggerEdit ActionDelete1 |
API Triggers
Create| ID | Name | Next Action | Operations |
|---|---|---|---|
| 5 | Partner post | Lead forward | Edit TriggerEdit ActionDelete |
▲ 模擬畫面(假資料)▲ Mock screen (sample data)
- 1
舊的觸發方式,在「To be removed」群組裡。Event Trigger = 聯絡人建立時(可設延遲)觸發 Action;API Trigger = 由 API 觸發。旗標沒開的一般使用者會在選單最下面看到單獨的「Triggers」,因為有客戶還在用。The older trigger mechanism, in the "To be removed" group. Event Trigger = fire an Action when a contact is created (with optional delay); API Trigger = fired via the API. With the flag off, regular users see a standalone "Triggers" at the bottom of the menu, because some customers still use it.
Partnership conduit · Endpoint Attributes
/partnership-conduit/endpoint-attributes這一項目前在程式裡沒有對應的頁面,點了會是「找不到頁面」(同 Sub IDs)。This item currently has no page in the code — clicking it gives "page not found" (like Sub IDs).
Partnership conduit · Technographics
/partnership-conduit/technographics這一項目前在程式裡沒有對應的頁面,點了會是「找不到頁面」(同 Sub IDs)。This item currently has no page in the code — clicking it gives "page not found" (like Sub IDs).
(這一項的介紹整理中)(This item's explanation is being written.)
🔒 = 只有系統管理員看得到;🚩 = 功能旗標控制;↗ = 另開分頁。選單結構整理自 samurai-world-client 2026-09-29 版。🔒 = system admins only; 🚩 = feature-flag gated; ↗ = opens a new tab. Menu structure taken from samurai-world-client as of 2026-09-29.