SL Freshview Subscribe v1.4.0 : Now fully compatible with Solspace's User module

The signup form contains a field for the email address and a “trigger” field. The value of the trigger field determines if the signup data is sent to Campaign Monitor. Assuming that the trigger fires then the signup info is sent to the Campaign Monitor account and list specified in the extension’s configuration. Does anything get to Campaign Monitor? Are the signups in a “pending” list awaiting activation - i.e. the list is set up as a double opt in?

I needed a drop down to say ‘No’ by default and ‘Yes’ as the other option, this wasn’t getting populated by the member custom field, even though the Freshview extension could see it.

Nothing was getting to CM as far as I could see.

I’ll give it another go when I can, as I mentioned previously, I’ve opted for the Campaign Monitor generated sub/unsub forms for now.

Pete’s explanation was spot on (thanks Pete).

I needed a drop down to say ‘No’ by default and ‘Yes’ as the other option, this wasn’t getting populated by the member custom field, even though the Freshview extension could see it.

If your custom member field isn’t displaying correctly in the sign up form, or the value isn’t being saved correctly when the form is submitted, that’s a problem with the form, not the extension. If the custom member field isn’t getting saved, that would certainly mean that the extension doesn’t add the member to the mailing list, as the “trigger” criterion isn’t being met.

I’ll give it another go when I can, as I mentioned previously, I’ve opted for the Campaign Monitor generated sub/unsub forms for now.

OK, well as long you’ve got something that works for you.

Cheers, Stephen

Hi Stephen

Is there not yet an official way for Campaign Monitor data to be updated when a member updates their EE profile via a Solspace User Edit Profile page?

Many thanks

Hi optima,

Is there not yet an official way for Campaign Monitor data to be updated when a member updates their EE profile via a Solspace User Edit Profile page?

Actually there is now, but only if you’re using the User module. I’ve been waiting for EllisLab to implement the relevant hook, so I could update the addon in a manner that’s compatible with both the User module, and the built-in member management, but so far the feature request has been ignored.

I’ll be implementing the User edit hook in the next release, but it’ll be a few weeks before I can find the time for it.

I hope that answers your question.

Cheers, Stephen

Hey Stephen, Great extension!

I’m having issues sending custom fields across to campaign monitor.

The username and email are being sent over just none of the cusom fields.

My form has fields such as: <input type=”text” name=”m_field_id_1” id=”phone”>

I’m using Single opt in lists and SL freshview Subscribe Version 1.4.0.

Anything I could have missed?

I’m having issues sending custom fields across to campaign monitor. The username and email are being sent over just none of the cusom fields.

Have you mapped the custom EE member fields to your custom CampaignMonitor mailing list fields?

Stephen

You mean within the extension settings? Yeah, all that seems to be set up correctly. I’ve even tried limiting it to just one field

You mean within the extension settings? Yeah, all that seems to be set up correctly. I’ve even tried limiting it to just one field

OK. From your original message, it looks like you’re using a custom registration form. If that’s the case, have you using the standard registration form?

If everything works with that, we at least know it’s a problem with the form, not the extension.

Cheers, Stephen

Hi Stephen,

Gereat extension, I got it set up and doing the basics in no time.

I have 2 problems specific to the project I’m on.

Problem 1: As I believe both username and screen name are required to be unique in the EE member management module they are not suitable to use as ‘real’ name fields. I got round this using the User module to push the email address into both of these fields, not using them in the front-end, then setting up a custom field for Name.

Question 1 : Would it be possible to include the default CM Name field in the list that can be mapped to?

Problem 2: I would like to map the standard EE member birthday field into a CM custom field. First I’d need the ability to map standard EE fields into custom fields, then I’d need to think about how to handle the date field when CM doesn’t offer date as a field type.

I’m thinking that a format of YYYYMMDD (e.g. 20091213 for todays date) would allow me to segment based on date ranges fairly easily.

Any ideas? I appreciate these aren’t trivial so I’m happy to discuss budgets offline.

Hi there,

Sorry for the delay in replying, things appear to be getting more hectic in the run-up to Christmas, not less.

Question 1 : Would it be possible to include the default CM Name field in the list that can be mapped to?

That’s do-able. The “name” field would need to be manually added to the CM field list (or some other way of overriding it provided), and the “subscribe” method updated, but it’s not a huge change.

I’m not sure about adding it to the main extension at this point; I think it could cause some confusion if not implemented well, so I don’t want to just quickly throw it together. If you want to branch the extension on GitHub, and let me know where the new repo is, I can help you sort this out.

Problem 2: I would like to map the standard EE member birthday field into a CM custom field. First I’d need the ability to map standard EE fields into custom fields, then I’d need to think about how to handle the date field when CM doesn’t offer date as a field type.

There are actually 3 standard EE member birthday fields, one each for year, month, and day. If you wanted to use the standard EE member birthday fields, but map them to a single CM field, you could:

1. Create a custom “full birthday” member field.
2. Map the custom member field to your custom CM field.
3. Create your registration form using the standard birthday fields.
4. Create a simple extension that runs before SL Freshview Subscribe, and populates the custom “full birthday” field.

You could also simply hide the “full birthday” field, and populate it on the registration form using JS, if that’s an option.

Makes sense?

Cheers, Stephen

Hi Stephen,

Do you have any idea of timescales for the next release containing the User Edit hook?

Many thanks

Thanks Stephen,

I’ve got round both issues by creating bespoke fields on both sides for now. It’s only CM’s limit on custom user fields that may force my hand further down the line.

Now I’m just keeping fingers crossed that the user edit hook will become available before the client has enough data to worry about it. Otherwise I’ll just write a cron job to dump all the EE data into CM each night.

Have you ever considered creating a similar extension to run with the Interspire Email Marketer product?

That’s one option I still have up my sleeve, but I’m reluctant to use it unless the client has their own dedicated server. The risk of screwing up our other clients is just too high.

@optima

Do you have any idea of timescales for the next release containing the User Edit hook?

I’m hoping to get this sorted over the Christmas “break” (I use the word loosely).

@shinemktg

Now I’m just keeping fingers crossed that the user edit hook will become available before the client has enough data to worry about it.

See above.

Have you ever considered creating a similar extension to run with the Interspire Email Marketer product?

I’ve never even heard of the Interspire Email Marketer product before.

Cheers, Stephen

I’ve never even heard of the Interspire Email Marketer product before.

It’s software rather than a hosted service so only really worth a look if you’re running large mailings off your own server.

For client work we always use 3rd party broadcast tools, but we have a few projects of our own where we know exactly where the data comes from and what content’s being mailed.

If you’re dealing with very large lists of your own and have a dedicated server then a solution like this is a good option. (by very large I mean more than about 50,000 names) It costs a few dollars, but it’s a lot easier to use than something like PHPList.

I’m investigating their API at the moment, I’ll post how we get on in a couple of weeks.