This article is useful for gCast users that want member records in gCast to be updated automatically based on them having been sent a campaign from gCast. In particular, gCast users who have a re-engagement campaign series and/or who need to remain CANSPAM (Canadian anti-spam legislation) compliant should find this article useful.
In this article:
gCast gives you the ability to update member records as a campaign is processed and sent from gCast. We call this feature 'Post Process' and you can access it as part of your campaign set up.
'Post Process' allows you to alter certain settings1 on a member's profile and update these in bulk for every person that is included in your campaign send.
When creating or editing a campaign, you'll see a 'Post Process' tab located next to the 'Demographics' tab. This is where you would define the member profile attributes that you want to update when the campaign is processed and sent.
Any gCast user with an account login AND the 'Post Process' access level can use the 'Post Process' functionality. Please follow the links at the end of this article for more information on gCast access levels if you can't see the 'Post Process' tab in your campaign.
When creating or editing a campaign in gCast, go through the usual steps of entering in your content on the 'Layout' tab, setting your send date and other criteria on the 'Send Options' tab, and of course, setting up your demographic targeting.
When you click on the 'Save & continue' button on the 'Demographics' tab, gCast will take you to the next tab which is the 'Post Process' tab2:
As the text suggests, any demographic question that you add in here will set the value you select to all members that are sent this campaign.
Click on the drop-down in the 'Add a demographic' field and select the 'Standard Demographics' option from the drop-down list
At the time of writing this article, there are three available options for post-processing (even though all standard demographics are listed as being available for post-processing):
Example 1: Set a member's email opt-in status to opted-out
Click into the checkbox next to the 'Happy to receive emails' field (you should see a tick appear in the checkbox), then click the '<- add' button, and click into the 'No' field:
This setting means that everyone who is sent the campaign will be opted out from receiving future email campaigns when the campaign processes and sends from gCast
Example 2: Set a member's SMS opt-in status to opted-out
Click into the checkbox next to the 'Happy to receive SMS' field (you should see a tick appear in the checkbox), then click the '<- add' button, and click into the 'No' field:
This setting means that everyone who is sent the campaign will be opted out from receiving future SMS campaigns when the campaign processes and sends from gCast
Example 3: Set a member's record to be inactive
Click into the checkbox next to the 'Active user' field (you should see a tick appear in the checkbox), then click the '<- add' button, and click into the 'No' field:
This setting means that everyone who is sent the campaign will be made inactive (and will not be included in any future campaigns at all from gCast)
You can edit any campaign (using the standard rules for active/completed campaign editing) and make changes to the post processing settings however it is not currently possible to completely remove a post processing setting once you've added it in.
It is not currently possible to completely remove post processing settings from a campaign once they've been added. However, to work around this, simply set the demographic/s you selected to be the opposite of what you had them previously (e.g. if you had post process that updates the 'happy to receive emails' have an answer to 'no', then switching this answer to 'yes' in your post process tab will simply overwrite the existing answer of 'yes' with 'yes' and the member record's status will remain opted in to receive future email campaigns).
- happy to receive emails (yes/no)
- happy to receive sms (yes/no)
- active user (yes/no)
Other articles you might find useful:
User access levels in gCast (coming soon)