How does one go about using the MailChimp API to create a two-step signup process? I'm having a really hard time finding any documentation for this. It should go like this:
Step 1:
The website shows a sign up form with just an email field and a subscribe button. Once someone fills out her/his email address and hits 'Subscribe', the email address gets added to the list, and then additional options show up in a modal window (name, location, interests, etc.)
Step 2:
At this stage the user has already been added to the mailing list. The user can now choose to fill in the additional fields in the modal window (which will then be added to her/his account), or if he doesn't, then certain default values are added, after which a thank you message is shown.
Any help would be greatly appreciated! Thank you.
I would suggest that you use a single signup form as you capture your subscribers ... users rarely want to do something in two steps. Make it easy for them to take all the actions they want in one screen.
When you design your form, consider what information is mandatory and what is optional. You will need to think of how you will use the fields, groups, etc later in campaigns.
You can provide default values for many of the fields. You can also specify what message to send for an initial subscription.
Remember, a user is not "subscribed" until they accept the "did you really mean to subscribe" email that is automatically send by MailChimp.
Related
The default Twitter pixel script contains this code
twq('track','PageView');
to trigger a PageView event (conversion).
In the documentation it states:
Choose the type of conversion you’d like to track with this tag. Your Twitter Ads dashboard reports on conversions by conversion type.
Here are the types:
Site visit: User visits your site
Purchase: User completes a purchase of a product or service on your
site
Download: User downloads a file, such as a white paper or software
package, from your site
Sign up: User signs up for your service, newsletter, or email
communication
Custom: This is a catch-all category for a custom action that does not
fall into one of the categories above
Does this mean that I can trigger these conversion types by the twq('track', event) function? If so, what is the syntax?
It appears they've expanded their documentation slightly in this regard, but it's still vague:
A conversion event can be any "Action" that a user completes on your site which you would like to track. It does not have to be a purchase, but can also be a shopping cart update, a newsletter sign up, etc. Choose the type of conversion you’d like to track with this tag. Available tag types are Site Visit, Purchase, Sign Up, Download, or Custom. Choose “Custom” if you’re tracking an action other than the conversion events we’ve predefined.
There is, however, an example of this in the documentation:
Under the question How to setup advanced conversion tracking to monitor campaign ROI? there's this:
You'll notice the Purchase event, above. Unfortunately it doesn't give up the syntax for the two word events like Sign up. Sigh.
There is also this post on their developer forums from an employee (date Jan 2018) indicating they are moving away from the other custom event types:
Due to a roadmap change, we are actively supporting “PageView” and “Purchase” tag types. But this does not mean that you can’t still track sign ups or custom events.
In their documentation there is also this disclaimer:
The purchase tag must executed independently of 'PageView' tag type, otherwise the dynamic values will be overwritten.
This appears to suggest these additional event types must be in replacement of the PageView event, but again it's unclear. If you tell Twitter to create a Purchase conversion event, the snippet it provides still uses PageView. It's very confusing.
Update: From my tests it appears the above code (with Purchase event) fires, and is tracked correctly, by Twitter.
Ho everyone, I'm in trouble with my campaign, this happened to me... when i go to my list to see the data of the recipients.
It is asking me to create a reconfirmation Campaign, due to a too high volume of unsubscribed to this campaign.
Here the path I've been following to realise my campaign ( It is the first time I'm using Mailchimp):
I have an invitation to a event where guest can approve or decline the invitation.
When they Accept the invitation: it bring to the update profile form - which icahnge in the advence editor. This way We can record some data such as dietary requirements,etc which would be recorder to our subscriber list ons submit.
When people decline the invitation, we have link to the unsubscribe form. This way we are able to know Which person has decline the invitation.
From what I understand, this is way It stopped our campaign.
What I'm looking to achieve . . . and din't manage i slept 2 hours last night trying to make this work . .. and i m in a big rush :
How can I achieve to collect data with the path explain previously, without having this issue in the future - so without using the unsubscribe from - but two different forms ?
How can I access to the List of User who have accept the invitation, so I mean the Subscriber List. because since that happen, I can't access it - and obviously i don't want to send another email to the guests asking them to fill up again.
I really appreciate all the help that anybody can provide me with that,
Thank you guys !
If I'm understanding you correctly, you're trying to use list subscriptions to stand-in for RSVPs? That is likely to look really bad -- ESPs see high volumes of unsubscribes as suspiciously spammy -- you'd be better off using Interests or Merge Fields on your list to denote the user's RSVP rather than asking them to unsubscribe. As for your current account, follow the instructions in the email you received if you want to get your list back up and running again.
I am having a register form that user fill in, once the form fill in, the registration is postponed till the user recieve an email to check that his email is ok, then when he reply the email, the registration is fully proceed.
I would like also the process to be automatic, without the need for the user to entered any number ect, just the need for him to click on the email to confirm, and automatic on my side too.
I want the process to be available to some others task than the registration process as well if possible.
Do I need to do all way check/123456 with the 123456 generated or is there a better way to do, a component, nuget that can do the job ? you experiences return would be helpful
thanks
You appear to be on the right track.
I do a similar thing quite often. It isn't generic since I do not need it but you can change that quite easily.
Once a user registers I send an activation e-mail that contains a link that when clicked navigates to something such as http://domain/member/activate/id where the id is a GUID. That is all I need. I look up the member id and activate it. Chances of someone guessing a new member's id are rather slim and even if they do it is very far from a train smash.
From what I can tell you need something more generic and a bit more security. You could always create some key (like a new GUID) that you store along with the user and then the activation calls: http://domain/member/activate/id?key={the guid}. You could even encrypt the key. But that is up to you.
For something that can be re-used and is more generic you could create an activation component that contains a list of activation ids. But to then activate a specific type of entity (such as user registration or form validation) you would need to have a way to perform that on the back-end. For example, when you call http://domain/activation/activate/id internally is looks up the id and gets the type. The activation request is, of course, created when, e.g., your user registers. You would probably want to store some expiry/timeout since a user may never activate.
For each type you could have an activation mechanism on the relevant controller: member/activate/key or formvalidation/activate/key. So when you activation controller receives a request to activate it has a list of routes conigured per type and the navigates to the relevant route to perform the 'actual' activation.
Another option is to have an in-process component perform activation e.g.: an IActivator interface implemented by a MemberActivator or FormValdationActivator and then have an IActivatorProvider implementation that gives you the relevant provider based on a type (.NET Type or a string type you provider --- that's up to you).
You could even pass an ActivationRequestCommand along to a service bus endpoint if you are so inclined.
So you have many options. HTH
If you are a developer I suggest you at least try to start with the code... then ask again if you get stuck providing a sample of what you've done.
What you are looking to do is basically use a temporary url that posts to a page to complete the registration...
How we can implement Two recaptcha user control on the same page.
Problem :
we have two views one for tell a friend about the site by sending e-mail and another authoring any note. the tell a friend part is hidden which send e-mail through ajax and note author part is visible so it is making problem when we need both but in different way.
Refactor to avoid usability issue
This doesn't seem reasonable and I would suggest to avoid this at all costs, because you have a serious usability issue if you do need two of them. Why would you need two captchas anyway? The main idea behind a captcha is that it assures that there was a person entering data in the form and not a computer.
So if there's one captcha on the page, you're assured. So if the first one was filled by a person, all other data is as well and you don't need a second one.
But I can see one scenario where two captchas could come into place. And that's when you'd have two <form> elements on the page. So a user can either submit one or the other. In this case user will always submit data from just one form and not both. So you could avoid this as well by either:
separating these two forms into two pages/views with an additional pre-condition page where a user would select one of the two forms
hiding captcha at first, but when a user starts entering data into one of the forms you could move the hidden DIV with captcha inside the form and display it. This way there would only be one captcha on the page and it would be on the form that the user is about to send
The second one is the one you'd want to avoid. If you give us more details what your business problem is, we could give you a much better answer.
Alternatives
Since you described your actual business problem I suggest you take a look at the honey pot trick, that is more frequently used for this kind of scenarios. Because if you used too many captchas on your site, people would get annoyed. They are tedious work, that's for sure. Honey pot trick may help you avoid these unnecessary data entering.
The other question is of course: Are your users logged in when they have these actions available? Especially the editing one. If they are, you can better mitigate this problem. You could set a time limit per user for sending out messages. Like few per minute. That's what a person would do. And of course store the information about sending out these emails, so you can still keep historical track of what users did so you can disable accounts of this gets abused. But when users are logged in they normally don't have to enter captchas since they've already identified themselves during authentication phase.
The ultimate question is of course: Why would a bot send out emails to friends? they wouldn't be able to send any kind of spam would they? What's the point then? It's more likely that bots will abuse your system if they can spam users anyhow. Either by sending email with content or leaving spam comments on your site. These forms need to be bot checked.
I am working on a form filling program and I'm looking for suggestions on implementing data validation.
I'm considering a two-phase approach:
Interactive - after user enters data and attempts to move to the next field, flag invalid data with something non-obtrusive, like a balloon message but let the user continue on.
Preflight Checklist - Once the form is filled and the user attempts to print/send it, re-validate the form, notify user of errors and refuse to continue until corrections are made.
Any other ideas, suggestions?
I would always recommend validating at the server as well.
Otherwise, what you describe is what I typically see. Oh... and don't flag a required field as invalid if a user tabs through it, unless it's still blank when they submit, but if they enter "wrong" data into a field, indicate it immediately, as you describe.
OK, if you are asking about user experiace, then i would apply both 1 and 2.
As users input fields, highlight fields, that are required, incorrect with colours/icons (no blloons, they are in the way). Icons can then be clicked for explanation of why it is incorrect.
Also validate the form at the end, before submit, and highlight the incorrect fields/required missing fiels, but try to avoid step by step acceptance (click ok, and message per field missing, incorrect).
You could rather then have a display that tells the user the messages, but dont remove this, otherwise you are back where you started from, click and go.