In EngagementHQ, you can allow your participants to link their EngagementHQ accounts with their Facebook, Twitter, and Google account. A participant that chooses this method of registration, as opposed to the regular way, will be able to log in to your site using their Facebook, Twitter, or Google login credentials. Note, however, that after the participant signs up using their social media page, it will lead them back to the EngagementHQ sign-up form, which they will need to fill up as a part of the process.
Important note regarding Twitter API:
Twitter has very recently announced that from February 14th, 2023 (AEDT), it will no longer provide free access to its API.
Twitter has provided very little warning and information about these changes. They have also been moving the dates and therefore we are still determining the correct path forward as we wait for more information from Twitter. If your organization has integrated your EngagementHQ account with Twitter, there may be two disruptions to be aware of:
Social Sign-in using Twitter: If a participant signs in using Twitter, this may no longer work. As a workaround Admin users can disable 'Enable Twitter signup' from Site Settings>Privacy and Security>Sign Up Form section. Participants can also sign in using other options available.
Sharing contributions or pages from EngagementHQ to Twitter: sharing (contributions, pages, tools, or widgets) from within the EngagementHQ application using Twitter may no longer work. As a workaround, you can copy the URL from your browser and post that URL manually on Twitter.
We apologize for this inconvenience and will provide more updates shortly as we learn more from Twitter and the impact on EngagementHQ customers. Please feel free to reach out to Support with any questions.
How does it work?
1. When a participant chooses to register for your project, they will be given the option to log in with 'Facebook', 'Twitter', 'Google', or register directly with EngagementHQ.
2. The application will take the participant to their Twitter or Facebook or Google account, ask them to sign in to their account, and allow EngagementHQ and Facebook or Twitter or Google to 'talk to each other'.
In Twitter, for instance, it would look like this:
3. The participant will be directed back to your EngagementHQ site and will need to fill in your registration form. This is necessary to capture the demographic information you ask participants for in the registration process.
4. After the registration is submitted and the participant has verified their email account, they can now log in using Facebook or Twitter or Google. There is no need for them to remember their screen name or password to the EngagementHQ site. It also means that they will be automatically logged into your site if they remain logged in to Facebook or Twitter or Google on their computer.
Note: Users will not be able to login with their social media accounts if they have already registered on the site with the same email address. The social media login only works when the account is being created for the first time on your site.
How to enable Facebook, Twitter and Google log in?
Navigate to 'Site Settings' and the tab 'Privacy and security.
Here you can enable the option 'Enable Signup Form' and tick the required options.
For Twitter, ticking the box and clicking Update is all you need to do.
For Google, please tick the box, click Update and then get in touch with our support via Chat or send us an email at firstname.lastname@example.org.
Enabling Facebook Login
For Facebook, you need to set up the 'App' within Facebook and obtain the 'Application ID' as well as the 'Application Secret'. Here is a step-by-step guide on how to achieve this:
1. You will need to register with Facebook as a developer. It is free and easy to do. You do however need to use your private Facebook account, rather than your organization's Facebook Page. Follow the steps as described here.
2. Create a new app (see detailed steps here). After you set up an app, you will be first asked to create a new app ID. We will run through this on the example of Penrith City Council.
3. The type of Product we are looking for is a Facebook login
4. The platform we are looking for is Web.
5. You will be asked what the URL of your site is. This is your EngagementHQ domain. Enter it here and click save.
6. Now it gets a little bit more detailed. When you have completed the first few steps, you can run through the basic setup of a Facebook app creation. There are a few fields here, but it is all pretty straightforward and just a matter of copy and paste.
Under Settings, choose Basic
Enter your EngagementHQ URL under App Domains
Same for your terms
The User Data Deletion callback URL will again be the URL of your site.
Choose the category of your app.
7. Under Products, go to Facebook Login and Settings. The valid OAuth Redirect will be your EngagementHQ domain, with /auth/facebook/callback appended. In the case of Penrith, this is https://yoursaypenrith.com.au/auth/facebook/callback
8. We are almost there now. Go back to Settings and Basic and copy the APP ID and APP Secret. You need to paste them back into EngagementHQ in a moment.
9. Last step in Facebook is to make your app public. To do this, simply click ON (see step 1) and then confirm you want the app to be public.
10. Finally, go into EngagementHQ into your Site Settings and into Participation. Make sure Facebook Signup (1) is enabled, paste the ID and Secret you just copied (2 & 3) and click save.
11. This should be it. Now you can test it by logging out and going to your login screen and clicking Facebook
12. When the Facebook login is set up correctly, a screen like below will appear in your Facebook, asking you to confirm that you want to share your Facebook details with EngagementHQ. This is what your participants will see as well. If you continue here, you will be taken back to your EngagementHQ registration form.
Note: The Facebook login will work even if the site is not launched.
Contact our support team if you need any further assistance via chat or email email@example.com