Techvoot Solutions

The Push Notifier for Firebase plugin seamlessly integrates your WordPress store with the Push Notifier for Firebase Firestore database. It enables real-time synchronization of user data and other relevant information between Firebase and your WordPress site, ensuring a smooth and efficient data flow.
Additionally, the plugin offers Firebase user notification functionality, allowing you to send automated notifications to users based on a cron job. This ensures that your users receive timely updates without any manual effort.
Whether you’re running an eCommerce store, membership site, or a custom web application, this plugin provides the essential bridge between WordPress and Firebase Firestore.
<h3>Key Features</h3>
<ul>
<li>Seamless Firebase Firestore Integration – Connect your WordPress store to Firebase Firestore with ease. </li>
<li>Automatic User Data Sync – Keep user data updated in real time. </li>
<li>Firebase User Notifications – Send automated push notifications via cron jobs. </li>
<li>Scheduled Notifications – Set up periodic notifications. </li>
<li>Secure Connection – Ensure safe and encrypted data exchange. </li>
<li>Easy Configuration – No coding required! Just enter Firebase credentials. </li>
<li>Compatible with WordPress & WooCommerce – Works with standard WordPress setups and WooCommerce stores.</li>
</ul>
<h3>External Services</h3>
This plugin integrates with Google Firebase services to provide real-time data synchronization and push notification functionality.
<h3>Firebase Services Used:</h3>
1. Firebase Cloud Messaging (FCM) 
– Purpose: Sends push notifications to user devices 
– Data Sent: Notification messages, user device tokens, and project identification 
– When: When notifications are triggered manually or via scheduled cron jobs 
– Service Provider: Google LLC 
– Terms of Service: https://firebase.google.com/terms/ 
– Privacy Policy: https://firebase.google.com/support/privacy
2. Google OAuth 2.0 Authentication 
– Purpose: Authenticates with Google services to access Firebase APIs 
– Data Sent: Service account credentials (client email, cryptographic tokens) for secure API access 
– When: During plugin initialization and when refreshing authentication tokens 
– Service Provider: Google LLC 
– Terms of Service: https://developers.google.com/terms/ 
– Privacy Policy: https://policies.google.com/privacy
3. Google Cloud Platform APIs 
– Purpose: Accesses Firebase Firestore database and cloud services 
– Data Sent: User data, notification content, and synchronization information 
– When: During data synchronization operations and database queries 
– Service Provider: Google LLC 
– Terms of Service: https://cloud.google.com/terms/ 
– Privacy Policy: https://cloud.google.com/terms/cloud-privacy-notice
4. Firebase Storage 
– Purpose: Handles file storage and retrieval (if used by your implementation) 
– Data Sent: File metadata and storage tokens 
– When: When accessing or storing files in Firebase storage 
– Service Provider: Google LLC 
– Terms of Service: https://firebase.google.com/terms/ 
– Privacy Policy: https://firebase.google.com/support/privacy
<h3>Data Handling:</h3>
<ul>
<li>User data is only sent to Firebase services that you explicitly configure in the plugin settings</li>
<li>All communications with Google/Firebase services use secure HTTPS connections</li>
<li>Authentication tokens are securely generated and managed by the plugin</li>
<li>No data is shared with third parties other than the configured Firebase services</li>
</ul>

Push Notifier for Firebase

Seamlessly integrate WordPress with Firebase Firestore for real-time sync & automated notifications. Ideal for eCommerce & membership sites! 🚀

Mithun Biswas

If your Firebase client app communicates with a custom backend server, you might need to identify the currently signed-in user on that server.
This plugin work with Google Firebase tokens. You can use it to verify ID Tokens.
<h3>Namespace and Endpoints</h3>
When the plugin is activated, a new namespace is added
<pre><code>/verify-id-tokens/v1/
</code></pre>
Also, a new endpoint is added to this namespace
/verify-id-tokens/v1/token/validate | POST
<h3>PHP HTTP Authorization Header enable</h3>
Most of the shared hosting has disabled the HTTP Authorization Header by default.
To enable this option you’ll need to edit your .htaccess file adding the follow
<pre><code>RewriteEngine on
RewriteCond %{HTTP:Authorization} ^(.*)
RewriteRule ^(.*) - [E=HTTP_AUTHORIZATION:%1]
</code></pre>
<h3>WPENGINE</h3>
To enable this option you’ll need to edit your .htaccess file adding the follow
<pre><code>SetEnvIf Authorization "(.*)" HTTP_AUTHORIZATION=$1
</code></pre>
<h3>Configurate the Firebase projectId</h3>
To add the projectId edit your wp-config.php file and add a new constant called BENGAL_STUDIO_VERIFY_ID_TOKENS_FIREBASE_PROJECT_ID
<pre><code>define('BENGAL_STUDIO_VERIFY_ID_TOKENS_FIREBASE_PROJECT_ID', 'projectId');
</code></pre>
<h3>Configurate CORs</h3>
The Verify ID Tokens | Firebase plugin has the option to activate <a href="https://en.wikipedia.org/wiki/Cross-origin_resource_sharing" rel="nofollow ugc">CORs</a> response headers.
To enable the CORs edit your wp-config.php file and add a new constant called BENGAL_STUDIO_VERIFY_ID_TOKENS_ENABLE_CORS
<pre><code>define('BENGAL_STUDIO_VERIFY_ID_TOKENS_ENABLE_CORS', true);
</code></pre>
<h3>Retrieve ID tokens on clients</h3>
To retrieve the ID token from the client, make sure the user is signed in and then get the ID token from the signed-in user:
<pre><code>firebase.auth().currentUser.getIdToken(/* forceRefresh */ true).then(function(idToken) {
 // Send token to your backend via HTTPS
 // ...
}).catch(function(error) {
 // Handle error
});
</code></pre>
<h3>Verify ID Tokens</h3>
<h4>verify-id-tokens/v1/token/validate</h4>
This is a simple helper endpoint to validate a token; you only will need to make a POST request sending the Authorization header.

Push Notifier for Firebase vs Verify ID Tokens | Firebase