SOLVED

Re: Issues with Webinar Token

Go to solution
kenmckown
Level 4

Issues with Webinar Token

I am building out an Interactive Webinar and have everything setup, I have a Smart Campaign that triggers to set "Registered" status and then send a notification email that contains the webinar link. I ran a test and the link is not populating.

 

I see my record in the Members section with a URL, but the email is not populating it using the {{member.webinar url:default=edit me}} token.

 

I even set a wait step before sending the email to make sure the URL populated in the webinar program.

1 ACCEPTED SOLUTION

Accepted Solutions
SanfordWhiteman
Level 10 - Community Moderator

Re: Issues with Webinar Token

A Wait step is really clumsy here; you can’t know how long to wait and always risk sending a blank value.

 

But I suspect the direct issue in your case is the email isn’t in the program.

View solution in original post

4 REPLIES 4
SanfordWhiteman
Level 10 - Community Moderator

Re: Issues with Webinar Token

A Wait step is really clumsy here; you can’t know how long to wait and always risk sending a blank value.

 

But I suspect the direct issue in your case is the email isn’t in the program.

kenmckown
Level 4

Re: Issues with Webinar Token

You are correct, I moved the email into the webinar program instead of the email program nested in it, and it worked instantly. Thank you!

NiharikaGoyal
Level 4

Re: Issues with Webinar Token

@kenmckown Generally {{member.webinar url}} token typically populates only after the webinar provider syncs the join URL with Marketo. This process usually takes around 10 to 15 minutes. Please ensure that a wait step of at least 15 minutes is included before sending the email.

If the webinar URL is still not appearing after that, there may be another underlying issue that needs further debugging.

 

Thanks!!

 

 

 

 

SanfordWhiteman
Level 10 - Community Moderator

Re: Issues with Webinar Token

You don’t really need to wait for {{Member.Webinar URL}} and such a long wait is really questionable UX.