In my Codeignitor website, I have a registration form.. Earlier my developer added mailchimp API to collect users details in mailchimp who register and it's working fine (as soon as someone registers their details get saved both in mailchimp and in my site's backend).
After registration users receive an email as well with a link to activate their account on my website.. Now I want to segment my mailchimp list based on who activated their account and who didn't.. (want to move users in separate lists based on who clicked the activation link).. Currently, as soon as someone registers their details get saved in one list whether they activate their account or not..
Please note that the email users are receiving on signup is coming from Codeignitor site itself (not from mailchimp, it's not the confirmation mail from mailchimp).
Please let me know if this is possible and how can it be accomplished.. If you can provide any reference link that would be very helpful..
Thanks.
I've a solution for this,
Step 1: Create a Group/Segment as Radio button(prefered) with two options'Activated Users' and 'Not-activated Users'
Step 2: Add all users who signing up to the site into the 'Not-activated Users' segment.
Step 3: After a user clicks the activation link, you need to write custom code after the activation process to add that user into the 'Activated Users' segment.
Step 4: Remove the user from 'Not-activated Users' segment.
Please give me some feed back…
Related
I am trying to add a member to Visual Studio Marketplace. In my account I go to Manage Publishers & Extensions -> Members and click om '+ Add'. Whatever e-mail I provide shows "Invalid Domain" error:
Is it a VS Marketplace bug or do I need to somehow link Azure directory (or any other users directory) first?
I'm having the same issue with a newly registered Publisher and have contacted Microsoft. Here's what I was told:
Apologies for the inconvenience you are facing. This is currently due to an issue at our end.
To unblock you, we can add the users manually to the publisher. Could you please provide us the VSIDs of the users that you are trying to add to the publisher?
To provide the VSID, do the following:
Login to the Marketplace (https://marketplace.visualstudio.com) with the email address that has to be added to the publisher.
After getting logged in, from the same browser window, open https://marketplace.visualstudio.com/_apis/connectiondata
You should see some JSON data in the window.
Copy paste the output of the page that you see. We are interested in the "id" field of the "authenticated" user.
We will manually add the users to your publisher, once we have the VSIDs details.
You'll want to contact Microsoft using the "Need help? Contact Microsoft" link that Grzegorz Smulko also mentioned, but you might as well collect the relevant IDs to include when you reach out to expedite the process.
Microsoft may be requiring Microsoft federated(Hotmail, Live..., or AD integrated) IDs.
Due to the complete lack of documentation, I have been unable to verify this claim.
This could also be attributed to Microsoft banning gmail.com as a valid source e-mail domain.
It looks like a bug to me.
I've tried to add a new member from the same domain as all the other existing members and I'm getting the very same error.
I'd suggest contacting MS using the "Need help? Contact Microsoft" link from the top-right corner.
There is an alternate way to add members via User Id. Please follow the steps mentioned here:
Ask member (that you want to add) to login their account on Marketplace
User Id will be visible by hovering over email as shown in image.
Member can copy the User Id by clicking copy-to-clipboard button and share with the current owner of the publisher(you).
Now the current owner of the publisher(you) can add member using User Id from members tab. Click on + Add -> Now enter the User Id-> Select a role you want to assign to the new member.
As shown in the below screenshot.
Steps to Reproduce
Sign up for a new enterprise trial.
Go to the Organization Edit screen.
Click on the Members section.
Click on invite by email.
User clicks on received email.
They create an account using the pattern of username#orgid.
The admin cannot see them in an member lists.
The user cannot see any products or repos.
I can admin a user just fine if they create a full bintray account, but we would like to not tell our users that they need to create a new account, which right now also forces them to create a new organization also.
What step am I missing here?
This was a temporary issue with invite-by-email members not being shown in the members list (judging by the time the question was raised). It should all be okay now. Sorry for the inconvenience.
I’ve created a survey using Google Consumer Surveys. I want use a different account to check results of the survey.
How do I allow a second google account to access the survey though the API?
You can add a second account by modifying the owners of a survey.
You can do this through the UI by selecting a survey from your list of surveys and then clicking the +Share button in the top right hand corner of the page. Then put the email address of the new owner in.
https://www.google.com/insights/consumersurveys/
You can also do this programatically through the API by issuing an update call to the Survey resource with a new Owners list. Note that this overwrites the owners field and does not append to it, so make sure to include the current owners when issuing an update so that no one losses access. You can find the documentation for this here:
https://developers.google.com/consumer-surveys/v2/reference/surveys/update
Is there something similar to the email verifcation feature where a system admin could validate user sign-up/registration requests?
Background: We're building a system with a closed community, where new users can join only if an admin has verified their sing-up data.
Ideally the admin should just receive an email that there's a new registration request and validate the request directly from the email.
The emailVerified column is protected - it can only be updated by the system in response to the target user clicking the link in the validation email.
An admin can not "tick" this field on behalf of another user.
However. From your brief description of the background I would suggest that you want the users to click the link - after all it serves to validate their email address. If you are creating your own app there is nothing to stop you adding your own column to the user model (or preferably a related table) and implement code in your sign up that also checks this extra column. Of course this is more work - but likely not excessive - and you get the desired workflow.
I made a members-only site that uses Google oauth2 to authorise users. The site is built with the Laravel framework and Artdarek's oath library.
When the authorization callback comes from Google, I lookup the user record in the DB by email and proceed to the protected page if the record exists, otherwise to a register page.
The problem is some of our members use two Google accounts. One user registered via his primary account (e.ge. a#gmail.com). The next day he returned and mistakenly tried to login with b#gmail.com. Naturally the system showed him the registration page. From that time on each time he visits the site the authentication mechanism sees him using his second (unwanted) set of credentials.
To resolve this one case I instructed him to logout of all accounts (on both sides), clear cookies and start from scratch but this is not a practical solution for all users. In same cases even this measure does not seem to correct the problem.
How can I solve this case? What is the right way to request oauth authentication and get them back from the right account? Can I force Google to ask the user with which account to proceed?
Google will automatically ask the user which account they want on an oauth request if they enable the account chooser.
I have logged into my Google Apps and my Google account, so for me on an oauth request, I get the following prompt:
In order to do the same for your user, they have to click "Stay signed in", but of course this is not advisable for public computers.
Beyond the above, I'm afraid not much can be done. - if they logged in with a#gmail.com at that time, these are the credentials you will receive.
They way I solve this problem is to have a field where the customer can add additional emails, and select one that is primary. I will then inspect against these emails when a request comes in to avoid duplicate user accounts.