Mailing opt-in for Stager using CF7 (by DKZR)

描述

Use Contact Form 7 for your Stager mailing opt-ins form.

Stager is an all-in-one platform for ticketing, marketing and event planning. One of its features is a mailing tool for your customers. There is an API to register users for mailings but no WordPress integration to use this API. Until now!

To use this plugin your organisation needs a Stager envirionment, see Stager for more information.

You need to know your organisations Stager subdomain, eg. dkzr when your Stager domain is https://dkzr.stager.co/ and you need an Access Token. In your Stager Settings you will find the necessary information to configure your form.

All the configuration is done in your forms Additional Settings.

屏幕截图

  • Default form fields for Stager mailing opt-in: [email] (required), [firstname] and [lastname] (optional).
  • Required Additional Settings code snippets examples.
  • Help is available in the default WordPress help screen.
  • The contact form in your site with email, first- and last name fields.
  • After submit, you must check your email.
  • The email contains a confirmation link to your Stager confirmation page.
  • On the Stager confirmation page your customers can select the “audiences” they want to be part of.
  • The final page after your customers save the confirmation form.

安装

  1. Install Contact Form 7 through the WordPress plugin repository.
  2. Install this plugin through the WordPress plugin repository or by uploading the plugin zip file with the WordPress plug-in manager.
  3. Activate both plugins.
  4. Create a new form and follow the instructions in the “Stager CF7 integration” help tab.

To make use of this plug-in your organisation needs an account on stager.co

常见问题

How do I build and configure my form in CF7?

See the WordPress help tab in the CF7 form for more information and configuration under the “Stager CF7 integration” tab.

I configured multiple audiences, how does that work?

You need only one registration form. In the Stager opt-in process, your customers select the audience(s) they want to receive information for in the last step.

The process is as follows:

  1. Customer submits the registration form on your site.
  2. Customer receives an email with a confirmation link.
  3. On the Stager confirmation page your audiences are presented as options for your customer.

See the screendumps for an example.

评价

此插件暂无评价。

贡献者及开发者

「Mailing opt-in for Stager using CF7 (by DKZR)」是开源软件。 以下人员对此插件做出了贡献。

贡献者

「Mailing opt-in for Stager using CF7 (by DKZR)」插件已被翻译至 1 种本地化语言。 感谢所有译者为本插件所做的贡献。

帮助将「Mailing opt-in for Stager using CF7 (by DKZR)」翻译成简体中文。

对开发感兴趣吗?

您可以浏览代码,查看SVN仓库,或通过RSS订阅开发日志

更新日志

1.3.3 – 2025-09-11

  • Changed
    • Plugin description on request of Stager.co.
  • Added
    • Added explenation on how the Stager “audiences” work in your registration process and this plugin to this readme.
    • More screenshots of the form in your site, the email you receive and your Stager confirmation page.

1.3.2 – 2025-06-17

  • Added
    • Added load_plugin_textdomain since it does not seem to load automaticly when installed through the WordPress plugin directory?

1.3.1 – 2025-06-17

  • Added
    • icon 😀

1.3.0 – 2025-06-03

  • Changed
    • Renamed plugin slubs (… again …) for adding to WordPress Plugin directory
    • Simplefied adding help-tabs so I don’t need to use $_GET variables

1.2.0 – 2025-05-21

  • Changed
    • Renamed plugin slugs (again…)

1.1.1 – 2025-05-21

  • Changed
    • Updated code after tests with PCP

1.1.0 – 2025-05-21

  • Added
    • Screenshots
  • Changed
    • Renamed plugin slugs
    • Help label and instructions
    • Dutch translations
    • Readme updates
    • PayPal donation link
  • Removed
    • Old plugin slug

1.0.6 – 2025-05-20

  • Added
    • CF7 Help tab in edit/new screen
  • Removed
    • Integration setup, not needed for this

1.0.5 – 2025-05-20

  • Added
    • Readme
  • Changed
    • Dutch translations

1.0.4 – 2025-05-16

  • Changed
    • Plugin description

1.0.3 – 2025-05-16

  • Changed
    • Code refactor
    • Dutch translations
  • Added
    • Checks for proper API call response
  • Removed
    • error_log-ing

1.0.2 – 2025-5-6

  • Added
    • More helptexts
  • Changed
    • Dutch translations

1.0.1 – 2025-5-6

  • Added
    • Helptexts
    • Dutch translations

1.0.0 – 2025-5-6

  • Added
    • Proof of concept code