------------------------------------ NEW SET OF CHANGES -----(As on 11th May)-------------------------
Alert : This requires some technical changes latest by 31st May, 2023
(Partners should also go through the Self Serve side of changes here)
1. Changed response objects for 'Partner API for Get App Usage' - [BREAKING CHANGE]
Current response - Refer doc
Changed response objects from 1st June, 2023, [new highlighted in blue for data after 1st June, 2023 , deprecated highlighted in red for data before 1st June, 2023]
2. Changes in Partner Portal - Analytics interface [NEW from June 01, 23]
The analytics interface will now accommodate the new type of conversation categories. Also, the FEP and FTC types will now be replaced with Paid and Free conversations with breakups available when you download the report.
a. Summary and app usage table changes -
b. App usage report -
c. Downloaded cost breakup report
3. Auth Templates via 'Apply for Templates API for Partners'-[NEW & MANDATORY FROM 29th May, 23]
New form params addSecurityRecommendation & codeExpirationMinutes are added in create template API to allow to use security disclaimer and expiration warning in Authentication template. Also new CTAs - Copy code and Autofill can be configured in the authentication template.
NEW body object description | ||
Key | Description | Example |
category | Possible Values: AUTHENTICATION MARKETING UTILITY |
AUTHENTICATION |
buttons | For “authentication” category, indicates button type "otp_type" Set to COPY_CODE if you want the template to use a copy code button, or ONE_TAP to have it use a one-tap autofill button. If otp_type is set to ONE_TAP, three additional parameters are required: autofill_text (String. One-tap button text, Maximum 25 characters) package_name (Your Android app's package name.) signature_hash (Your app signing key hash) |
COPY_CODE |
addSecurityRecommendation | Optional. Boolean. Set to true if you want the template to include the string, For your security, do not share this code. Set to false to exclude the string. |
TRUE |
content | For “Authentication” category the first line should be - "{{1}} is your verification code." |
{{1}} is your verification code. |
codeExpirationMinutes | Optional, added to footer Integer. Indicates number of minutes the password or code is valid. If omitted, the code expiration warning will not be displayed in the delivered message. Minimum 1, maximum 90. |
10 |
(Refer Meta documentation here)
Except for India : WABAs with even a single Indian Phone Number or India-based WABAs when they apply for these templates might be rejected. They can continue to use Utility templates for authentication. When an approved Authentication template is sent to an Indian phone number recipient, the message sending will fail. Exceptions should be removed by Meta in later part of 2023, as per Meta.
Even if you are able to get an authentication template approved which does not follow the provided format here, please note it might get rejected or fail in future by Meta,
For WhatsApp Self Serve Side changes, refer this article
-------------------------------- EARLIER SET OF CHANGES-------------------------------------
Alert : This required some technical changes which went live on 29th March, 2023
Meta has started migrating all existing templates from March 27, 2023 into the new categories introduced by Meta. Read all about them here.
The pricing for the same will be changed by Meta from June 01, 2023. See the pricing here.
Creating templates
Starting March 29, 2023, users will need to submit templates with the new three categories ONLY - Utility, Authentication and Marketing. Any other category will not be accepted by Gupshup. They can create templates via -
- the Gupshup Create Template interface
- the Gupshup Apply for Templates API for partners. Read updated API docs here
- the WhatsApp Manager (for embedded signup users)
Managing migrated templates
Note : There will be no change in the Template ID
Starting March 29, 2023 customers will start seeing the new along with the old category for their templates auto-migrated by Meta, in the below ways -
- the Gupshup Template List interface
- or the Gupshup Get Templates API for partners. Read updated API docs here
- or the WhatsApp Manager (for embedded signup users)
Businesses will also receive 2 sub-types of Template event - Template status update event with the new category and Template category update event (if you have subscribed for ‘template events’). Read updated API docs here.
Managing rejected templates
Starting April 01, 2023, businesses can raise an appeal against the rejection or new auto-assigned category of templates by-
- Writing to devsupport@gupshup.io (for traditionally onboarded WABAs)
- or the WhatsApp Manager (for embedded signup users)
- or re-submitting a copy of the same template (with required modifications) from the Gupshup interface in the desired category
Managing billing and analytics
All conversations will continue to be charged as per User initiated and Business initiated conversations till May 31, 2023, no matter what category they are assigned. We will keep you notified about the changes and advancements on the wallet and analytics side in the coming weeks.
Gupshup fee changes
There will be no Gupshup fee changes in this timeline.
Comments
0 comments
Please sign in to leave a comment.