Template groups | Developer Documentation
Keep a campaign template register with ChatArchitect
Define the set and its owner
Give the campaign a clear identifier, purpose, owner, sender number and intended period. List the templates that belong to that scope. For example, an offer campaign may have separately approved language versions; an order-update workflow may have several messages at different stages. Keep each message's actual purpose and category visible.
Find the current versions in wtargeted.com. For a new or missing version, use the creation guide and review guide. Listing a template in the register does not establish approval or change its availability in a sending tool.
Record each template separately
| Register field | What the team should record |
|---|---|
| Campaign identifier and purpose | The campaign or workflow this entry belongs to and the action expected from the recipient. |
| Account and sender | The connected account and business number used by the sending workflow. |
| Template and language | The exact name, language, approved text/version checked and category shown in the account. |
| Current state | The review status and available quality information, with the time of the check. |
| Sending dependency | The CRM, help desk or automation that selects this version, its owner and variable mapping. |
| Test and reporting reference | The permitted test result, reporting period and available campaign or attempt reference. |
| Change record | When a version entered or left the campaign, what replaced it and who approved the switch. |
Check language versions individually using the language preparation guide. Avoid identifying a version by a friendly campaign label alone: the sending selection must match the actual template and language.
Maintain the register when a template changes
- Before the campaign, check each listed template's current status and test the intended version in its connected sending workflow.
- Before editing or deleting a template, use the management guide to check dependent sends. Record which workflows need to switch and who will verify them.
- After a switch, record the effective time, replacement name and language, changed variable mapping and test result. Keep the previous entry available for explaining earlier attempts. If the connected account will change, use the account change checklist to review destination availability before switching sends.
- If a template is paused or its quality declines, record the issue and review affected workflows. Moving an entry to a different campaign in your document does not reactivate a template.
Summarize results without losing their scope
Use the metrics guide to collect the available results for the same reporting period. Add counts only when their definitions and scope match and their records do not overlap. A template-wide total can include several campaigns; record that limitation if campaign-level separation is unavailable.
For example, 40 delivered messages from one language version and 60 from another total 100 delivered messages when the reports cover separate attempts. They do not establish 100 different recipients: one person may receive more than one message. Keep attempts with unknown results and unavailable metrics visible.
When deciding between two versions, use the comparison guide instead of assigning the same conclusion to every template in the set.
If you need automatic grouping
Meta offers template groups for grouped template metrics. Automatic group management and a consolidated group report through ChatArchitect have not been confirmed. Ask support about availability, membership rules and reporting scope before relying on such a feature. The working register described here does not create or modify a Meta group.
No comments to display
No comments to display