Event Custom Fields not working

[Kaitlyn_Nelson2]

Hi there, 

I am creating a drip campaign that needs to use 5 different event custom fields for 4 different CRM tracking codes that we are using. 

Most event custom fields are used within the emails, but there are two LP's that are using the same event custom field to direct the contact to our website. I tested the emails the other day and they all worked, but now this morning when I checked it leads to a #blocked page and when I go into a record and investigate, the URL works and everything looks fine, but just won't work when I send myself a test. Any ideas on why this is happening?

I used https:// before using the event custom field token and made sure that there was only www. in the record. I can't think of any reason why the links work when I copy and paste them into a browser, but not when I test the page?

Someone please help! 

[SanfordWhiteman]

You will have to provide the actual examples of broken links.

[Kaitlyn_Nelson2]

This is the link that I am using for Event Custom field 2 

www.ariba.com/solutions/intelligent-spend-management?campaigncode=CRM-XR19-FMA-IBFZ_J6A2

[SanfordWhiteman]

And the page it appears on and/or the HTML fragment (syntax highlighted) in which you've inserted the token.

[Kaitlyn_Nelson2]

Did I provide what you needed?

[Kaitlyn_Nelson2]

Here is the LP: SAP Ariba Solutions for Direct Spend 

[SanfordWhiteman]

And how you're attempting to embed the token in HTML.

[Kaitlyn_Nelson2]

<div><br /></div>
<div>Your company is spending money from many sources. Organizations need to manage spend across procurement, external workforce, and travel and expense categories. With the best systems from each category, using the most extensive networks and platforms, SAP brings your data into one unified view. </div>
<div><br /></div>
<div><br /></div>
<div><a href="https://{{lead.Event Custom Field 2}}" target="_blank">Learn more </a></div>
<div><br /></div>
<div><br /></div>
<div><br /></div>

[SanfordWhiteman]

The {{lead.token}} will be empty -- and thus the link will consist of only the protocol, "https://" -- if the link that brought the person to the page wasn't correctly tracked.

Ergo, you need to look at the email side to determine why link is not being tracked (rewritten to bounce off the branding domain and the mkt_tok query param appended to the LP URL).

[Kaitlyn_Nelson2]

So just to be certain, these SHOULD work on LP's right? It's not for email?