Switch on Tag by behaviour and the plugin writes tags into your autoresponder automatically. Here is the exact format, so you can build the automation before you run the webinar.
The tags:
Every tag is the webinar's own name inside WordPress, then a space, a hyphen and a space, then the behaviour:
- Webinar name - Attended
- Webinar name - No show
- Webinar name - Saw the offer
- Webinar name - Clicked the offer
- Webinar name - Watched the replay
- Webinar name - Unsubscribed
- Webinar name - Resubscribed
- Webinar name - Cancelled
The name is trimmed to 60 characters, so keep the first 60 distinctive if you run several similar webinars. Your customer facing title does not change the tags, so existing automations keep working if you set one later. Tags are created for you if they do not already exist.
Custom fields sent with every registration:
- rwb_session_ts. The session start as a UTC Unix timestamp. Drop it straight into a follow up link, or compare it with now inside your autoresponder, to give each lead their own hard deadline.
- rwb_session_utc. The same moment as a readable UTC date.
- rwb_webinar. The webinar title, which is your customer facing title if you set one.
- rwb_ followed by each tracking parameter the person arrived with, under its own name, so rwb_hop, rwb_tid, rwb_aff, rwb_hopid and so on. Names are lowercase.
Create the fields once:
Create these fields once in your autoresponder using exactly these names. Mailchimp uppercases its merge tags, so rwb_session_ts is RWB_SESSION_TS there. ActiveCampaign and GetResponse are matched on the field title you gave them. AWeber only accepts fields that already exist on that list, so create them before your first registration. A field you have not created is skipped, never invented.
ResultsAiX Mailer:
Mailer is the exception. Because it runs on this same site, the fields are created for you automatically at the first registration, each holding only the raw value, so rwb_hop holds testaffiliate and never rwb_hop=testaffiliate. They merge with any fields the subscriber already carries, and your Mailer audiences can segment on them directly. The name=value tags are still written alongside for anyone already segmenting on them.
When a seat is moved:
If a registrant switches to another session, only the two session fields, rwb_session_ts and rwb_session_utc, are updated. Everything else stays as it was.