We have an integration setup with On24 and I have an email I am testing that uses the {{member.webinar url}} token in a confirmation email once someone has registered. I have and email containing 3 variation of this token being used
one as with a WEBINAR LINK to the on24 webinar and the token being used in the URL link
one where the token is explicitly mentioned in the body of the email
and a save the date calendar link that download an ics file that has this token inside the ics file
Like so
Webinar Link - links to the webinar but the token is in the URL link
https://event.on24.com/interface/registration/autoreg/index.html?eventid
calendar
However no matter which link i click it always shows up in link tracking as the below.
http://mkt-franchise.schwab.com/rs/876-MVP-978/334/Test+Webinar.ics
Doubt it's happening the way you describe. It's not that both links are bring rewritten to the same tracked link (on your branding server). Rather, the {{Member.Webinar URL}} isn't being tracked at all. Here's a much better way to send out {{Member.Webinar URL}}:
Hi Sanford,
Question for you. We are trying to move the entire email process for ON24 webinars over to Marketo. I have set it up so that the confirmation email contains the {{Member.Webinar URL}} token, which works fine. However, the Marketo form that a user fills out should then taken users to the ON24 lobby for the event. You can't use tokens in the Marketo form submission screen, which let's you either stay on the same page, redirect to external URL, or redirect to a Marketo landing page. I want it to redirect to the ON24 lobby (https://event.on24.com/wcc/r/2291136/E35F51A04736B6614EC84AB42D611861) but with the tracking info appended to the URL that is populated via the {{Member.Webinar URL}} token.
Right now, if users fill out the form, they are taken to that lobby page, which generates an additional blank registration in ON24. If they choose the add to calendar icons from that lobby page, the URL in the calendar invite will not have the custom appendages to it needed to track the user info.