WhatsApp Sharing

Within ControlShift, admins can choose to include WhatsApp among the social share options available to site visitors. 

To turn on WhatsApp sharing, go to the org admin homepage > Settings > Social Media > Sharing Channels and choose WhatsApp in the dropdown. Then click to Add. Once added, mobile users will see the WhatsApp option in the social share block at the bottom of the petition page, in the post-signing share prompts, and in emails. If needed, you can also change the order of your sharing channels from this page.   

Please note: users will only see the WhatsApp option when they're viewing the petition on mobile-sized screens. If you want to test the WhatsApp configuration, you'll need to test it on a smaller screen. 

Admins can translate and/or customize the default WhatsApp share message by going to the org admin homepage > Settings > Content > Social > WhatsApp share text. This share text is automatically added to the user's WhatsApp message, but can be edited by the user. The petition's URL will be automatically appended to this message.

Like with Facebook and Twitter, admins can also customize the WhatsApp share message at the petition level. To provide a custom WhatsApp message, go to the petition > Admin > Settings > Social Media > WhatsApp Share Message. Because we automatically append the petition's URL, you should not include the petition URL in this customized share message. 

Whenever a petition is shared using the WhatsApp button, we'll append a whatsapp-share-button source and a whatsapp UTM parameter to the end of the URL. When the message's recipient clicks the link and signs the petition, they'll be tagged with the whatsapp-share-button source code and the whatsapp utm_source. To customize the UTM source used with the WhatsApp share button, click the edit ( ) button next to WhatsApp in the social media settings page.

Please note: If your organization has enabled WhatsApp sharing, but you're not seeing the WhatsApp button in automatic emails to creators and signers, it may be because your templates are using outtdated social media variables. Please see our documentation for next steps.