Supply subscriber address details etc
Hi,
When creating a new subscription, is it possible to supply the subscriber's details such as address, email, etc? This would save them having to type the details in again if we have already collected them.
Thanks,
Tim
When creating a new subscription, is it possible to supply the subscriber's details such as address, email, etc? This would save them having to type the details in again if we have already collected them.
Thanks,
Tim
2
people have this question
I have this question, too!
Tell me when someone answers.
The more people who ask this question, the more it gets noticed.
The more people who ask this question, the more it gets noticed.
The company marked this question as answered.
Create a customer community for your own organization
Plans starting at $19/month
-
Inappropriate?We've definitely considered this. Email's pretty easy, the concern with address is that what we need is the billing address that corresponds with the payment method, which may or may not correspond with the address you might have for them.
Can you think of anything besides email address and billing address that your system has and could pass over?
I’m thankful for the feedback
-
Inappropriate?We'd also be interested in this feature at PostRank, specifically for name and email, since we're asking the user for that information already. Any chance you might look at implementing this?
Thanks. -
Inappropriate?While you can't pass the info along in the link, what you can do is
pre-create and/or update your customer's subscriber details using the
Create Subscriber and Update Subscriber API calls:
http://spreedly.com/manual/integratio...
http://spreedly.com/manual/integratio...
If you use those to set up the info before the link is clicked the
form will pre-fill with whatever Spreedly already knows about the
subscriber. They can still change the details while paying (which
makes sense, since some folks will need/want their billing info to be
different than their application info) but the details won't have to
be re-entered if they're already correct.
I'm thinking the best way to do this would be to create the subscriber
in Spreedly when someone creates (or maybe activates) their account in
your application. Then you can update their Spreedly info whenever
they change the relevant info in your system (if you want to - I think
this is a gray area that will depend on the application).
Will this fit your needs?
1 person says
this answers the question
-
Sounds like that should do exactly what we want. Thanks for your detailed response. -
Nathaniel,
Would this not result in a lot of cruft in the system? We have 150 new users a day but only 5 new paying users. Wont this just put lots of rubbish in the system?
Adrian -
Inappropriate?Sorry, I forgot about this thread; we just rolled out a better solution:
http://getsatisfaction.com/spreedly/t...
I’m excited
Loading Profile...




EMPLOYEE
