You can't use a lead token in this context.
You'll have to flag on something else that's predictably in the URL. Don't the non-app URLs always start with a small set of predictable hostnames (www, pages, etc.)?
Thanks for clarifying that.
That's a good point. Our non-app URLs generally start with www, and our app does not have www. I'll try implementing a filter based on that criteria.
Unfortunately it's either not working, or I'm not implementing it correctly.
There are two smart campaigns I'm running. The first campaign adds an Interesting Moment to a lead, as well as adding it to a Salesforce campaign. The steps are shown here:
The second smart campaign is triggered when a lead is added to the SFDC campaign shown in the second screenshot above. The steps are shown here:
After making these changes, I checked on the status of a lead who MQL'd. This is their activity log:
The redacted URLs before kennasecurity.com are instances of the prospect using our app. As you can see, it appears that Marketo is still registering our app as visiting a web page, and thus triggering the first smart campaign.