--- title: "Google Push and Stamping hybrid launch guide" slug: "google-push-and-stamping-hybrid-launch-guide-everything-you-need-to-know" description: "Plan a hybrid launch: push the plain-text block to Gmail on the web and turn on Stamping for every other client, with timing tips and a sample email." updated: 2026-02-26T14:42:56.000Z canonical: "https://help.opensense.com/docs/google-push-and-stamping-hybrid-launch-guide-everything-you-need-to-know" --- > ## Documentation Index > Fetch the complete documentation index at: https://help.opensense.com/llms.txt > Use this file to discover all available pages before exploring further. # Google Push and Stamping hybrid launch guide ## Overview A hybrid deployment pushes plain-text signatures into Gmail in a web browser, and also turns on signatures for all other clients and devices through Stamping. The two work together, so employees get beautiful email signatures on every corporate email, from any device. ## Google Push deployment Google Push deployment applies the Opensense plain-text signature block to each user's Gmail signature settings, with the Pusher tool in the Opensense portal. Employees who send email from Gmail then have the correct signature loaded in their account. ### Deployment prerequisites - On launch day, your Opensense signature admin pushes to a list of users in Opensense. You can then repeat this push for ongoing employee onboarding. - You can generate the list in Opensense, in Users & Compliance. See [Exporting a Pusher CSV from Compliance (classic UI)](https://help.opensense.com/docs/exporting-a-pusher-csv-from-compliance). ### Deployment tips and best practices **Best day to push:** any time. ### End-user experience - When you push to Google, we write to **My Signature** in Gmail signature settings, as your branded Opensense Signature Instructions document shows. If **My Signature** is already in use, it's overwritten. - Employees may need to refresh their browser for their new signature to show in their account. - As an extra check, employees should make sure **My Signature** is the default for new messages and replies, by following the instructions in the linked document. - In the Opensense Email Signature Instructions, we share how to stop Google from moving the signature to the bottom of the email thread. This isn't an Opensense setting, but employees and admins have found our instructions on fixing it useful. - **The default signature appears as plain text, and the recipient always gets a beautiful email signature design** that Marketing manages centrally. Your branded Opensense Signature Instructions document explains this transformation. ## Stamping Stamping adds a signature to all emails from any device, after the email is sent. **Stamping adds a signature only when a plain-text signature block isn't already in the body of the email.** ### Deployment prerequisites - On launch day, your Google admin adds users to an access control group or organizational unit (OU) in Google. This turns on email signatures for those users. - Coordinate the deployment date and time of your Push to Gmail with your IT department, so they can turn on Stamping at the same time. ### Deployment tips and best practices - **Best day to deploy:** any day, during off-peak email hours. - Adding users to the Stamping group can take up to 48 hours to take full effect, though it usually happens much faster. This happens on your email provider's side, and is unrelated to Opensense. Consider adding test users first, to confirm how long it takes in your environment. ### End-user experience - Employees need to remove their old signature from their devices, if they had one. Otherwise, emails may get two signatures. **They don't need to remove their Gmail signature in the web browser, because the Pusher tool updates that client.** - After deployment, emails sent from their corporate email addresses have the Opensense signature "stamped" onto them, after they're sent. - No signature is visible in the body of sent emails. ## Internal launch communications ### Before you send Good launch communication is the difference between a few support emails and many more than you need. To help you get started, here's a sample email, submitted by a customer who launched their email signatures successfully. - Send launch communications 1 to 3 days before launch day. Bonus points for showing your new company signature even sooner, at an all-hands meeting. - If you write a launch email you're proud of, send it to your customer success manager, so it can be added to the knowledge base to help others. :::caution[Personalize each template] The template is a great place to start, but customize it for your use case before you send it: this is the best time to prevent confusion. Replace the examples, such as the launch date (XX/XX/XX) and the help desk address (help@ABC.com). ::: ### Email template > **To:** All Employees > > **Subject:** Standardized Corporate Email Signature > > In an effort to present a stronger unified brand to our customers, we will be implementing a standardized email signature for all employees. Using a service called Opensense, the marketing team will now centrally manage the style and format of email signatures, while employee contact information will be synced from our company directory. This ensures that our corporate email communications will have a consistent appearance going forward. > > This means your email signature on all emails from any device will be beautiful and up to date with all of the latest messaging, and best of all, there is nothing to do on your end! Our IT team will be enabling a policy starting on XX/XX/XX that will automatically update your email signature in Gmail in your web browser. If on that day you compose an email and it is not the plain-text signature, you may need to refresh Gmail or log back in. When you send from a mobile device, the email signature will be added automatically after you send an email. If you have an existing signature on your mobile device, please turn it off. > > Finally, because contact information is synced with our company directory, any changes made directly to your signature block will be overwritten by directory information when you send an email. If your signature contains incorrect information, or you need any other help setting up your email signature, please contact our IT Helpdesk for support: help@ABC.com > > Highlights of the new email signature block are: > > ![An annotated example signature: a high-resolution logo, the name in bold blue, the title, office phone, and website in bold black, and linked social icons](https://help.opensense.com/media/googlestamphybrid1-14b669e23180.png) ### Change requests To set expectations for changes, you can add these paragraphs to the email: > Do not add quotations, tag lines, former acquired company names, memes, videos, alternate legal disclaimers, manufacturer logos, certifications, etc. If you believe that you have a legitimate case for adding or changing something on your signature block, please get approval from your manager, and place an IT service ticket stating what you want. Your request will be reviewed by Marketing for consideration. Do not make changes on your own. Thanks for your cooperation. > > The signature will appear as plain text when you send an email, and the recipient will always receive the branded email signature design that is centrally managed by Marketing. You can send a test email to your personal email or a colleague to confirm it's working as expected before you send an external email. Whenever you deploy the Opensense signature in bulk: - Announce it at an all-hands meeting, for an engaging launch. - Reduce internal support requests by sending a reminder email (or two) before launch. - Support requests tend to subside a week or so after launch. ## Placement issues Rarely, customers see placement issues, where the stamped signature is applied at the footer of the email thread, instead of in the last message sent. If you see this, or notice the signature stamped somewhere it shouldn't be, [send a #debug email](https://help.opensense.com/docs/how-to-send-a-debug-email), so Opensense support can trace the problem. ## What's next - [How to send a #debug email](https://help.opensense.com/docs/how-to-send-a-debug-email) - [Editing one user in Users & Compliance (classic UI)](https://help.opensense.com/docs/individual-edits-in-users-compliance) - [Saving your signature block in Microsoft 365 email apps](https://help.opensense.com/docs/opensense-on-microsoft-365) For further help, contact Opensense Support at [help@opensense.com](mailto:help@opensense.com).