Ultimate Guide to Fixing Issues with Password Generation Webhook

Memberium Admin — 

Memberium’s password generator webhook allows you to generate a random password for your users, and this password can then be emailed to your users. The password generator is a quick way for onboarding members to your membership site. In this guide, we’ll give an example of an ideal automation for password generation and also how to fix any issues that you face with it.

An ideal automation in ActiveCampaign

Ideally, you would first add a trigger which would start this automation. This can be a tag trigger, form submission, etc and then you’d add the Password generator Webhook and finally send a Welcome email with their login information.

Here’s how it will look like:

ideal activecampaign automation

NOTE: Once the password has been generated in ActiveCampaign, and the user logs in to the site, Memberium will remove the password from the password field in ActiveCampaign and it is only stored in WordPress (encrypted by default).

Memberium for ActiveCampaign uses more secure WordPress password encryption than storing plain text passwords in ActiveCampaign field, that’s why the password from ActiveCampaign field is removed.

Even if the password is removed from ActiveCampaign, the user will still be able to login to the site using the same password.

When the user changes the password, lets say using [memb_change_password], then the same password is not synced with ActiveCampaign and its stored only in WordPress.

If you’ve followed these instructions and still face problem with password generation, then continue reading this article.

Delay in password generation

Normally there shouldn’t be a delay when it comes to password generation, but if there’s a delay then you might want to check your automation for any delay timer in there.

We’ve noticed some users place a 5 minute delay timer after the webhook, and then send the Welcome email but normally the delay timer is not needed. You might want to remove the delay timer and test out the automation again.

Password being removed from ActiveCampaign

If the password is being removed from ActiveCampaign, then you might want to check if the user has logged in to the site. If the user has logged in, then, in this case, Memberium removes the password from the password field in ActiveCampaign and it is only stored in WordPress as explained at the starting of this article. This is an intended feature.

Emails being sent with blank password

One reason for emails being sent with blank password can be that your email template might not have the correct placeholder for the password field. For example, you might be using %PASSWORD% whereas you’re actually using Membership Password field, and the placeholder for that would be %MEMBERSHIP_PASSWORD%.

password placeholder AC

ActiveCampaign calls this placeholder as Personalization Text. You can view the Personalization tag from Forms > Manage Fields, and then use the correct Personalization tag in the email template.

BONUS TIP: When sending emails, we’d suggest you to use an email address from your domain name and not a generic Gmail address. This ensures maximum email deliverability rate. You can change your “From” email address and name when editing the email template.

HTTP or HTTPS?

Have you recently started using HTTPS on your site? If so, then you’ll need to change your Password generator webhook to start with HTTPS.

Example: https://yourdomain.com/?job=createuser&key=K5ymgeegw1

Notice that it starts with HTTPS instead of HTTP. You’d need to make this change in your automation.

Is your Homepage protected?

In some cases, the homepage of the website is protected which can be a problem. Our default Password generator webhook example uses homepage, but what you can do is to use some other page also as your HTTP post.

Example, let’s say the default webhook is: https://yourdomain.com/?job=createuser&key=K5ymgeegw1 but since your homepage is protected, this won’t generate the password. You’d need to use a non-protected page for this, which can be your Login page such as https://yourdomain.com/login/?job=createuser&key=K5ymgeegw1 (notice the /login/ part in the URL).

Is Memberium running on the frontend?

You can check if Memberium is running on frontend by checking the page source of the homepage of your site. Here’s a screenshot for this:

Memberium frontend

If you’re unable to view this highlighted part in the screenshot, then it means that Memberium is not running on the frontend and one reason for this is that IonCube loader is not installed or misconfigured.

In some cases, Memberium support might be able to help you fix this issue or you can also try contacting your host who’ll help you in installing IonCube.

Test it out!

Once you’ve configured everything, its a good idea to test out your complete signup/purchase process and see how it goes. To test, you can use a new email address and then use it to signup/purchase as a user and check if you’re getting a proper email with login details and also sign in to the site and check if the user is getting proper access to the protected pages. Testing might take a few minutes, but it’s very important!