Template Comparison | Developer Documentation
Compare WhatsApp template results in a ChatArchitect campaign
Compare two approved templates when deciding which wording or action to use in a later campaign. Start with the results your connected sending tool and business systems actually expose. Use the campaign metrics guide to locate delivery results, website data and business actions.
Define the comparison before sending
- Choose one question, such as whether two versions of an offer lead to more recorded appointments. Record the exact template name, language, approved text and intended action for each version.
- Use comparable recipients who expect the message. Record differences in audience, offer, sender number, send time and language; these can affect the result even when the wording is unchanged.
- Choose the reporting period, time zone, outcome and counting unit before reviewing results. Keep both templates' records within the same scope.
- If testing new versions, confirm their approval and check their quality. Plan recipient selection in your connected workflow. Built-in random assignment or an automatic A/B-test report in ChatArchitect has not been confirmed.
Build a comparison sheet
| Field | Record for each template |
|---|---|
| Template identity | Name, language, text/version checked, category and sender number. |
| Campaign scope | Campaign identifier, audience selection, period, time zone and counting rule. |
| Sending result | Available attempt, delivered, failed and read counts, with their units and source. Record a missing metric as unavailable. |
| Business outcome | The selected action from the CRM or website, its reporting period and how it was associated with the campaign. Use the measurement plan. |
| Template health and feedback | Current status and quality in wtargeted.com, plus relevant recipient feedback your team received. |
Check whether a template total includes other campaigns or earlier versions before using it. Count delivery states according to the sending tool's definitions. Several messages to one person are several messages, not several distinct recipients.
Compare rates with their denominators
The following is an illustrative worksheet, not a ChatArchitect report or a measured product result. It uses delivered-message counts and campaign-linked action counts for one reporting period:
| Measure | Template A | Template B |
|---|---|---|
| Delivered messages | 80 | 160 |
| Recorded campaign-linked actions | 8 | 12 |
| Actions divided by delivered messages | 8 / 80 = 10% | 12 / 160 = 7.5% |
Template B has more recorded actions and a lower ratio in this example. Keep both the counts and the denominator visible. This ratio is not a unique-customer conversion rate when actions or messages can repeat, and the difference does not prove that wording caused the result. Check audience differences, measurement gaps and repeat actions before choosing a version.
Review failures and quality before deciding
Separate delivery problems from missing business outcomes. If an attempt reports 131049, follow the recipient marketing limits guide before any retry. If quality declines or recipients complain, review the audience, frequency and content even when the campaign records more actions.
Record the decision, its supporting period and any unknown metrics. Use it to plan the next permitted comparison; avoid sending extra messages to the same contacts just to increase a sample. Keep the reviewed versions in your campaign template register.
If you need a native comparison report
Meta documents a separate template comparison API for send counts and block-related results. Its availability through ChatArchitect is unconfirmed. Ask support which report is available for your account, what it measures and which eligibility or reporting-period rules apply. Customer workflows use ChatArchitect App key and Secret; this guide does not require a Meta access token.
No comments to display
No comments to display