This article is useful for gCast users who are looking to implement the use of member preferences on their sign-up/opt-in pages that are linked directly into gCast.
Member preferences help you to more effectively target your campaigns or where, for legal reasons, you might want to gain stronger and clearer consent.
In this article:
gCast offers some basic opt-in code snippets for including iframe opt-in code in your webpage, but the most effective way to collect preferences (or any additional information) from someone at the point of opting-in is to create a webform on your page and use gCast's 'custom form' code snippets to build out your preferences.
All of the code snippets for opt-in data are readily available to all gCast accounts and hinge heavily around getting smart with your demographics - and most gCast users should be familiar with demographics and how they work.
Step 1 - Create your demographic questions
Before you can insert your html code into your webpage, you'll need to create your demographic questions in gCast first. If you're not familiar with creating demographics, you can read more information here.
Any demographic that is going to be included in an opt-in form on a webpage must have a 'Reference' (which you insert during the creation of the demographic).
Once you've created your demographics, you're ready to start inserting the code into your webpage. We advise that your webmaster or someone who is familiar with html perform this task.
Step 2 - Add the code snippet into your opt-in page html code
You can find an entire gCast page dedicated to the 'custom form' code and permissible inclusions, it even has some sample code to get you going. Simply, login to gCast, click on the 'Admin' link, then scroll about halfway down the Admin page and click on 'Special Links' (under the 'Resources' section). On the 'Special Links' page, scroll down to the 'Opt-in via your custom form' section and click on the 'click here' link:
The 'custom form' information page includes some sample code that has some account-specific information in it that you can copy and paste out into your opt-in page's code. To add your preference demographics to the page, look for the html code line that looks like this:
My Question:<input type="text" name="questionField_MyOtherQuestionRefFromSystem" value="" ><br><br>
And modify the following:
'My Question' - this is the text that will appear on the webpage when a visitor views it
'Input type' - make sure the input type you select here aligns with the setup of the demographic question in gCast. For example, if you had created a multiple choice/single answer question with a range of possible answers, then a 'text' input type probably isn't appropriate and will not populate your data correctly for you to target on at a later stage. There are many different input types you can choose from. Your webmaster will be able to assist you in choosing the most appropriate for your needs.
'questionField_MyOtherQuestionRefFromSystem' - this is where you would insert the 'Reference' that you added to your demographic when you created it. For example, if you created a demographic with a reference of 'IceCream' then your version of this field would be: 'questionField_IceCream'.
Step 3 - Test your results
It's always important to 'inspect what you expect'. Testing your opt-in page to ensure that the experience is what you want it to be for anyone visiting, as well as completing an opt-in or two yourself and then checking the result in gCast are things we can't stress enough before you rely on the opt-in mechanism for collecting data from your page visitors.
If you're concerned about trying this out on your live gCast account, drop us a line and our team can help set up a sandpit account where you can play to your heart's content before migrating your code to your live gCast account.
Step 4 - Target your campaigns
Don't forget, for preferences to be useful, you will need to review any current campaigns you have running (including auto-responders and set and forget campaigns) to ensure that they're targeting based on the preferences you've collected. Any future campaigns you create may need to take consideration of the preferences too.
You may even want to think about having different welcome emails and distinctly separate campaigns per preference, if your preferences are significantly different in nature.