What Campaign Monitor custom fields do I need to have set up to import contacts to RunGopher?

RunGopher requires that you have custom fields set for all subscribers who are in your Campaign Monitor campaign. This allows us to import the data needed for an SMS campaign. Do note that these fields do not have to be called anything specific - just a name that will help you identify the relevant information. The following fields are mandatory: 

Mobile number - This is the mobile number of the constituent. 

First Name - The first name of the contact, used in many RunGopher campaigns to personalize the message. 

Last name - In some RunGopher SMS campaigns, this is an optional field. In others, it's mandatory.

When you import your Campaign Monitor campaign into RunGopher, you'll see a menu like this:

Using the drop-down, you can select which custom Campaign Monitor field maps to which RunGopher field. 

For some campaigns, RunGopher will require additional fields:

address - If you are running any campaigns that require address as an input (eg. Address Verification) then RunGopher requires that this custom field is populated.

custom1 - If you are using any custom fields (ie. custom1, custom2, custom3, custom4) then you will need to have those fields set up as custom fields within Campaign Monitor, with the same name as they appear in message copy (and CSV upload template) for your RunGopher campaign.

If you need any tips for working with Campaign Monitor custom fields then please click here.